The F.. Word

4 min readJan 23, 2020

Competition is good

Context:

Flutter happened, everyone started to buzzing about it. Decided to look over spec, wait a year or two and if customers will start asking about it than look at it without any prejudgments. Is possible? Let’s see.

Switching technology should not be as hard?

Switching project is as hard as switching technology 2–3 days max 1 week to understand 80% of components and tools and concepts, and 20% is Nuances mastering it which are not visible at the beginning and will come up in daily year job.

Let’s start from code

flutter/flutter

Flutter makes it easy and fast to build beautiful mobile apps. - flutter/flutter

github.com

I have sources lets run it

Set up an editor

You can build apps with Flutter using any text editor combined with ourcommand-line tools. However, we recommend using…

flutter.dev

My daily job requires Android Studio.

Installation succeed I can create new Flutter project

Downloaded opened samples and hit run.

Error had install missing Pie SDK

Hit run again, nice

Changed icon and it hot reload, ok nice.

Let’s put something than Icon I don’t know components so IDE will help me

No it will give all, so I need learn components.

Visual Studio Code have few helpers for wrapping components:

I will need to switch to VS CODE and learn more about VS Code tricks.

Jump to deep water

Will go for more advanced samples and see it will go there

Run

Derived samples look amazing, but let’s edit one

Looks readable 500 lines of making UI and 200 delivering data

Summary

First impression on code:

Upsss I’m not as fast and flexible as I expected need go threw basics.

My Mind and habits and eyes will have to switch:

many }}}}}, const,”…” and syntax ?

How to i18n in Flutter?

After some months (maybe a year) working with Flutter I want to start sharing advanced things about Flutter like state…

dev.to

load of new commonest to learn it not just other tags but a all new logic for making UI (It is NOT my loved XAML)

Tools, Android Studio is ok, my eyes are used to VS so later will use Visual Studio Code
Tools, Android Studio is ok, my eyes are used to VS so later will use Visual Studio Code
Architecture: loved by enterprise MVVM is not recommend, it’s a big mind switch
TODO: How to bind native controls, background tasks? Is Kotlin required?

To sum it up it a main thinking switch if you ware able to imaging UI just by looking on XAML and fluent in MVVM , and you are use to tools than you will little more time to adapt.

Links: