Product Ideas · Cruise
Cruise line apps: three features guests need
Most cruise line apps work well on board, connected to the ship's Wi-Fi. Step ashore on a port day — exactly when guests need their plans — and they stop working.
The problem
A cruise app has a harder job than most. Connectivity at sea is limited and expensive, guests move between ship and shore every day, and the information they need lives in several systems: the booking engine, the pre-cruise portal and the ship's own property management system.
The result, at many mid-size lines, is an app that is a thin layer over those systems — fine when it can reach them, and of little use when it can't.
Three missing features
- Works ashore, with no signal — The day's programme, the guest's own plans, booked excursions, all-aboard time and the ship's location, all available with no connection at all — and a planner that covers the whole cruise, not just today, with reminders that fire whether or not the phone can reach the ship. Not working off the ship is the complaint guests make most often. Some lines already design for it — Fred. Olsen's app was built for minimal connectivity, and Carnival's HUB app runs in airplane mode on the ship's network — so guests increasingly expect it.
- Dining that knows your dietary needs — Book a table, choose a sitting, and have the dietary requirements given at check-in carried through to the restaurant, so the guest doesn't explain their allergy to a new waiter every night. Dining reservations are already in some apps — P&O and Marella offer them — but in the apps we looked at, the dietary information collected before the cruise never reaches the galley. The data exists; it just doesn't travel.
- One app, not three — Check-in, payments, upgrades, the onboard account, bookings and messages in one place, with one login, from the day of booking to the day of disembarkation. Many lines run a pre-cruise web portal, an onboard app and a browser front end side by side, often from different suppliers. Guests aren't sure which to use, and the joins between them are where things break — card registration failing between the app, the portal and the payment provider is a typical example.
How we'd build it
Offline-first, with a ship-side node
Each guest's itinerary, bookings, programme and menus are replicated to the phone and to a server on the ship, and synced whenever a link is available — Starlink at sea, or shore connections in port. The app reads from the phone first, so it never waits on the network.
One API over the existing systems
A single guest-facing layer over the booking engine and the onboard property management system, rather than replacing them. Guests get one app and one login; the line keeps the systems it has already invested in.
The same build on every ship
A per-ship capability manifest switches features on and off by vessel, so older ships without the hardware for a feature get a graceful fallback instead of a separate release.
Designed for an older audience
Large type, VoiceOver and TalkBack support, a published accessibility statement, and a printable daily programme generated from the same data — because many cruise guests are not the people app designers usually picture.
Based on public app store listings, release notes, reviews and press coverage, September 2026. Product Ideas pages describe what we think a category of product is missing; they're ideas, not a review of any one company's app. Also see: hotel booking apps.
Questions people ask
Why doesn't my cruise app work when I'm ashore?
Most cruise apps fetch everything from servers on the ship, reached over the ship's Wi-Fi. Once you step ashore your phone is off that network, so the app has nothing to show. An offline-first app keeps your plans, bookings and the day's programme on the phone itself, so it works anywhere.
Do I need to pay for Wi-Fi to use a cruise line's app?
Usually not on board — most lines let their app reach the ship's own network for free, even without an internet package. The gap is ashore and anywhere the ship's network can't reach, which is why caching on the phone matters.
Can I book dining and record dietary requirements in a cruise app?
Some cruise apps take dining reservations, and most lines collect dietary requirements at check-in. What is rarely joined up is the two: the information you gave before the cruise reaching the restaurant you have booked.
Why do cruise lines have a separate portal and app?
Pre-cruise booking, payments and check-in are often built by one supplier and the onboard app by another, each over different systems. A single guest-facing layer over both gives guests one app and one login without replacing the systems behind it.
Run a cruise line?
Tell us which ships, which systems, and what your guests complain about most.
support@powerslave.devOr see what to put in the first email.