Getting started
The path through these guidelines - from deciding whether add-to-app fits, to planning the migration, setting up the architecture and building your first Flutter screen.
Adding Flutter to a native app is four decisions in a row. Read them in order the first time; later, jump straight to the tier you need.
Decide whether add-to-app fits
Start with What is Flutter add-to-app? to see how embedding Flutter lets you adopt it gradually, without a full rewrite. Then check When should you consider Flutter add-to-app? - when it pays off, and when a full rewrite is the better call.
Plan the migration and the team
Planning the migration to Flutter covers picking the first screen, rolling out in phases, store review and the exit to a pure Flutter app. Organizing your team covers team shape, hiring vs upskilling and who owns the native-Flutter boundary.
Get the architecture right early
Read Core concepts first: Flutter engines, Dart isolates and platform channels sit under every later decision. Then choose how native and Flutter talk in Native-Flutter communication, and where the code lives in Project structure.
Build your first screen
To build with Inlay, follow Getting started with Inlay to wire it into a Flutter module and a native host, then add Navigation between native and Flutter screens. Not using Inlay? The architecture guidance above still applies directly.