Oasis

Inspiration

The modern airport experience is broken. Once a passenger passes security and reaches their gate, their journey hits a brick wall. They spend an average of 60 to 90 minutes trapped in "dead time"—anxiously checking flight boards and disconnected from the terminal's retail economy. For passengers, it's a high-stress waiting game. For airport vendors (like Pret A Manger or World Duty Free), it's millions in lost, trapped revenue.

We built Oasis to bridge this gap. Oasis is a dual-sided marketplace that turns terminal dead time into a hyper-efficient, gamified digital economy.

What it does

Oasis is a comprehensive airport commerce ecosystem, currently mapped to London Gatwick (LGW), featuring two distinct interfaces:

1. The Passenger Journey (B2C)

• Live Telemetry: A real-time departure/arrival feed so passengers never have to stare at a terminal monitor.
• Gate Wayfinding: An interactive map routing passengers between Terminal North and Terminal South.
• Play-to-Earn Lounge: A "Terminal Trivia" mini-game where passengers earn loyalty tokens for their aviation knowledge while waiting.
• In-Seat Delivery: A localized marketplace where passengers can spend their earned tokens or crypto to order food and retail directly to their gate.

2. The Merchant Portal (B2B)

• Terminal Operations Dashboard: A stark, high-contrast B2B portal for Gatwick vendors to track live order queues, dispatch gate deliveries, and monitor daily revenue volume.

How we built it

We built Oasis with a "Web-First" approach using React Native and Expo, styled with Tailwind CSS (via NativeWind). We implemented a bespoke "Aviation Brutalism" design system—utilizing pure blacks, high-contrast text, and sharp 90-degree corners to mimic premium enterprise aviation software.

For our data layers, we integrated the AviationStack API for live flight telemetry and React-Leaflet (OpenStreetMap) for interactive terminal mapping. The application is deployed live on Vercel.

Challenges we ran into

Building a cross-platform Web3 and geolocation app at 6:00 AM comes with brutal technical realities.

• The Bundler Wars: We originally attempted to integrate heavy native SDKs (@solana/web3.js and proprietary Mapbox LiDAR files). However, Expo's Metro bundler strongly rejected the Node.js cryptography polyfills, resulting in repeated white screens of death.
• The Web-Safe Pivot: We rapidly pivoted our architecture. We swapped native maps for a dynamically loaded, web-safe react-leaflet implementation (bypassing the dreaded window is not defined SSR error). We completely rebuilt the UI to simulate the Solana connection, prioritizing a flawless, crash-proof live web demo for the judges over unstable native dependencies.
• API Security: We had to implement a secure HTTPS proxy logic to fetch live HTTP-only AviationStack data without triggering Vercel's mixed-content security blocks.

Accomplishments that we're proud of

We successfully built and deployed a fully functioning, two-sided marketplace ecosystem in a single night. We didn't just build a mock-up; the app pulls real Gatwick flights, uses real mapping tiles, features a playable game state, and cleanly separates the passenger UX from the merchant B2B dashboard.

What we learned

We learned that in a hackathon, perception and stability are reality. A perfectly functioning, beautifully designed web-safe prototype is infinitely more valuable than a broken app with bleeding-edge cryptography installed. We also mastered Expo Web's intricate configuration, specifically disabling unstable package exports to force Metro to resolve CommonJS modules.

What's next for Oasis

The web prototype is live. Next, we will compile the native iOS and Android binaries, integrate true Solana wallet adapters for zero-fee micro-transactions, and partner with Gatwick's enterprise data team to import 3D Mapbox IMDF floor plans for true indoor LiDAR routing.

Built With

• aviationstack-api
• expo.io
• github
• leaflet.js
• nativewind
• openstreetmap
• react-native
• tailwind-css
• typescript
• vercel