© Frank Zammetti 2019
Frank ZammettiPractical Flutterhttps://doi.org/10.1007/978-1-4842-4972-7_6

6. FlutterBook, Part II

Frank Zammetti1 
Pottstown, PA, USA

In the last chapter, we began looking at the code of FlutterBook, the notes entity specifically. In this chapter, we’ll close it out by looking at the tasks, appointments, and contacts.

That may seem like a lot of ground to cover, but here’s the secret of why it’s not: if you compare the code for the four entities, you’ll see that they are probably 90% the same. The same structure is at play for all of them: a main code file (like notes.dart) and then a list screen and an entry screen, each in their own source files. The code in each will mostly be the same (or extremely similar) to that of ...

Get Practical Flutter: Improve your Mobile Development with Google’s Latest Open-Source SDK now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.