Great UX And Good Enough UI

Something from Hacker News, What I learned from clubhouse:

https://anu.substack.com/p/what-i-learned-at-clubhouse-

Sparked an idea of how I can explain the Flutter Architecture and Design DevOPS I am creating and polishing off to show and have everyone who wants to, modify and abuse it. Remember, we are dealing with mature markets and the app has to wow the blokes who are using it. At the same time, it just has to have good enough UI-code and flutter-dart code to get the job done, as it’s not supposed to be Google perfect.

So the article title happens to describe in as few words as possible, but let me detail some examples that show what I mean.

Core of Clean Arch And Domain Driven Design

The core of both Clean Arch And Domain Driven Design while it differs in certain aspects has at its core connecting data interfaces to service classes as a way to abstract the API away from the implementation with the API being the API of the flutter app itself. But that comes at a cost of the time to code that boilerplate.

In fact, in some well known examples from some Google IO participants (GSkinner and VGV) you never see an usercase command pattern. And that is largely due to the fact that if you are using BLoC you already get model events through BLoC…