I’m planning to build a food delivery app using Bubble and would like some advice from the community. What is the best way to structure features such as restaurant listings, food menus, user accounts, cart and checkout, online payments, order tracking, and delivery partner management?
Also, has anyone built a multi-vendor food delivery marketplace on Bubble? I’d love to know how you handled database structure, workflows, API integrations, and scalability as the number of users and orders increased.
If you’re planning on doing live updates by showing a car moving on the map or something like that, I would say it could use a lot of work units and might not be the best idea.
Other than that, you can ask Bubble’s AI and get some feedback on the whole thing. Here is a post from Bubble that explains how they can help you:
Simple estimated delivery time is fine, but real time updates definitely not worth it.
Did estimated delivery time where driver logs to pickup, then check estimated drive time to drop off automatically via api and log estimated delivery time….hopefully people have enough patience these days for that to suffice.
but still, having drivers see requests in real time and accepting them, and having the rider see in real time that they had a driver, was too many work units.
Bubble is great for most apps, but in cases like I mentioned, it’s not.
Wouldn’t it just be cost of fetching for driver to see the requests, cost of update to request to accept and cost of individual item request for user to see request confirmed by a driver?
I mean, yes, not going to scale to be an Uber Eats on Bubble with WU costs, but to take a 15-25% commission on an Order from local restaurant could be justify spending 3-4 WUs per driver claim of an order.
I may not know enough about Bubble as you and others do…
but if there are 10 drivers that can accept jobs, and say 50 people at any given time requesting a ride, that would take refreshing the app at a minimum of every 5 seconds?
I played around with it all and couldn’t see how I could get it to be profitable.
Maybe, as I said, I just don’t know how to use Bubble as well as I should.
No need to refresh. If a driver has app open and is therefore already initiating a search of all jobs whose status is pending, then 15 riders log in and each create a separate ride whose status is pending, the driver doesn’t need to refresh the app to see those 15 new ride requests, since bubble searches get updated automatically unless develop does something that breaks that like using workflow actions to filter or sets search as static.
But, I do think a ride hailing app and a food delivery app are two completely different beasts…food delivery on bubble can be profitable, but I’ve never built a ride hailing app and I do imagine a ride hailing app would not be as easily monetized as a food delivery app.