If you’re hungry for a good bite, we recommend ordering something off Uber Eats. But if you’re hungry to start building software without needing to write code, we recommend using Bubble’s cutting-edge visual development tool.
Our powerful platform is revolutionizing how everyday people can build software, making the path to building an online business more accessible. Our customers are using Bubble to build portfolios, marketplaces, and even social networks.
In this article, we’ll walk through the process of building your own meal delivery platform - without touching a single line of code. If you’ve ever wanted to replicate your own version of Uber Eats, Seamless, Postmates, or Doordash, this no-code tutorial is perfect for you.
Throughout this guide, we’ll highlight how to build the following key features for your no-code Uber Eats clone:
To get started, you’ll need a Bubble account (sign up here - it’s free). We also recommend completing our introductory lessons, which will guide you through the step-by-step process of the most common Bubble features. This will help you get a running start when building your no-code Uber Eats clone.
We also recommend understanding how to create and edit user accounts. We’ve previously covered how to create user accounts in Bubble in great detail.
When kickstarting your project, you can choose to begin by wireframing your product design, or building the necessary fields within your database.
In this case, we’ll start by using Bubbles visual design tool to shape the user-interface of our product. As we’re replicating a code-free version of Uber Eats, some of the core pages we’ll need to include are:
A major feature within Bubble is the ability to send data between pages. This allows you to create one generic version of a page, then dynamically display the relevant content from your database when it’s required.
In the case of your Uber Eats template, you’ll only need to create one page to host your individual meals. We can then build the necessary logic to display only the relevant meal details on each page when they’re required (we’ll cover this in more detail soon).
Once you’ve mapped out the display of your product, you can focus on creating the necessary data fields to power your application. We’ll rely on these fields to connect the workflows behind your product.
Bubble’s pre-built database streamlines the process of creating different data types with unique fields. To build the underlying logic for the core features listed above, we’ll need to create the following data types & fields:
Data Type: User
Data Type: Meals
Data Type 3: Restaurant
Data Type 4: Delivery contractor
Now that you’ve structured both the design and database for your application, it’s time to start stitching everything together - making your product functional.
In Bubble, the main way to do this is with “workflows.” Each workflow happens when an “event” occurs (e.g. a user clicks on a button), and then runs a series of “actions” in response (e.g. “sign the user up,” “make a change to the database,” etc.)
To display content on your platform, you’ll need to first add new entries within your database. Within Bubble, there’s two ways to accomplish this.
If you’re the sole moderator of your product, you can manually add a new entry in your database to the relevant fields.
As an alternative, it’s possible to also build a separate page into your product where you can visually add submissions using input fields. We cover this process in more detail here.
Once you’ve started submitting meals into your database, you’re ready to display each item in a feed on the homepage. This can be achieved by utilizing our repeating group element.
Repeating groups integrate with your database to display and update a list of dynamic content.
When using a repeating group, you’ll need to first link the element to a data type within your database. In this instance, you’ll classify the type as a meal.
You’ll also need to set the data source as a list of all the submitted meals from your database. If you’d like to segment each repeating by a relevant category, you can even add an additional constraint to your data source.
Now you’re ready to start structuring the dynamic content that will be displayed within this grid.
Simply map out the first column with the relevant content you’d like to show, then this powerful element will populate the remaining columns based on your existing data.
When using a repeating group, it’s also possible to create events within each individual column.
This feature will become useful when building navigational functions across your platform. As the Uber Eats homepage only displays an overview of each product (including its name, image and price), you’ll want to display the full meal details for each unique item on a separate page.
This additional content will need to be hosted on your individual meals page.
To power this event, you’ll need to start by creating a workflow that redirects a user to your product page when the meals image is clicked.
When creating this workflow, use a navigation event to send a user to another page. From here, select the destination page type to be the meal page.
You’ll then need to send additional data to this page so the Bubble editor knows which specific product to display. The data you’ll need to display is that of the current cells meal.
It’s also possible to use our search bar element to help navigate through the pages of your application. If you’d like to learn more about this powerful element, we’d recommend reading this guide.
When a user is directed to a specific meal page, you can easily pull this event data from your workflow to display the relevant content.
Before we create this workflow, you’ll first need to ensure that the destination page type matches the data property that you’re sending through your event logic. In this case, you’ll need to set the meal page to a meal property.
You can now start adding dynamic content into your page elements, displaying the information from the meal that has been sent in your workflow.
Using Bubble, it’s possible to harness the power of several free plugins to easily accept payments and process orders.
In this guide, we’ll be using the Stripe.js plugin to process credit card payments through Stripe.
Note: After integrating this plugin, you’ll need to first configure your API keys within the plugin settings.
When accepting payments, you’ll need to build a checkout interface that allows users to add their credit card details. For the sake of our MVP, we’ll be adding these relevant fields below the purchase button. Within your product, you could add these elements to a pop-up or even a separate page.
You’ll also need to include a Stripe token element next to the payment form. This element won’t be visible to your end-users, but is essential to powering a new transaction in Stripe.
When the buy button is clicked, we’ll then create a new workflow that triggers a Stripe payment.
You’ll begin by selecting the event ‘convert card into Stripetoken A’. Within this event, you’ll need to configure your input fields to match Stripes payment structure.
Once a card has been converted into a Stripe token, you’ll then need to create an additional workflow that automatically processes this token from a user's bank account.
Using the ‘Stripe.js - charge - create’ event, you’ll verify the Stripe token, as well as the final amount to be paid (including the currency).
If you’d like additional guidance when building your payment processing workflow, you can watch a full tutorial in the video below.