About the client
The client runs a digital travel platform offering bookings, multilingual travel content and agent-led travel assistance. Much of the agent side of the business still ran offline: agents had offers to sell and customers to advise, but no shared digital channel to publish those offers or hold conversations. The client wanted to bring agents and consumers onto the same platform, in several languages, without building two unrelated products.
Getting offline travel agents onto a digital channel
- No place to manage offers. Agents could not list, update or retire travel offers in one place.
- No live conversation. There was no real-time channel between agents and consumers, and no group chat for travel parties.
- No way in. The platform lacked invite-based onboarding, deep links and location-aware agent discovery, so consumers had no easy route to an agent.
- Backend limits. Existing services were not built to handle multilingual data at scale, nor to track agent availability or offer publishing as one workflow.
What FiftyFive built
FiftyFive ran the work full cycle, from product consulting and UI/UX design to backend, mobile apps, cloud setup and QA. The team built: an agent app and a consumer app in Flutter, sharing a common component architecture; Firebase Authentication, Cloud Firestore and Firebase Cloud Messaging for sign-in, real-time sync and event notifications; deep links for agent invites, joining group chats and connecting a consumer to an agent; a Node.js backend with APIs for offer management, agent discovery and chat workflows; location tracking, multi-language content and role-based access across both apps.
How the solution works
Two apps, one component base
- The agent and consumer apps are separate Flutter applications built from shared components, so screens and behaviour common to both are written once and stay consistent.
Real-time data and notifications
- Firebase Authentication handles sign-in.
- Cloud Firestore keeps offers and conversations in sync across devices in real time, and Firebase Cloud Messaging pushes event-based notifications, such as a new offer or chat message, to the right users.
Invites and discovery
- Deep links carry an agent's invite, a group-chat join or a direct connection request straight into the right screen of the app.
- Location data lets consumers find agents near them, and role-based access keeps agent and consumer permissions separate.
Backend services
- The Node.js backend exposes APIs for publishing and updating offers, discovering agents and running chat workflows, and serves content in multiple languages.
Technology stack
What the solution enabled
Business transformation
One for agents and one for consumers on shared components
Messaging between agents and consumers, with group chats
Agent discovery with invite-based onboarding
Two apps
Two mobile apps, one for agents and one for consumers, built on shared components.
Offers
A central place for agents to publish and update travel offers.
Messaging
Real-time agent–consumer messaging, including group chats joined by deep link.
Onboarding
Invite-based onboarding and location-aware agent discovery.
FiftyFive Technologies designed and built two mobile applications for a travel platform serving travellers in South Asia and international markets: one for travel agents and one for consumers. Agents previously had no digital way to list offers or talk to customers. FiftyFive built both apps in Flutter on a shared component architecture, with Firebase for authentication, real-time data and notifications, and a Node.js backend for offer management, agent discovery and chat. The delivered apps support deep-linked invites, group chat, location-aware discovery and multilingual content.
Technical questions
How are the agent and consumer apps built?
The agent and consumer apps are separate Flutter applications built from shared components, so screens and behaviour common to both are written once and stay consistent.
How do deep links work in the apps?
Deep links carry an agent's invite, a group-chat join or a direct connection request straight into the right screen of the app.