How To Apply Engineering To Flutter DevOPS

Yeah, everyone does that brief article of this how you get the tests in junit report format and this is how to do lint. How about I start from a more powerful flutter library stack and how those choices give us a more powerful Flutter DevOPS implementation.

First, I cover my Flutter library stack and why every choice was made both on the UI, code side, and the devOPS side. Then I will show the full-blown Flutter DevOPS set up.

Why A Flutter UI Stack

Well, the Google folks are developing 3 very different front-end SDKs and thus are somewhat stretched to the limits. That means it is very easy to get in stuck in that never ending Material Design spec evolution and how it is implemented in the Flutter SDK.

So, reason one is that we need the extra libraries, so we have some UX hooks that allow us to tell the brand story without directly relying on any specific Material Design feature. And at the same time, we also need to use additional libraries to address the holes in implementing the Material Design spec within the Flutter SDK.

And, on the devOPS side we have some things such as:

-localization without context as that makes some models easier to construct