# Adalo beginner’s guide

Plan a first record workflow in Adalo and understand which parts of the 2021 crash course still apply to today's builder and the separate Ada beta.

- Canonical URL: https://adalocado.com/guides/adalo-beginners-guide
- Verification: Verified from current public evidence
- Topic: Getting Started
- Skill level: Beginner
- Last reviewed: 2026-09-21
- Index status: index-now

## Short answer

Start with the data your app needs, then create screens that display or change that data. In Adalo, components provide the interface, actions create behavior, and collections store records.

Start with one complete loop: a person sees a record, changes it, and confirms that the change persisted. Screens provide context, components provide the interface, collections hold records, and actions create change. This page uses a 2021 walkthrough for that mental model; it is not a click-by-click guide to today's responsive builder. Adalo also has a separate, limited-access Ada beta that starts from a prompt. Follow the path shown in your own account, and use current Adalo documentation for control names until the corresponding workflow has been reproduced here.

## Intended outcome

A mental model for planning a small Adalo app before committing to screens or database relationships.

## Requirements

- An Adalo account
- One simple app idea
- About 45 minutes if following the 2021 video

## Step by step

1. **Write the user’s job**

   Describe the one useful thing the person should accomplish. Keep the first build smaller than your full product idea.

2. **List the nouns**

   Turn the important nouns—Users, Events, Orders, Messages—into candidate collections. Properties describe each record.

3. **Draw the screen flow**

   Identify where someone starts, what list they browse, what detail they open, and what they create or update.

4. **Connect components to data**

   Use lists for groups of records, Magic Text for record properties, and forms or actions to create and update records.

5. **Test one complete path**

   Preview the app and complete one realistic journey before adding secondary features.

## Why it works

- Collections are tables, records are individual items, and properties are the values stored on those items.
- Screen data determines which record a detail screen can show. A link from a list item usually carries the selected record forward.
- Actions are the bridge between interface and state: they navigate, create, update, delete, or call connected services.

## Data model

| Collection | Properties | Relationships |
| --- | --- | --- |
| Users | Email, Full Name, Role | Has many records owned by the user |
| Example records | Name, Status, Created Date | Belongs to one user |

## Common failures

### A detail screen shows the wrong record

Check which record the link sends and confirm the destination screen lists that collection under Available Data.

### Magic Text does not offer the property you expect

Confirm that the current screen or component has access to the correct record or relationship.

### The original video interface looks different

Use the video for concepts, then follow current Adalo labels. This guide does not claim the 2021 UI is current.

### Your account opens the new Ada beta instead of the canvas shown in the video

Treat it as a separate workflow. Ada starts from a prompt; do not copy 2021 menu clicks into the beta builder. Review the generated data, screens, and preview before relying on the result.

## Testing checklist

- [ ] A new user can create, open, update, and revisit one sample record.
- [ ] The destination screen receives the record selected from the source list.
- [ ] The primary user outcome is written in one sentence
- [ ] Collections represent distinct kinds of records
- [ ] Every screen has a reason to exist
- [ ] One end-to-end path works in Preview

## Limitations

- The 2021 video is conceptual evidence, not proof of the current builder interface.
- The new Ada beta at friendsofadalo.adalo.com is a separate path; its complete first-app workflow is still being tested.

## Community evidence

### [A practical approach to structuring collections in Adalo](https://forum.adalo.com/t/a-practical-approach-to-structuring-collections-in-adalo/59756)

The guide recommends defining core objects as separate collections, keeping user roles explicit, and planning structure before building screens. Boundary: This is practitioner guidance, not an official product guarantee or an end-to-end test of this beginner project.

## Sources

- [Adalo Help Center](https://help.adalo.com/)
- [Adalo database overview](https://help.adalo.com/database)
- [Adalo: Responsive and Legacy Builders](https://help.adalo.com/design/legacy-builder)
- [Adalo: new Ada beta build guide](https://ada-help.adalo.com/ada/build-with-ada/)
- [Adalo forum: structuring collections](https://forum.adalo.com/t/a-practical-approach-to-structuring-collections-in-adalo/59756)

Markdown version: https://adalocado.com/guides/adalo-beginners-guide.md