Case Study · Travel
A food delivery app built for airports and sports stadiums
Delivering food to a gate or a stadium seat is nothing like delivering to a house. A US technology startup asked AMT to build a platform for exactly that: native customer apps, a restaurant portal, a delivery agent app and an admin console, with 24-hour advance ordering and timezone-aware scheduling for travellers.
Schedule Technical DiscoveryYour first conversation will be with a senior technical partner, not a salesperson.
Published
At a glance
- Client
- US-based technology startup
- Industry
- Travel and transportation, venues and food service
- What AMT built
- Customer apps (iOS and Android), restaurant and vendor web portal, delivery agent app, admin console
- Key features
- Real-time ordering, advance ordering up to 24 hours ahead, timezone-aware scheduling, automatic order queuing for agents
- Stack
- Angular, Node.js, MongoDB, Android SDK, Swift
The short version
Airports and stadiums are crowded, self-contained places where customers want food fast and travellers cross timezones. AMT built an ordering and delivery ecosystem that connects four groups of users. Customers order now or up to 24 hours in advance, with the schedule adjusted for their timezone. Orders queue automatically for delivery agents, and restaurants manage menus and incoming orders from their own portal.
The problem
- A different delivery environment. Locations and customer needs inside airports and stadiums differ from home delivery.
- Advance ordering. Customers needed to pre-order meals up to 24 hours ahead.
- Timezones. International travellers move between timezones, so advance orders had to be scheduled correctly.
- High density. Restaurants and agents had to cope with crowded, high-traffic conditions.
- Four user groups. Customers, restaurants, delivery agents and administrators needed one connected order lifecycle.
What AMT built
Customer apps
- Native Android and iOS apps
- Food discovery and ordering from participating restaurants
- Real-time orders and advance orders up to 24 hours ahead
- Timezone-aware scheduling for international travellers
Restaurant and vendor portal
- Restaurant onboarding and management
- Menu creation and maintenance
- Incoming and pre-scheduled orders in one view
- Coordination of food preparation and fulfilment
Delivery agent app
- Orders queue automatically for agents
- Delivery task management
- Linked to restaurant and customer workflows
Admin console
- Central web administration
- Restaurant, vendor and delivery agent management
- Oversight of platform operations and order processing
Why timezones mattered
A traveller might place an order before boarding, in one timezone, for collection after landing in another. The platform schedules advance orders against the right local time, so customers can plan meals ahead and restaurants and agents know exactly when to deliver.
How AMT contributed
| Area | What AMT did |
|---|---|
| Product and design | Customer journeys, ordering workflows, user interfaces |
| Front end | Angular admin and restaurant web apps |
| Back end | Node.js services for ordering and operations |
| Mobile | Native Android (Android SDK) and iOS (Swift) |
| Data | MongoDB |
| Workflow | Real-time orders, advance scheduling, restaurant and agent coordination |
Results
- One ecosystem connecting customers, restaurants, delivery agents and administrators
- Advance ordering up to 24 hours ahead
- Timezone-aware scheduling for international travellers
- Automatic order queuing for delivery agents
- Web apps for admins and restaurants plus native iOS and Android apps
- Restaurant, vendor, menu and agent management in one place
Technology stack
| Layer | Technology |
|---|---|
| Web front end | Angular |
| Back end | Node.js |
| Database | MongoDB |
| Android app | Android SDK |
| iOS app | Swift |
Before you build something similar
- Where exactly is the customer? Gates, seats and zones need a location model that home-delivery apps do not have.
- Whose clock wins? Store order times in one standard and show them in each user's local time.
- How do orders reach agents? Automatic queuing beats manual dispatch in a crowd.
- Native or cross-platform? This client chose native apps. The trade-offs are on our mobile app development page.