Ask most people what app they use for group trips and they’ll name one, usually the chat app, because that’s where the trip visibly lives. Ask what they actually use and the honest answer is a stack: WhatsApp for talk, Splitwise for money, Google Maps for finding each other, a shared album for photos, and a notes doc or spreadsheet somewhere for the itinerary nobody can find when they need it. Five tools, one trip, no single one of them aware the other four exist.
That’s the real comparison worth having, not which chat app beats which splitting app, but what a group gets from running five specialists against what it gets from one app that does less of each thing but knows they’re all the same trip.
What the default stack actually is
A chat group carries the conversation: who’s coming, what time, did you see this restaurant, are we still on for Saturday. It’s real-time, it’s where the group already lives, and everyone already has it installed, so there’s zero setup cost. It also ends up carrying the plan by default, which is where it starts to strain.
A splitting app carries the money. Something like Splitwise logs who paid for what and keeps a running balance, and it’s genuinely built for that job in a way a general chat thread never will be, since chasing “who owes what” back through two hundred messages is exactly the failure mode a dedicated ledger exists to prevent.
A maps app carries location. Google Maps in particular does live location sharing well: open it, share your location with the group for a set window, and everyone can see where everyone is on an actual map with directions built in.
A shared album carries the photos. Google Photos shared albums let anyone in the group add photos to one place, and because it’s tied to an account people already have, there’s no separate signup for anyone to skip.
A notes doc or spreadsheet carries the plan. Whatever the group already reaches for, a shared doc for the itinerary, a sheet for the day-by-day, it’s flexible enough to hold anything, from a packing list to a running set of restaurant links.
What each one is genuinely best at
Each piece of that stack is, on its own axis, better than a bundle will be. WhatsApp is a full chat app with voice notes, calls and reactions; a trip board that’s deliberately not a chat will never replace it, and it isn’t trying to. Splitwise is built to track a balance across years and multiple groups, not just one trip, so a running tab with the same friends outlives any single trip’s ledger. Google Maps has real turn-by-turn navigation and live traffic; a location share built for a single trip’s window doesn’t attempt that and shouldn’t. Google Photos shared albums aren’t scoped to a single trip either, so if a group wants one running album across every trip they’ve ever taken together, that’s what it’s for. Each tool wins its own job because winning that job is the only thing it has to do.
What the stack costs
The cost of running five specialists shows up as context switching, not as any single app being bad. The plan lives in the doc, but nobody checks the doc, because the conversation happens in the chat. The expense gets logged in Splitwise, but half the group forgot to open it because the reminder to pay came through WhatsApp instead. Someone asks “where is everyone” in the chat because the location share from that morning already expired and nobody thought to restart it. None of these are bugs in any one app. They’re the tax of five tools that don’t know about each other, and it’s a real cost that grows with the size of the group and the length of the trip.
Photos are the clearest case: they get taken on five different phones, shared into three different places, some to the album, some just dropped in the chat and scrolled past within a day. By the time the trip is a memory, the actual photo record is scattered across whoever remembered to upload where, which is why where the photos land is worth deciding before the trip rather than after it.
What a bundle gives back
A bundle trades some of each specialist’s depth for one thing the stack structurally can’t offer: everything tied to the same trip. Log an expense and it’s attached to this trip’s ledger, not a running account that has to be filtered. Share your location and it’s this trip’s map, ending on a timer rather than a share someone has to remember to switch off. Upload a photo and it lands in this trip’s album, GPS stripped automatically, not a chat thread someone has to remember to also copy into an album later.
manzil is built around that trade specifically: one trip holds the plan, the expenses, the photos and the location share, closing together when the trip ends instead of scattering across five apps that each kept their own copy. It won’t out-navigate Google Maps or out-chat WhatsApp, and it isn’t trying to. What it’s for is a group that’s tired of the fifth app being the one nobody opens.
Picking the shape that fits your group
Neither shape is wrong. A group that already runs a tight stack and doesn’t feel the switching cost has no real reason to change; five best-in-class tools genuinely beat one generalist on any axis you measure alone. A group that keeps losing the same photo, missing the same expense, or asking “where is everyone” in the chat because the location share expired is feeling the cost of the stack more than the benefit of any one piece in it, and that’s the group a bundle is actually for. manzil is invite-only for now, so trying it means getting a code from someone already on it, worth knowing before you point a group there. The useful test isn’t which app scores highest on a feature list. It’s to think back to the last trip and name the thing that actually went wrong. If nothing did, the stack is working and there is no reason to touch it. If the same photo, the same expense or the same “where is everyone” comes to mind every time, that’s the switching cost talking, and no fifth specialist app is going to fix it.