Cruise app development cost in 2026: budgets, drivers and cuts
TL;DR
Cruise app development cost in 2026 runs from $8,000 in one vendor's published range to $1,000,000 and above in another's, and the spread comes from what each price leaves out. Across Mercury Development's closed contracts for cruise software, the median is $250,000 and the range runs from $10,000 to $1,000,000.
- Legacy cruise systems, ship connectivity and release gates for accessibility and payments move the price more than screen count does.
- Vendors disagree on what cross-platform saves: Bacancy says 20-30%, Dotcode says 40-60%. Either figure applies to the app layer only.
- Pre-cruise flows first, a hosted payment page and one codebase across brands are cuts that hold up.
- Dropping offline behavior or contingency looks cheap and returns as support load and change requests.
- Store deadlines from Apple and Google are fixed yearly work inside the 15-20% maintenance budget that vendors quote.
What cruise apps cost in 2026
Published prices for this query disagree by two orders of magnitude. GMTA Software's cruise app development guide puts the average at $8,000 to $20,000, quoting what Asian development companies charge, and expects about 4 months to launch. Dotcode's travel app cost guide starts a travel MVP at $15,000 to $50,000 and takes full platforms past $500,000. Bacancy's 2026 cost breakdown starts an MVP at $50,000 and runs enterprise booking platforms to $1,000,000 and above.
Our records sit well above the low end. Across Mercury Development's closed contracts for cruise software, the median is $250,000 and the range runs from $10,000 to $1,000,000.
The gap is scope. Published ranges price screens: sign-in, search, booking, a map. A cruise line app prices the systems behind those screens, and those systems now carry real money. On Royal Caribbean Group's second-quarter 2025 earnings call, CEO Jason Liberty said nearly 50% of onboard purchases now come through the mobile app.
Two store deadlines and an EU law set the 2026 floor
Every cruise app now carries a fixed yearly bill before any feature work. Apple's upcoming requirements page says that from April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 and the iOS 26 SDK or later. Google Play requires new apps and updates to target Android 16 (API level 36) from August 31, 2026, with extensions available to November 1, 2026. Both companies have raised these minimums year after year.
Accessibility moved too. The European Accessibility Act, Directive (EU) 2019/882, applies to services provided to consumers after June 28, 2025. Its scope names websites, mobile apps and electronic ticketing for waterborne passenger transport. Whether your sailings fall in scope is a question for counsel. If they do, accessibility is a release gate, and it belongs in the first estimate.
Dotcode and Bacancy both put maintenance at 15-20% of the build cost per year. On a $250,000 build, that is $37,500 to $50,000 a year, and the store deadlines land inside it.
How we put these numbers together
We read the three pages that AI search cites for this query today. GMTA Software's guide is the only one about cruise apps and answers three questions in its FAQ. Dotcode and Bacancy price travel apps in general. Platform deadlines come from Apple and Google, accessibility scope from the directive text, and payment scope from the PCI Security Standards Council FAQ as summarized by Davis Wright Tremaine.
Mercury's figures come from closed contracts and project records for cruise software, without client names or counts. Any group with fewer than three data points is not published. Mercury Development builds cruise software, so read this as an interested view.
Cruise app cost ranges at a glance
| Source | Range | Scope behind the number |
|---|---|---|
| GMTA Software, cruise app | $8,000-$20,000 | Average cruise app from Asian vendors, about 4 months |
| Dotcode, travel MVP | $15,000-$50,000 | One or two core flows, 6-10 weeks |
| Bacancy, travel MVP | $50,000-$100,000 | Search, basic booking, one payment gateway, one platform first |
| Bacancy, enterprise booking platform | $300,000-$1,000,000+ | GDS integrations, multi-currency payments, fraud controls |
| Mercury, closed cruise software contracts | $10,000-$1,000,000, median $250,000 | Guest apps, crew tools and shipboard platforms built on cruise line systems |
None of the published ranges mentions ship-side servers, ship-to-shore sync or testing at sea. Those are the lines that push a cruise program toward the upper rows.
If procurement bars paid discovery, price the same scope with our guide to a cruise software RFP without paid discovery.
What drives the price of a cruise app
Screen count is the smallest driver. Five things move a cruise app budget more:
- Legacy integration. For cruise line clients Mercury cannot name under NDA, we build backend components that aggregate data and functions from dozens of legacy microservices before the app can show a single booking. An API that works in production and fails in QA adds days to every feature that touches it.
- Ship conditions. Connectivity at sea is slow and drops without warning. Our spa platform for OneSpaWorld runs as web applications on onboard servers without external internet, so anything a guest or crew member waits for lives on the ship and syncs ashore later. Some behavior reproduces only on a real ship, and testing has to go to sea.
- Brands and lines. A group that keeps each brand on its own branch pays for every later change once per brand. Our guide to one codebase for multiple cruise brands shows the alternative.
- Release gates. On our cruise programs under NDA, accessibility (ADA) and PCI DSS are release conditions. An app that misses either does not ship, so the work sits in the base estimate.
- Client readiness. Test accounts expire and VPN access arrives late. Price the wait: four engineers blocked for two weeks is 320 hours. At the $40-$80 an hour Dotcode lists for Eastern European teams, that is $12,800 to $25,600. At its $120-$200 US rate, it is $38,400 to $64,000.
How much each scope cut saves
Cruise buyers ask the same question in the negotiations we run: what does each cut take off the budget? Here is the short answer, with the bill each cut sends forward.
| Scope cut | What it saves | What it costs later |
|---|---|---|
| One cross-platform codebase instead of two native apps | 20-30% (Bacancy) to 40-60% (Dotcode) of the app build | Native modules for BLE or NFC features; backend unchanged |
| Pre-cruise flows first, onboard flows in release two | Ship-side integration, onboard servers and sea trials leave release one | A second integration project before onboard ordering |
| Card entry on a payment provider's hosted page | Can bring web checkout down to SAQ A, the shortest PCI self-assessment | Onboard point-of-sale still needs its own assessment |
| Crew tools as a private app or a tablet web app | No store review per release; private Play apps skip the target API rule | Device management and kiosk setup |
| One codebase with brand configuration | Each fix ships once instead of once per brand | Design tokens and feature flags up front |
| Lower-cost crew tablets | At 1,000 devices, $100,000 for every $100 off the unit price | Performance testing on low-end hardware |
| AI recommendations moved to a later phase | $15,000-$35,000, by Dotcode's feature pricing | Personalization waits |
The cross-platform saving is real and narrower than the headline. GMTA says building native for both platforms may double the cost. All three figures price the client layer, and the integration layer does not shrink when the interface is written once. For cruise line clients under NDA, we rebuilt a passenger app on React Native instead of porting the old stack. Our Distiller case shows the same choice outside cruise: one React Native codebase for iOS and Android.
Pre-cruise first is the cut we recommend most. On one cruise program, dining plans went into the MVP as a pre-cruise flow because that scope was simpler than live onboard availability.
The payment cut needs care. Michael Borgia of Davis Wright Tremaine explains that SAQ A covers merchants who fully outsource card processing through a compliant provider's hosted site, redirect or iframe, and never store, process or transmit card data themselves. It does not cover in-person point-of-sale, so onboard card sales stay in a larger assessment.
Crew tools have the widest options. Google exempts permanently private apps, restricted to one organization for internal distribution, from its target API rule. Our OneSpaWorld platform reaches staff on Android tablets in kiosk mode or on ordinary computers, with no store release per update.
Buying a platform instead of building is compared in our guide to onboard apps off-the-shelf or custom.
Cuts that look cheap and cost more later
Offline mode is the first. Dotcode prices it as a $5,000-$12,000 feature for travel apps. On a ship it is architecture: where data lives, what syncs when, which side wins a conflict. Cut it and the failures move to the guest services desk. Our guide to offline-first apps on ships shows what the cut removes.
Contingency is the second. On one shipboard platform, we priced a contingency reserve at 20% of the core estimate and showed it as its own line. The buyer asked us to remove it, and we did. The risk stayed: missing API documentation and late system access returned as change requests. Cruise buyers often ask vendors to strip risk margins to win a comparison, and the reserve is the first thing to go.
Testing at sea is the third. GMTA puts testing at 8-12% of overall development cost. Dropping sea trials saves travel and crew coordination, then leaves ship-only behavior for production to find. Our guide to cruise ship app testing covers what a sea trial catches.
What our cruise programs show
Our spa platform for OneSpaWorld has run in production since 2018 on over 160 ships operated by multiple cruise lines. Staff schedule and book treatments, fill in guest intake forms and check out with dynamic pricing, all on onboard servers. We also built a spa pre-booking site for Windstar Cruises guests, replacing bookings through OneSpaWorld's call center.
For cruise line clients Mercury cannot name under NDA, we build React Native food and beverage apps, tableside ordering wired to kitchens and bars, and backend components that aggregate dozens of legacy microservices. These programs carried work the client side had to unblock first: test accounts, VPN access, API documentation.
From Mercury's contract records for cruise software:
- The median closed contract is $250,000, and the range runs from $10,000 to $1,000,000.
- Around 45% of contracts closed under $200,000.
- Around 30% closed at $700,000 or more.
Price followed integration depth more than screen count. The top of the range belongs to programs that combined legacy integration with fleet-wide rollout.
Blocked engineering time and how to avoid it are covered in our guide to mobile development when the backend is not ready.
Price the integration layer before the screens
Screens are the cheapest part of a cruise app and the only part most published estimates price. So start the estimate where the money goes. Ask each vendor for the integration layer on its own line: which systems release one reads from, how many record types, what runs on the ship.
A vendor that cannot split that number has not scoped it. Then cut from the edges inward. Defer features, phase onboard work, move payments to a hosted page. Never cut integration depth by accident, because it comes back as a change request at a worse price.
One question sorts vendors fast: "Which of our systems does release one read from, and what does the app do when the ship loses its link?" A team that has built for ships answers with a sync model. A team that has not answers with a loading spinner.
Written by Rob Devereaux, Chief Operating Officer at Mercury Development. Rob has run the firm's operations from Hudson, Ohio since 2019 and has over 20 years of operational and financial experience. The contract and scoping records behind this article's pricing data sit in the operations he oversees.
Pricing a cruise app? Get every scope cut on its own line
Tell us what your app has to do, which cruise systems it reads from and what must work at sea. We will price the base scope, then show what each cut removes and what it sends to a later release, so you can decide with the numbers in front of you.