Building Simple Web and Mobile Apps
From idea to running app
The build workflow is consistent across web and mobile: model data → build screens → wire logic → secure → test → deploy. Start by defining Entities and their relationships (one-to-many, many-to-many). Then create Screens with Widgets (Form, Table, List, If, Button) and bind them to data via Aggregates or Data Actions. Add Server Actions for business logic and Client Actions for UI behavior. Apply Roles and screen permissions. Finally, test in the integrated environment and deploy.
Concepts to master
- CRUD pattern: Create (Form + CreateEntity action), Read (Aggregate + Table/List), Update (Form pre-filled + UpdateEntity), Delete (DeleteEntity with confirmation).
- Forms and validation: Built-in validators (Required, Email, etc.) and custom validation in actions. A trap is assuming client-side validation replaces server-side validation; it does not.
- Reusable UI: Blocks encapsulate UI and logic; use them to avoid duplication across screens.
- Navigation: Web uses links and screen navigation; mobile uses stack-based push/pop.
- Testing and debugging: Use the built-in debugger, inspect variables, and check logs for runtime errors.
Traps to watch
Questions often ask which element performs a task. Remember: Aggregates read, Server Actions write, Client Actions handle UI, Blocks reuse UI. Another trap: confusing an Entity attribute with a Screen variable - they are different scopes.
Rule of thumb
"Read with Aggregates, write with Server Actions, react with Client Actions, reuse with Blocks." Apply this mapping to any build-pattern question.