Analysis paralysis (or paralysis by analysis) describes an individual or group process where overanalyzing or overthinking a situation can cause forward motion or decision-making to become “paralyzed”, meaning that no solution or course of action is decided upon within a natural time frame.

I have often be guilty of this, expending my energy, over thinking and evaluating all the pros and cons of doing something INSTEAD of doing it.

A quote that has been living rent free in my head recently: “It is easier to steer a moving ship than one thats docked”. Rather than thinking about whether to start/doing something, actually starting WILL get you further.

In the past I’d have spent weeks doing my research on the best way to get something done, to create the perfect app/platform etc. Given the reality is that there will be an audience of one for the app I am going to build for myself, really there is no pressure out there to perform. It should be a fun learning experience for myself over the next few days!

Best case scenario: I get something working and it marries with my goal of Macro counting (with ease) and I pass the challenge.

Worst case scenario: Nothing gets build, I lose my rep (a bit) with my accountability sponsors and close friends I’ve informed about my endeavour.

So what? As Akuma says – it is the path not to goal. As long as I enjoyed myself and learnt something new, it is time well spent.

Platform choices

Without overly complicating the choice of where to build on, a quick run on Google suggest that Flutterflow and Firebase was the right place to finish this challenge. I gave it a go on Flutterflow and saw some merit in the generative AI prompt driven samples it was able to generate.

The goal here is to be as frictionless and painfree for the creator as much as possible so we are not going to be a Nazi about code perfection or best practices. As long as it works!