Table of Contents

• Why Offline?
• Getting Started

Why Offline?

Building offline-first mobile apps provides the best user experience when steady bandwidth cannot be guaranteed. Brick's local cache ensures quicker round trip times by storing all data from Supabase locally. This reduces the time and expense of round trips, and even offers a third cache in memory for improved performance. Requests made while offline are retried until the app reconnects online, ensuring local state syncs with remote state.

Getting Started

1. Create a Flutter app.
2. Add Brick dependencies to your dependencies.
3. Set up directories for Brick's generated code.
4. Define models in Dart that match Supabase table columns.
5. Generate code for adapters and migrations.
6. Check and review generated migrations for accuracy.
7. Re-run adapter generation after every model change.
8. Interact with Brick's entrypoint to handle data fetching and caching seamlessly.
9. Run your app.