Book Image

Flutter for Beginners - Third Edition

By : Thomas Bailey, Alessandro Biessek
5 (2)
Book Image

Flutter for Beginners - Third Edition

5 (2)
By: Thomas Bailey, Alessandro Biessek

Overview of this book

There have been many attempts at creating frameworks that are truly cross-platform, but most struggle to create a native-like experience at high-performance levels. Flutter achieves this with an elegant design and a wealth of third-party plugins, solidifying its status as the future of mobile app development. If you are a mobile developer who wants to create rich and expressive native apps with the latest Google Flutter framework, this book is for you. You’ll start with the basics of cross-platform development frameworks, specifically Flutter. You’ll then explore the Dart programming language which is the foundation of the Flutter framework. Next, you’ll get a feel for Flutter and how to create your first app, followed by an exploration of the various popular plugins that supplement the Flutter framework. Finally, you’ll explore testing and app release, including some common glitches that you may experience. By the end of this book, you’ll be well-equipped to create and release a basic Flutter app along with gaining a solid understanding of the Flutter framework and Dart language.
Table of Contents (20 chapters)
1
Part 1:Learning the Core Concepts
6
Part 2:Building a Basic Flutter App
11
Part 3:Turning a Simple App into an Awesome App
15
Part 4:Testing and Releasing Your App

Common issues

Sometimes, your Flutter run or build will fail, and often, this is related to plugin issues. In this section, we will look at some of the common issues and give some hints on how to resolve them.

Plugin breaking change

When a plugin changes its major or minor version number, it can mean that there has been a breaking change and that you will need to make some changes to keep the plugin working correctly.

There are generally two reasons for breaking changes:

  • A change in the way you use the plugin at a programmatic level. For example, the constructor parameters for a widget have changed, or the order of method calls to the plugin needs to be modified. These are often simply notified via compilation errors and deprecation warnings.
  • A required change in the configuration of your project. These can be less obvious and checking the plugin’s README on pub.dev is often the best way to assess whether you need to change your project configuration.
  • ...