Learn how to build for Android, iOS, and the web from a single codebase with Flutter, the cross-platform UI toolkit from Google. Rather than listing concepts, this guide is organized so you can follow the content in the order you have to make decisions on a real project.
Key perspective
Frontend / app development
Do not stop at drawing the screen: look at state, data requests, routing, accessibility, and the unit of deployment together.
Cross-platform appsWidget-based UIThe pub.dev package ecosystemBuilding Android/iOS/Web together
Architecture diagrams
To make what you read stick, it helps to capture the flow as a picture first. The two diagrams below are reference maps you can keep coming back to while learning Flutter.
Learning flow
Rendering diagram…
Architecture view
Rendering diagram…
Install & create a project
When you first open Flutter, the big picture matters more than individual commands. This section starts with the problems the concepts ahead were created to solve.
flutter doctor diagnoses whether Android Studio, Xcode, and each platform toolchain are connected properly, so run it before your first build and resolve the warnings first. flutter run greatly speeds up development with hot reload, which refreshes just the UI while keeping the app state every time you edit the code.
BASH
# macOSbrew install --cask flutterflutter doctor # check the environment# Create and run a new project (with hot reload)flutter create my_app && cd my_appflutter run
Widgets & layout
Here you look at Widgets & layout alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
In Flutter everything is a widget. A StatelessWidget draws UI from its inputs alone, with no internal state, and layout is composed with Column/Row/Container.
Here you look at State management alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
The most basic state management is a StatefulWidget with setState(). When setState() is called, build() runs again and the screen is updated. As the app grows, extend it with Provider or Riverpod.
Here you look at Networking alongside real code. Rather than copying the example as-is, read it with an eye on the inputs, the outputs, and the parts most likely to change.
For REST API calls, the http package combined with async/await is the most widely used. The FutureBuilder widget lets the UI branch directly on the loading/success/failure states.
DART
Future<List<User>> fetchUsers() async { final res = await http.get(Uri.parse('https://api.example.com/users')); if (res.statusCode == 200) { final List<dynamic> data = jsonDecode(res.body); return data.map((j) => User.fromJson(j)).toList(); } throw Exception('Failed to load the user list');}
Flutter practical design
Flutter practical design is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.
Design Flutter with the widget tree depth and the rebuild scope in mind. Do not keep state high in the widget tree; narrow it to the scope that needs it to prevent unnecessary rebuilds.
Decision point
Question to ask
Practical guideline
Boundaries
Which parts of the Flutter code are most likely to change?
Separate input/output, configuration, external integrations, and the core rules.
State
Where is state created and where does it go away?
Make the owner and lifecycle of state visible in the code.
Failure
What does the caller receive on failure?
Decide the timeout, fallback, and error contract first.
Flutter operating standards
This section covers Flutter operating standards from a practical perspective. Instead of memorizing the concept, focus on the situations in which you would reach for it.
In operation you need monitoring of dropped frames (jank), image caching, exception handling for platform channels, and app size (APK/IPA) management.
Flutter verification strategy
Flutter verification strategy is a point where the options diverge. Using the table to compare what each approach is for and how it differs in operation makes later decisions much easier.
Verify all the way to real device scenarios with widget tests, golden tests (screenshot comparison), and the integration_test package.
Quality axis
How to verify
Definition of done
Correctness
Automate the normal/failure cases.
The core scenarios pass reproducibly.
Regression prevention
When fixing a bug, leave the same case behind as a test.
The same failure is not deployed again.
Operability
Check the logs, metrics, and alerts.
There is a path for tracing the cause when a problem occurs.
Flutter: frequently asked questions
What is the difference between Flutter and React Native?
Flutter uses the Dart language and draws the UI with its own rendering engine, so it looks the same on every platform. React Native uses JavaScript and React and renders with each platform's native UI components. Teams with web frontend experience find React Native familiar, and Flutter has the edge when consistent design and animation matter.
How do I choose between StatelessWidget and StatefulWidget?
A StatelessWidget draws only from the values it is given and has no state that changes on its own. A StatefulWidget holds internal state and redraws when setState is called. Splitting parts that need no state into StatelessWidgets narrows what gets redrawn.
Can a Flutter app use device features such as the camera or sensors?
Yes. Most device features are available as published plugin packages. For a feature with no plugin, call native code written in Kotlin or Swift through a platform channel.