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...

In the preceding code, we are calling the getData() method, but after that, we are adding the then function.

Note the following:

  • The getData() method returns a Future. Futures are generics, so you have the option to specify the type of Future you are returning; if the return value of a method is Future<int>it means that your method will return a Future containing an integer number. In this case, specifying the type is not required, so we could also write the following:
Future getData() async {

The preceding code would work just as well.

  • The getData() method is marked as async. It is considered a good practice to mark your asynchronous methods with the async keyword, but it's not required in this example (it is only required when using the await statement, which we'll see in the next recipe in this chapter: Using async/await to remove callbacks).
  • The http...