A hub, not another silo.
Experience shows that travel organisations don't want yet another system to manage separately. That's why we build our travel apps as a hub architecture by default: one API layer that talks to your existing GDS, PMS, payment and CRM systems, with the mobile experience built on top. To build that layer, we draw on our experience with marketplace architectures and payment platforms.
In practice, the hub looks like this: a service layer with an adapter for each integration (Amadeus adapter, Mews adapter, Mollie adapter, in-house CRM adapter), a simple contract model that the mobile app calls (search trip, book trip, get itinerary, pay balance), and monitoring so you can see which integrations are slowing down or failing. If a GDS goes down, the app falls back on the last known cache instead of breaking the entire user experience, which in the travel industry can be the difference between a satisfied customer and a complaint flow.
Do you have your own middleware or a legacy reservation system in-house? No problem: we integrate those case by case. It takes a little extra time in the planning phase, but it prevents a mountain of integration debt later. It also means your own IT team can maintain the app independently in the future, because the adapter layer is clearly separated from the mobile experience.