Flutter Complete Reference: Create beautiful, fast and native apps for any device

This is the most comprehensive, well written book on Flutter available at this time. It has detailed table of contents and Index. The book covers Dart, the Flutter Widget Framework and Practical Flutter Examples. I would describe it as a technical reference book with examples, it is not a turtorial project based book. If you have a Flutter tutorial or already have some basic Flutter expereince but you just need a Dart langauge and Flutter Widget book to use as a reference then this is the book for you.The Kindle version does not have all the features available, it works more like a pdf file than a kindle book. It also does not support page links, so for example you cannot click on a refence in the Index to go to that page. The Kindle app does have a page search feature and so you can enter the page number from the index and it will open that page. Likewise you cannot click on a web link to open a web page to that reference. Also the book is not viewable on the Kindle Cloud Reader. Nevertheless, the Kindle version is useable.

I've only had the chance to spend ~6 cumulative hours reading this book so far, but have been very pleased with how well it's written and laid out. Whether you're a beginner or expert in Flutter, each section has applications and something to learn for both. Ideally, this book is to be used as a reference, not necessarily read start to finish. It's a little pricy, but can't complain given that it's fairly priced compared to other references and books in CS and Software Development.

I've always (at least since books of this ilk broke the $40 barrier) chosen to learn to programming tools using a little common sense and a good search engine. I think the last computer book I bought, other than "Java in a Nutshell," was a Palm Pilot programming book. With Flutter that didn't work out very well. Given any problem, there were 12 solutions out there, each one seemingly based on what the author figured out using whatever ad hoc method seemed to work. There was no consistency and it was maddening. So, I succumbed.The first section was about Dart, and I figured I could safely skip that. I decided not to and I must admit I learned things I had not known. So, my first recommendation, read it, quickly if you must, but there's a wealth of good information there.The Flutter sections (well over 500 pages) is a wonderful help and covers the latest features of the language. Areas such as state management and routes became clear, possibly because there were no conflicting examples, but the methodology presented works, and, as importantly, makes sense. Can things be dome better? I don't know (that's why I bought the book). But at least now I have a firm base from which to explore.The third section is full of useful, or at least interesting, examples and build upon the earlier sections. I haven't gone through them all (other than a quick read) but they seem to cover subjects necessary to anyone building non-trivial apps.I won't go into any more detail regarding the content. You can read the table of contents and, in fact, a large part of the early book. I am generally pleased with the work and feel confident that it was a worthwhile purchase.Now for the missing star. The grammar, while not bad, leaves a bit to be desired. But then, the author is Italian and his English is much better than my Italian. The author spends to many words pointing out differences with other languages (C++, Delphi, and, mostly, Java). Frankly, my dear, .... The physical book is a print-on-demand publication (the date on the last page is the date I ordered it). For me, the font is about a point or two too large. The programming examples are, fortunately, a Courier-type font. The left and right margins are only about 1/4in, which just feels wrongly annoying. There doesn't seem to have been any thoughts about layout; many of the coding examples, including those having only a few lines, inevitably run onto the next page. The book would have seemed much more professional had just these few issues been considered. It just feels like a large PDF file wrapped in a cheap cover. Which is my last point: I suspect this book will not hold up. As much as I prefer the heft of a book, with this one, having a chance to buy it again, I would consider the Kindle version, particularly since there are very few graphics. Actually, for the price, they ought to throw in the Kindle version, or at least the PDF.

This is sn excellent study and reference book every flutter developer needs.The layout is superb and no aspect of flutter is left out. It is easy to read and presented in a friendly and professional manner

THE BOOK IS BARELY OK BUT BEWARE!!!! I really really wanted to like this book. It is better than most of the pitiful Flutter tutorial examples on this site and elsewhere on the Internet. The author really tried to touch most of the subjects you will need to know about flutter in a business way vs. tinkering. The chapters subjects selected are good and flow well in terms of subjects with a couple of exceptions. The exceptions about chapter organization I would attribute more to my personal preference vs anything else.That's where the praise ends. As I dug more deeper into the Flutter vs. the Dart code examples, this book got worse and worse to the point where I had to try to skip ahead and go back to older sections just to barely get the code to work. Then as I got deeper in the book the author got plain lazy and did not finish code with no explanation. I'd get crap like Column(...) or children <Widget>[....] with no earthly idea what code should go there or whether the program will work that way.I finally got it that these were place holders for other code but the part that really made me angry was that this author did not give any indication which code went where when. He would give these type of examples, then switch subjects or talk about all the ways I should not code but NEVER COMPLETELY FINISH the example code he was talking about in the first place. At first I thought maybe I was skimming or not paying close enough attention to the lead in paragraphs for his code examples for flutter. No, its that bad and gets even worse the more of the book you read. I essentially put the book down and had to go back to scouring the Internet to complete concepts and coding examples this author lazily started and halfheartedly coded.In the end I got it. It hit me like a ton of bricks. This book is a massive cut and paste of other books with different chapters sourcing very much different references. The author or authors wrongfully assumed that subjects and code examples covered in later chapters was adequately supported by detailed information in earlier chapters. OR, they were just plain lazy and did not thoroughly review this book from the perspective of the first time or even lightly seasoned Flutter developer. This book should have been proof read more thoroughly and each coding example tested to ensure that it worked as expected. Giving me examples of bad coding while telling me all the reasons why bad coding should not be used is bad enough. Not giving me a working example is actually far worse than the bad coding warnings. I'd rather use bad code techniques that work rather than have some idiot telling me all the flutter coding pitfalls for two thirds of a chapter, then not practicing what he preaches.Lazy half a*** code examples seems to be the Flutter tutorial community's weapon of choice. ALL of them, including the flutter dev sight, seem to think that if they dismiss their responsibility for good writing away by saying, "hey you understand coding and OOP before attempting Flutter right?", they can get away with developing crappy incomplete tutorials. My answer to anyone reading this from that community (including this author) is yes, but that does not give you an excuse to be a lazy a*** and waste my time reading a tutorial that has incomplete, incorrect or very confusing code examples in it.Bottom line, stay away from this book if you are just now learning Flutter. Stay away from this book if you need learn anything other than high level theoretical concepts about Flutter. Do not go into this book with any expectations beyond a "what high level things could I do with Flutter". The coding examples are horrible once you get past the Dart tutorial. I am actually concerned there too but at least most of the examples worked.