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

There are two directories you can get with path_provider: the documents directory and the temporary directory.

Since the temporary directory can be cleared by the system at any time, you should use the documents directory whenever you need to store data that you need to save, and use the temporary directory as a sort of cache or session storage for your app.

The two methods that retrieve the directories when you use the path_provider library are GetApplicationDocumentsDirectory and getTemporaryDirectory.

Both are asynchronous and return a Directory object. The following is an example of a Directory, with all its properties, as it looks on a Windows PC with an Android simulator attached to it:

As you can see, there is a path string property that contains the absolute path of the directory that was retrieved. That's why we used the following instructions:

setState(() {
documentsPath = docDir.path;
tempPath = tempDir.path;
});

That's how we updated the...