Transitioning to Flutter App Development
Article Summary
Cherry Lu from Mercari shares her journey switching from embedded Flutter to standalone app development. The architectural differences were bigger than she expected.
Cherry, a Flutter engineer on Mercari Hallo's mobile team, spent two years migrating a native Android app to Flutter using the add-to-app approach. Now working on a standalone Flutter app, she breaks down the key differences in architecture, testing strategies, and development focus that caught her off guard.
Key Takeaways
- Standalone Flutter eliminates complex native-Flutter bridge syncing and mixed routing stacks
- Mercari Hallo uses go_router with StatefulShellBranch for clean tab navigation management
- Widget and golden tests replace traditional layer-separated unit testing approaches
- React-like architecture with flutter_hooks replaces MVVM's separate ViewModel and Repository layers
- Custom linter rules enforce Dart best practices like collection literals over map-toList chains
Moving from embedded to standalone Flutter means simpler project architecture but requires deeper focus on Flutter-specific patterns, widget testing, and React-like state management.
About This Article
Cherry Lu kept writing Kotlin-style map-filter-toList chains during code reviews instead of using Dart's collection literals and spread operators.
Mercari Hallo's code review process taught Cherry Dart best practices. She learned to refactor using collection literals with spread operators and embedded for loops, which made the code cleaner and more idiomatic.
Cherry started writing code in Dart's preferred style. This improved readability and consistency across the Mercari Hallo team as the team enforced standardized patterns in reviews.