Report
How I built a MVP in 14 hours
Explore how the EaseMyInjury AI project was built using NextJS, TailwindCSS, Firebase, and OpenAI's ChatGPT4. Learn about key tech choices, tools, and lessons.
joaoaguiam.com
In this blog, I share the process of developing the EaseMyInjury project, utilizing NextJS, TailwindCSS, Firebase, Trigger.dev and OpenAI's ChatGPT4 on top of the ShipFast boilerplate. I also share my main takeaways to be able to ship MVP faster.
User feedback all the way, Joao.
Kudos on shipping such a polished initial version so quickly!
That's perfect, im building now my saas, im too close too finish, haha i thought im breaking a record because i took only 30 hours.
But well done, keep the good work.
But question if i may ask, what's the recording tool you used in the video you posted in X ( Twitter ) ?
Thanks! I used the tool Screen Studio.
I love the idea of using a boilerplate. I recently switched from rails to next.js and firebase for my personal projects.
Trigger.dev is something I haven't checked out before either. I've been looking for a good job runner for react.
I'm checking out DevJoy right now since they have integration with firebase.
I appreciate the article and recommendations!
Welcome!
I am really like Trigger.dev, very easy to use/setup and it lives inside your code so you can use Firebase as if you were on a server component. If you need any help just reach out.
Thank you so much for this!
It is indeed a very efficient way to build MVP capabilities. It fully utilizes open platforms and templates and selects the fastest solution.
This is pretty inspiring. Good job!
When you have failed multiple project building a new mvp of a project will just take hours. That is the power of having coding skill and keep trying. Something will get better.
The only mistake that people often make mistake when building one is overthinking about it. You want to add this feature that feature and thinking hard on what you are missing etc.
My rule for building MVP is if i need to think hard about a certain feature that means it is not important for mvp. Just get your first version out first and then add feature on daily basis at least you wont be missing any customer looking for your product and also with the mvp you can already start marketing.
Here a guide on how to mvp quick : How to build a MVP: Focus on what user want
I am stuck right now deciding whether it's worth the ~6 months to teach myself this next.js/tailwind/firebase stuff - or whether it is more valuable to teach myself a nocode tool like bubble.
bubble will get me functioning prototypes more rapidly - I won't get stuck as much. But I hate their pricing scheme, it is damn expensive to pay that much whilst you may be pre-revenue.
self-coding will be a good skill & hopefully mvp's will be more easy to resell/exit or scale. But it's a long slog, I may get stuck & not know what I'm doing.
I dunno what's worthwhile/more efficient
If you are not in rush I would recommend you to learn it. Because there is a certain that your project will fail and you need to build a new one so having the capabilities to build one without thinking about cost is really valuable.
Maybe you can try this approach, while learning how to use next ( which if you have basic coding 1 month is more than enough ) , you can do market validation, post blogs, daily twitter post, reddit post get email of your potential customer etc.
PS: If you want to do blogging I want you to try out my automated seo research tool creativeblogotopic.com . The tool will analyse google search and give you the best title and keywords to use on blog to get more traffic for your specific niche and target customer
I'll check it out. Yeah the market validation/blogs/twitter/reddit stuff is where I really would want automated
Coding is totally worth the effort. Not only as a life long skill, but it helps you understand what a no-code program is doing in the backend, making it easier to solve problems faster.
coding is worth it. Lifelong skill.
I can't tell much about no-code tools. I tried to use some in the past, but as a developer, I quickly find myself limited in the possibilities and always tend to go to directly to code. Maybe as well because I have a learning curve for those tools. I prefer to use more low-code tools like retool than really no-code tools.
But if you have some time to dedicate to learning coding, it's definitely worth it in the long term.
Congrats, action taker ⚡️