What Not To Do When Building Your Tech Stack: A Founder’s Postmortem

When we initially built boomering we decided to use a stack that would help us accelerate to market. Despite our best intentions, as a first time non-technical founder, I sucked at that. I’ll write a whole different post on that. Nevertheless, we did make it to market and our tech stack is as follows.

High Level Overview

This has worked quite well for getting us to market with an MVP. Flutter is a fantastic tool for rapid development and deployment. However, we did experience an issue where we were slowed down because our third party dev shop couldn’t find flutter developers. (Lesson in there) I am now learning Flutter and will be contributing to the code so we can move faster. Flutter is a powerful framework for getting to market. It is cross platform and it allows rapid testing and development. I have had a lot of fun learning it. Another area we had problems was we didn’t build out our data stack. (Another lesson). I have gone back to the drawing board on that as well, and will be adding in data and marketing tools to help build out our discovery and distribution. On the back end, we have had issues on caching images, but that is beyond the scope of this post. (Lesson…)

In sum, if I was starting over again I would do a lot of things differently. I would still use flutter. I would be far more involved in the technical aspects of the project. Instead of just managing designs I’d want to see the code, work much more closely with the developers. I’d prioritise a few things over many. We would have focused on time to market, app speed, and data analysis. Getting feedback is the most important part of any early MVP. I sucked at that, and am changing that now. Experience is a painful tutor, but a powerful one. In a future post I will write a guide to our new tech stack.