!(https://hackernoon.com/hn-images/1*49JRIXl5TjmS9GWjlyr7Sw.jpeg)\n\nI've just submitted [Steady Calendar](https://www.steadycalendar.com), a minimalist habit tracker app, on the [Google Play Store](https://play.google.com/store/apps/details?id=com.manninglabs.steady), design by my wife [Irina](https://www.behance.net/irinamanning) and developed in short order by yours truly in the little free time I have being a new father. The app was a port from iOS to Flutter. After speaking about the experience ([slides](https://docs.google.com/presentation/d/1YQP7Qz1-4xRQWmOhwhswDTexmOl456RZPko45lhh-KU/edit#slide=id.gcb9a0b074_1_0)) at last week’s [Flutter Camp](https://flutter.camp), organized by @[flutterfyi](https://twitter.com/flutterfyi), I've decided to boil my talk down to something more meaty for everyone and make it a prelude to what an upcoming Flutter course, [Practical Flutter](https://mailchi.mp/5a27b9f78aee/practical-flutter), will be all about.\n\nWell, after writing this app, with little free time yet without cutting really too many corners, I wasted a lot of time with distractions on what I thought I had to learn about Flutter, which in the end wasn't very useful and was sort of time lost.\n\nSo with that said, here’s some advice for newcomers to Flutter.\n\n### 1\\. Keep it Simple When Getting Started with Widgets\n\nFlutter heavily uses [Material Design](https://material.io/design/) widgets in examples and throughout most of its library. If you want to quickly get a UI together or have no time to write an app for Android and iOS, stick to Material Design.\n\nYet the problem with Material Design is it may alienate your iOS users unless customized properly. Google has been [recently making efforts](https://www.theverge.com/2018/5/10/17339230/google-material-design-theme-update-new-tools-matias-duarte) to make its library more flexible and show how adaptable it is, encouraging developers to break out of boring, repetitive UIs that all just look like Google Docs.\n\nFlutter does offer “Cupertino” [iOS style widgets](https://flutter.io/widgets/cupertino/) yet this comes at the cost of needing to do some heavy code splitting, since these widgets require other [parent widgets](https://www.crossdart.info/p/flutter/0.0.32-dev/src/cupertino/scaffold.dart.html) to work properly. Plus, Google isn’t heavily focused on offering a full blown comprehensive set of iOS widgets, after speaking with one of it’s employees at a recent event.\n\nIn my next app, I will be customizing Material Design heavily to match design needs yet here are some of the widget you may want to learn for now to stay flexible and get the most out of your time:\n\n* [Scaffold](https://docs.flutter.io/flutter/material/Scaffold-class.html) and an AppBar (container for a screen and nav bar, respectively)\n* [Layouts](https://flutter.io/tutorials/layout/), with Column, Row\n* [Container](https://docs.flutter.io/flutter/widgets/Container-class.html) (ability to set ‘padding’, ‘decoration’, etc)\n* [Text](https://flutter.io/widgets/text/)\n* [AssetImage](https://flutter.io/assets-and-images/) ([NetworkImage](https://flutter.io/cookbook/images/network-image/) as a bonus)\n* RaisedButton (forgot icons for now)\n\n### 2\\. Forget Learning Dart From Day One\n\nFlutter uses [Dart](https://www.dartlang.org), a language that is very easy to pickup, even for folks new to software development. Yet getting an app running and rendering some simple UI does not at all require any Dart knowledge.\n\nAfter you’re comfortable with learning the basics of layouts, getting some content on the screen, then take an entirely separate day to read up on Dart. After that, you’ll be ready to learn things like handling events (i.e. tapping a button) and maybe even fetching data from an API, depending on your experience level.\n\n### 3\\. Stick to Stateless Widgets For Now\n\n‘StatelessWidget’ is the default class any Widget will extend in Flutter. As the name implies they are for rendering widgets that will not need to hold any state.\n\nIn terms of it’s counterpart, ‘**Statefull**Widget’, Flutter’s documentation presents this by showing how to say, handle an event and change some information that’s on a screen. If you’re a newcomer to programming or even a junior developer, learning this in the beginning is by no means required. I say this because in the beginning of learning anything, motivation is the key to keep going and your primary focus should be getting comfortable with rendering a nice looking screen with some content.\n\n### 4\\. Establish Some “Motivation Milestones”\n\nAgain, when learning anything, hitting some important milestones is key to staying motivated. Here are some of my recommended learning milestones:\n\n* Milestone One: Be able to develop a screen with a simple layout, text, a non-working button, and an image.\n* Milestone Two: Be able to run your app on your actual phone. This is very cool and really motivating.\n* Milestone Three: Learn how to hook up a button, change some state and render it on the screen by using a StatefulWidget.\n* Milestone Four: Take a few hours to read up on Dart (this step can even come before the previous milestone if you’d like).\n* Milestone Five: Be able to fetch some data from a public API ([examples](https://github.com/toddmotto/public-apis)) and render it on the screen. Understand how to work with JSON and deserializing it.\n* Milestone Six: Release an actual iOS and/or Android build to a friend. This will surprise you but I really believe in doing this early, unless you’re still evaluating to see if Flutter is right for you. Showing an app you wrote, even if it’s not at all useful, to friends and family and sending it out to a test user via iTunesConnect or the Google Play Store (easier) and doing this early on is the really an amazing way to stay motivated and confident that you can crank out an app to the public one day.\n\n### 5\\. Learn How to Get Help\n\nGet used to going to the [Flutter Google Group](https://groups.google.com/forum/#!forum/flutter-dev) if you can’t find an answer to a problem on Stack Overflow. I recommend the former over Stack Overflow when asking questions actually. You can read more advice [here](https://flutter.io/faq/#where-can-i-get-support).\n\nTry to find a few mentors that can help you as well. You’ll find the Flutter community is wonderfully engaged and passionate.\n\n### 6\\. Share Your Work\n\nI’ve found that Twitter is a great way to share what you’ve done. Even if it’s something simple, simply posting a screenshot of your app and mentioning @[flutterio](http://twitter.com/flutterio) is really motivating.\n\n### Final Thoughts on Learning\n\nOverall, in terms of learning resources out there, there’s a lot available yet I’ve found that there isn’t enough real, end to end, battle tested tutorials on Flutter out there. Sure there’s your Google-produced YouTube videos and Udacity courses and these are great, yet a lot of the time they cover 1/5th of what you’ll need to learn to get a real app into the app store(s). I say this because after writing a port from iOS to Flutter for a simple app I wrote, Steady Calendar, recently, I found that things like working with JSON, APIs, manging multiple build environments, localization, caching, code organization, state management, tweaking Material Design for really custom UIs, etc took some digging.\n\nSo with that, **I plan to release a beta Flutter course** which will take my experiences learning Flutter and boil it down to practical, more “end to end” type tutorials which will focus on Flutter and all the other know-how it may take to write a real app.\n\nIf you’d like to sign up to get notified when I release the first lesson in July ’18, sign up here: [Practical Flutter](https://mailchi.mp/5a27b9f78aee/practical-flutter).\n\nHappy Fluttering.