arch-atlas
Docs Atlas · Learning Path

Flutter Architecture, step by step

6 short chapters that teach Clean Architecture, GetX, and the organizational scaffolding that makes both look the same when you switch between projects.

≈ 2 hours total·read in order·open any card
  1. 01
    Start hereThe why behind every layer25 min

    Clean Architecture, deep dive

    Why Clean Architecture exists, the dependency rule explained from first principles, and how each layer earns its keep — with the bookshelf project as live evidence.

    7sections15snippets5checks
    Start
  2. 02
    Trace the cold start20 min

    One feature, end to end

    Follow the camera as one user action — 'open the app, see books' — flows through every file in the bookshelf project, line by line.

    8sections13snippets
    Open
  3. 03
    The other professional Flutter architecture25 min

    GetX modules done right

    Module pattern, reactive state, services, routing, offline-first writes — how the TINITEC sup_order app stays clean while embracing GetX's all-in-one model.

    8sections17snippets10checks
    Open
  4. 04
    Same feature, both architectures, side by side15 min

    Choosing & comparing

    A five-question decision framework + the same feature built both ways so you can compare directly. Pick on real constraints, not on familiarity.

    6sections2snippets5checks
    Open
  5. 05
    Keep this open while you codereference

    Cheat sheet

    The single page reference — both architectures, side by side, smallest viable code for every operation.

    8sections15snippets10checks
    Open
  6. 06
    Identical scaffolding across both architectures20 min

    Organizational patterns

    Asset paths, colors, theme, preferences, network info, splash flow, naming conventions — the scaffolding that's the same in CA and GetX. Apply identically to every project.

    10sections15snippets22checks
    Open

Already know the theory?

Skip straight to the visual reference. Every folder tree and architecture diagram from the docs, on one page. No prose.

When you finish

You'll defend each layer of bookshelf's code, add a new feature without breaking the dependency rule, and pick between Clean Architecture and GetX based on real constraints — not on familiarity.