While each user will have their own habits when building on Bubble, the general approach is to start by establishing your application's visual structure, and then define the workflows that program it. The visual structure is going to be the set of core elements you need your users to interact with, such as inputs, buttons, etc. Workflows are a series of workflows, i.e. an event that triggers a series of actions. For instance, a click on a button is an event. That's why it's easier to think about these events once you already know which buttons and inputs are needed on the page. Another dimension of building on Bubble is the data structure. This entire chapter covers different key concepts in Bubble's application data structure. Lastly, it is very likely your app will rely on external services to function, such as payment solutions, data providers, etc. This is done through plugins.
It is usually a good idea to start drafting what your application will look like and what it will do on paper. Our experience shows it is worth the time to draw the few key screens on paper, with the necessary elements on each of them, and then draft the workflows, action by action. Once you have this, designing the actual application will be much faster and natural. Things you should ask yourself as you're thinking about your app include
How many pages your app needs. For instance, Facebook has a homefeed page, a home page when logged out, a profile page, a settings page (at least in an earlier version of Facebook...).
What kind of data your app will store. If it's a rental market place, you'll have, in addition to users, apartments, reviews, etc. An apartment will have an address, some pictures, etc.
How users navigate between pages, and under which circumstances.
Building an application is an iterative process; most users start by designing a wireframe of the page with the first elements and a simple layout, move to the workflow part to set basic behavior, and then move back to the design part as they have a better sense of the elements they need. As your app grows and you refine the product, add features, etc. you will also be modifying the design, the workflows and the data structure.
Because Bubble is very open-ended, you will very likely make some mistakes as you are building your application, as you would sometimes make mistakes in an Excel formula. This is part of the programming process. Bubble offers a few tools to help you debug and fix your application. There is also an Issue Checker that will help you identify data inconsistencies in your app.
Building is only one facet of Bubble's power. Once you have built the first version, you will run it with real users and real data. When your app is in production, i.e. used by actual users, you will be able to monitor it to make sure everything is working as expected. Again, Bubble has a few monitoring tools and logs to help you with that.
Some features may only be accessible on paid plans. You can review the plans differences here. All features are accessible in the Editor, but will not work in run mode if your plan does not allow the feature. A warning is usually displayed next to the feature if your current subscription does not cover it.
Please see the Account, Plans and Billing chapter for more details regarding applications plans.