Booking apps look simple in a demo. A user picks a slot, pays, gets a confirmation, and everyone moves on. Then production happens: a provider in Berlin edits availability while a customer in Singapore is mid-checkout, a payment webhook arrives after the user has already closed the app, and the push notification that should have said "your session starts in 15 minutes" lands an hour late.
If you are the engineer asked to build a two-sided booking marketplace in Flutter, this post is the design review I wish more teams ran before writing the first widget. It is based on the Flutter booking app guide for marketplace founders published by the team at Journeyhorizon , reframed for the people who actually have to ship the thing.
Why Flutter is a reasonable default here
Let's get the framework question out of the way, because it is rarely the hard part.
One codebase, three targets.β¦