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

Using generics

The <> syntax is used to specify the type supported by a class. If you look at the examples of lists and maps in Chapter 2, An Introduction to Dart, you will notice that we didn’t specify the type that they can contain. This is because this type of information is optional, and Dart can infer the type based on elements during the collection initialization process.

When and why to use generics

The use of generics can help a developer maintain and keep collection behavior under control. When we use a collection without specifying the allowed element types, it is our responsibility to correctly insert elements of the expected type. This can lead to bugs when data of an incorrect type is placed in a collection or incorrect assumptions are made about the contents of a collection.

Consider the following code example, where we have named a List variable placeNames. We expect this to be a list of names and nothing else. Unfortunately, without generics, we...