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 way Flutter handles dialogs is fascinating in terms of its simplicity. Dialogs are just routes. The only difference between a MaterialPageRoute and a Dialog is the animation that Flutter uses to display them. Since dialogs are just routes, they use the same Navigator API for pushing and popping. This is accomplished by calling the showDialog or showCupertinoDialog global function. Both of these functions will look for the app's Navigator and push a route onto the navigation stack using the platform-appropriate animation.

An alert, whether Material or Cupertino, is made up of three components:

  • Title
  • Content
  • Actions

The title and content properties are just widgets. Typically, you would use a Text widget, but that's not required. If you want to put an input form and a scrolling list in a Center widget, you could certainly do that.  

The actions are also usually a list of buttons, where...