Book Image

Flutter for Beginners - Second Edition

By : Thomas Bailey, Alessandro Biessek
Book Image

Flutter for Beginners - Second Edition

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, making it 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. This book will guide you through developing your first app from scratch all the way to production release. Starting with the setup of your development environment, you'll learn about your app's UI design and responding to user input via Flutter widgets, manage app navigation and screen transitions, and create widget animations. You'll then explore the rich set of third party-plugins, including Firebase and Google Maps, and get to grips with testing and debugging. Finally, you'll get up to speed with releasing your app to mobile stores and the web. By the end of this Flutter book, you'll have gained the confidence to create, edit, test, and release a full Flutter app on your own.
Table of Contents (18 chapters)
1
Section 1: Introduction to Flutter and Dart
6
Section 2: The Flutter User Interface – Everything Is a Widget
10
Section 3: Developing Fully Featured Apps
14
Section 4: Testing and App Release

Streams

As its name suggests, a Stream is simply a stream of data that your app can react to. For example, a stream is used to allow your app to respond to user authentication changes, which we will explore, in further detail, in Chapter 9, Popular Third-Party Plugins. That stream shares updates to a user's authentication status. To use the stream, you register to listen to the Stream instance and supply a function that will be called when there is new data added to the stream.

Throughout third-party plugins, especially Firebase plugins, you will see the regular use of streams so that the plugins can effectively call back into your code to tell you something has changed. They are very similar in concept to the use of a callback method, which is passed to the data source and called on data changes.

As a very brief example to give context to this idea, let's take a look at an example of a stream that gives updates when the weather forecast changes. Let's suppose...