The Day I Rejected Flutter and Still Couldn't Explain the Android Framework
Android 16's recreation behavior hits every UI stack equally, because the host Activity is still an Activity; engineers who can't trace which layer owns a bug end up gambling on gray release instead of locating it in an hour.
When Android 16's large-screen configuration changes start recreating Activities by default, a health app's report page loses in-progress notes and double-submits. The immediate fix is moving state from an async callback into saved state. But the deeper realization hits during a review meeting: the author's own argument against rewriting the page in Flutter rests on platform capabilities like PdfRenderer and memory clearing, which Flutter can't replace - yet they couldn't articulate which layer actually decides an Activity's fate.
The article untangles the word "Framework" into two meanings (system source vs. app architecture) and maps a single fold event across six observation points, from user perception to AOSP source. It shows that switching UI stacks only replaces the top two of six layers; lifecycle, permissions, insets, and system services remain. A Channel call is similarly dissected into six places, proving the bridge isn't free.
The core argument: Flutter and Framework are different asset types, not competitors. Flutter's declarative mindset transfers to Compose and other UI, while Framework knowledge is about understanding the platform as a state machine. The author proposes three questions for any stack decision, a twelve-item platform capability checklist, and practical learning paths starting with L1 verification actions, plus measured numbers from a real Add-to-App case.
Platform contracts are getting finer while abstraction layers get thicker; the leaks in the abstraction are exactly where someone who understands the contract is needed, so switching frameworks doesn't eliminate platform knowledge requirements.
Flutter's most portable skill is the declarative rebuild mindset, which carries over to Compose, SwiftUI, and React; the framework-specific API details depreciate quickly.
A judgment based on a single 2019 performance observation was treated as a permanent law for six years; re-testing old conclusions against new engine changes like Impeller is more valuable than chasing new frameworks.
The numbers commonly cited in hiring debates count unrelated things: developer surveys, app store analyses, vendor self-reports, and job descriptions; none individually supports a career decision.
Responsibility for platform behavior rarely appears in job descriptions; the person who can trace a crash to the right layer is the one people find on release day.
Upgrade risk is driven by four unsynchronized version lines (targetSdk, AGP, Kotlin/Compose, Flutter SDK, and third-party SDKs); separating them into individual PRs reduces the variables in any single failure.