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)
16
About Packt

How it works...

When you create a new app with Flutter, the default package name is com.example.your_project_name. This must be changed before you upload your app to the stores. Instead of com.example, you should use your own domain, if you have one, or some other unique identifier. This package name must then be set in the AndroidManifest.xml file in the manifest node, and in runner.xcworkspace in the Bundle Identifier setting.


The iOS bundle identifier and the Android package name do not need to be the same; just make sure they are both unique in the respective stores.

When you change the package name in the AndroidManifest.xml file, you also have to update the MainActivity.kt file to avoid compilation errors.

The android:label property contains the name of the app that your users will see on their screen, so it's particularly important that you choose a good name for your app here. On iOS, you perform the same with thDisplay Name property.

Another setting...