Mobile tech stack at Tide
summary
Tide runs a single monorepo with ~3 million lines of Dart split into ~400 packages to keep CI and codegen fast, serving 1M onboarded businesses and ~500k mobile sessions/day. Architecture uses a Lego architecture of self-contained feature packages (flow widgets + Bloc) with GetIt/injectable, Dio+Retrofit, freezed/resenteralizable codegen, Mason templates and Melos tooling. Tests are feature-level widget tests generated from Gherkin, golden tests for the design system, and CI only runs checks/tests for affected packages.
AI-written summary · about
chapters (13)
- 0:00Tide’s mobile tech stack intro
- 3:12Team structure & onboarding
- 5:21Monorepo & package org
- 7:28Codebase consistency & linting
- 9:55Design system & UI consistency
- 12:47Lego architecture for scale
- 16:47Dart code generation & automation
- 19:18Testing feature packages
- 23:53BDD widget tests with Girkin
- 24:58CI with GitHub Actions
- 27:29Release process & builds
- 28:33Production monitoring tools
- 29:59Summary
related talks
25mNative to flutter: A tale of Tide's transformation
39mImplementing Flutter at Tide
09mFlutter for Enterprise: How your company should be building with Flutter at scale
30mFlutter at scale-experience from 25+ Flutter Devs working together on a mobile banking app
35mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
37mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
34mProduction Fluttering
42mA fresh perspective on multi-platform UI