How We Built the Superapp "Dealer Online" and What Came of It
summary
A Flutter-based case study of building a multi-module superapp called “Dealer Online,” focusing on repository structure, monorepo organization, and navigation tools. The talk explains choices for state, dependency and navigation management—reworking patterns from MobX, GetX, Flutter Modular and GetIt—and demonstrates a practical approach for organizing dependencies and state in a large Flutter superapp.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:30Need for a superapp
- 5:10Dealer app definition
- 8:24Modular architecture choice
- 10:10Monorepo problems and fix
- 13:28Module structure and types
- 17:51UI Kit and resources
- 19:40Feature modules organization
- 20:01Host app role
- 21:05Navigation and Aro package
- 22:49Screen logic separation
- 23:34State manager issues in Flutter
- 25:00Dependency containers implementation
- 28:55Widget extensions
- 31:33Summary and recommendations
- 32:38Q&A
related talks
34mModular Flutter App Architecture Answering the What, When and How
44mMultimodule Flutter App
41mSuper apps: wanted a skateboard, built an aircraft carrier
34mBuild reactive mobile apps with Flutter
37mBuilding scalable, maintainable and robust apps in Flutter
37mLessons learned from crafting an in-house framework
22mArchitecture First: Foundations for Long Term Success
46mBuilding a SuperApp: Lessons from merging multiple apps into one