Which Builder.io product makes app screens?

Builder Code is the workspace for creating or changing app screens. Start from a description, a Figma design or a project connected to an existing code repository. Builder Content is a separate product for managing site content.

What happens between a preview and a live change?

Preview the edit in Builder Code. If your Git provider is connected, you can send a pull request, a proposal showing what changed in the app’s files. Someone can check it before it becomes part of the main project. Your existing release process decides when visitors get it.

What should you keep outside the editor?

Keep the accepted changes in the app’s repository. Make a separate list of the accounts, data services and content the screen relies on. For example, the signup page code can be in Git while the signup records are kept in a database elsewhere.

What can use up your plan allowance?

Builder Code’s pricing page lists both daily and monthly agent credit limits on Free. Compare the included credits and user pricing for paid plans. Check Builder Content separately if you also need people to edit site content.

How would you check a proposed class filter?

Sketch a filter for a fictional classes page and decide what a reviewer needs to see before it reaches the live app.

Choose two results
Pick a weekday with classes and one without. Show how the preview should look in each case.
Keep the next action working
Show what happens when someone clears the empty filter and signs up for a class.
Mark who reviews and releases it
Draw the preview, the proposed change in Git and the live page as separate steps. Give each step an owner.