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

With a script that takes just a few lines, you can literally save yourself and your team hours of work.

The first step in this recipe was adding the development team to your Xcode project. This is needed because signing the app requires a development team.

Then you generated an app-specific password. This is a password that you can use with your Apple ID and allows you to sign in to your account from any app. So, instead of using your main password, you can give access to other apps (in this case fastlane). In this way, when a security breach happens, you only need to remove the password that was compromised and everything else will keep working securely.

Each iOS app contains an Info.plist file, where you keep configuration data. There you put the following node:


The purpose of this node is to tell TestFlight that you are not using any special encryption tool within the app; some encryption tools cannot...