Flutter Development

Flutter Architecture Studio

You will rebuild a community events app twice: once for clarity, once for throughput. Along the way you document architectural decisions that new hires can read cold.

8 weeks · measured

Cohort plus labs

KRW 512,000

Tuition is informational on this static preview. Enrollment confirmations arrive from staff after you schedule a call.

Schedule a call

Cover treatment for Flutter Architecture Studio

Lead mentor

Mika Alvarez

Consulted on Flutter launches for civic tools; cares about boring, legible graphs of dependencies.

What is inside

Router configuration with deep link fixtures
Riverpod scopes aligned to feature seams
Golden tests for layout regressions
Isolates for image decode without UI jank
Error surfaces that degrade gracefully offline
CI recipe using local-only actions
Localization workflow with ARB discipline

Artifacts you ship

A decision log with ADR-style entries
A second architecture branch with tradeoffs noted
A handoff README for future contributors

Cohort questions

Bloc instead of Riverpod?

Mentors will comment on Bloc-shaped patches if you prefer, but reference solutions stay Riverpod-first for consistency.

Web target?

Deferred. Mobile form factors anchor the assignments to keep scope contained.

What is skipped?

Desktop embedders and custom embedders are not taught here.

Notes from recent seats

“Router + provider story matched how we split modules internally. Golden tests felt tedious until week six when they caught a real regression.”

— Daeun · Hanbit Mobile Guild · Trustpilot

“Second architecture pass hurt in the best way—forced me to articulate why I kept a redundant layer.”

— Chris