Flutter first impressions

Here’s the simple app I wrote:

I understand that may not be a priority for the Flutter team but I’m afraid those issues can easily happen. On Android, a considerable part of the UI is written in the XML files, which forces programmers to separate (at least a little bit of) their UI and business logic. With Flutter, since everything is coded in Dart, I think we need to be a bit more careful to not violate these separation of concerns.

Another example: I found it very helpful to have a separate class file for strings, another for colours, another for routing, etc. But that was my choice. I could have been lazy and not done that. That could easily become a pain to maintain and refactor.

I wrote a very simple app and there were many topics I didn’t cover, but are still important on production-ready apps: local database, tools for crash reporting, analytics, advertising, etc.

Related posts:

The game of give and take And cooperative interaction Reflections on the lake The suns synergetic radiation. The birds and the bees And balanced harmony of nature The soft caress of breeze An…

White Hat competitive intelligence is a skill every product manager should have in their toolbox. There is no excuse for not leveraging competitive intelligence that is freely available on the…

When it comes to group work, people often fear of having bad teammates that they don’t like to work with. Therefore, it is important to know what kind of person other people would like to work with…