Book Image

Flutter Cookbook

By : Simone Alessandria, Brian Kayfitz
4 (1)
Book Image

Flutter Cookbook

4 (1)
By: Simone Alessandria, Brian Kayfitz

Overview of this book

“Anyone interested in developing Flutter applications for Android or iOS should have a copy of this book on their desk.” – Amazon 5* Review Lauded as the ‘Flutter bible’ for new and experienced mobile app developers, this recipe-based guide will teach you the best practices for robust app development, as well as how to solve cross-platform development issues. From setting up and customizing your development environment to error handling and debugging, The Flutter Cookbook covers the how-tos as well as the principles behind them. As you progress, the recipes in this book will get you up to speed with the main tasks involved in app development, such as user interface and user experience (UI/UX) design, API design, and creating animations. Later chapters will focus on routing, retrieving data from web services, and persisting data locally. A dedicated section also covers Firebase and its machine learning capabilities. The last chapter is specifically designed to help you create apps for the web and desktop (Windows, Mac, and Linux). Throughout the book, you’ll also find recipes that cover the most important features needed to build a cross-platform application, along with insights into running a single codebase on different platforms. By the end of this Flutter book, you’ll be writing and delivering fully functional apps with confidence.
Table of Contents (17 chapters)
About Packt

How it works...

The UI in this recipe is data-driven. The ListView widget (the viewqueries the Plan class (the model) to figure out how many items there are. In the itemBuilder closure, we extract the specific Task that matches the item index and pass the entire model to the buildTaskTile method. 

The Tiles are also data-driven as they read the complete boolean value in the model to choose whether the checkbox should be checked or not.

If you look at our implementation of the Checkbox widget, you'll see that it takes data from the model and then returns data to the model when its state changes. This widget is truly a view into our data:

value: task.complete,
onChanged: (selected) {
setState(() {
task.complete = selected;

When building the UI for each individual task, the State of these widgets is owned by the model. The UI's job is to query the model for its current state...