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 flutter pub publish --dry-run command does not publish the package. It just tells you which files will be published and whether there are warnings or errors. This is a good starting point when you decide to publish a package to

A package published in must contain an open source license. The Flutter team recommends the BSD license, which basically grants all kinds of use without attribution, and releases the author from any liability. It's so short that you can actually read it (which is a miracle in itself).

The LICENSE file in the package project is where the text of the license is placed.

Another extremely important file for your packages is the file. This is the main content that users will see on your package home page. It uses the Markdown format, which is a markup language that you can use to format plain text documents.

In the example shown above, we used three formatting options:

  • # area: The single # is a level 1 heading (the...