5 articles from the engineers and strategists doing the work.
Oftentimes when building mobile apps, we want to front load data to avoid loading time in between each section of the app. Today, we will look at building a simple singleton cache in Flutter, and how using it can create a better user experience.
Dear Dev, One essay recommended to me early on in my career was “Object Calisthenics” (OC) and since that time I recommend it to every developer I cross paths with. “Object Calisthenics” describes a set of 9 rules credited to Jeff Bays in the book The ThoughtWork Anthology. The goal of these rules is to empower a developer to write cleaner, more maintainable code.There is a lot of value in being familiar with the OC rules, however there is also value in conversation with other developers, and hearing their opinions on the rules. I’d like to share my opinions over the Object Calisthenics ruleset.
In a previous article, I wrote about how separating Flutter views into distinct layers helps us create more robust and joyful mobile apps. If you missed that post, you can read it here: A Clever Way to Structure Flutter Apps. Today, I’ll build on that by walking through how I handle forms.
In a previous career, I was a software lead who wanted to build a highly performant group of devs. Doing so usually requires either a) hire several all-star developers, or b) develop a team from scratch for high cohesion, and then grow them into all-star developers. Due to budget constraints the latter strategy was chosen. Since the team was going to be primarily junior- and mid-level developers, I wanted to evaluate their skill in a code-agnostic way.
During my time building apps in flutter, I have found that online examples of implementations really boil down to two things. The two implementations I see most often rely on a Stateful Widget or a Provider to handle everything: updating the view, performing business logic, calling APIs, etc.
YOUR NEXT DECISION
Tell us what's slowing you down, what you've tried, and what needs to be different. We'll start there.
Come with a problem. You don't need a specification.
The first conversation helps define the next step, whether or not that step is with us.