1
3 Comments

How I built my first solo MVP in 18 days

So I had my idea, what I didn't have was the necessary skills to execute it myself, or so I thought. I had some experience building small bits of software in my previous startup and my previous jobs, but I had never attempted to launch an entire application myself, the task seemed gargantuan.

While I was pondering this, I was listening to podcasts and reading books to absorb as much information on building as I could. I stumbled upon a podcast episode with Pieter Levels, who is of course a bit of a legend in this community. He discussed starting to build his own businesses and how he knew even less code than I did when he began. He simply googled problems and solved them as he faced them. I thought this was brilliant. Armed with the confidence that I could solve anything, I began.

Not quite abiding by the levelsio dharma, I decided to spend a few days learning about the stack I was going to build with, I think overall this is a more efficient approach to development, provided you don't overcommit to the learning. I decided to build on a ReactJS frontend with a Python API backend. I chose React because I felt it was the frontend framework with the greatest degree of community support. This meant the framework had longevity and every problem I was likely to come across had a googlable solution. I chose Python because after a couple of quick google searches it seemed to sensible choice for web scraping.

I watched a four hour youtube video on ReactJS to learn the basics and followed along with the tutorial, giving me a nice bit of sample code that I could refer to whenever confused. I then set about mocking up a simple frontend. I built a basic homepage with a search bar and a black background, then I built a results page with results loading in cards once they're received from an external source (my python API) . This whole process took me about 6 days.

Python I had used a little bit before so I didn't think the pre-learning was necessary. I simply googled my problems as I went along and read short articles explaining what I needed to do. I used BeautifulSoup to web scrape along with requests (wherever possible) and Selenium. About 5 days later I had finished with a simple synchronous version of the API, it scraped only 3 websites and ran entirely synchronously, but in 12 days I had finished my first ever solo PoC.

I then undertook the challenge of making the frontend look nicer (a dreaded task) and preparing the API for production. For the frontend I made the background of the home screen a bookshelf and cleaned up all of the display cards to show the necessary information. This took me 2 more days. The API was more challenging, I had to add more websites to the scraper and make the scraping system asynchronous, I had no idea how. I hopped between adding websites to the scraper and studying asynchronous programming in python, the endeavour made me begin to regret my choice of stack, but I was too deep to turn back now!

After opening and abandoning multiple ways of async programming I finally found an old way of implementing threading that I understood well enough to implement. The entire process took me 3 days of intense work.

Just like that I was done, I showed it to my family and friends and sought their feedback. I ended up listening to about 10% of the advice they gave me and implementing little things here and there to tidy the platform up. 18 days after ideation, I was ready to launch.

, Founder of Icon for Pages on Pages
Pages on Pages
on November 9, 2022
  1. 2

    Whoa, that you taught yourself how to code and built your first MVP so quickly is amazing and inspiring. I'm outlining my first MVP right now but I don't think I'm brave (or skilled) enough to build it on my own :( I also like the idea of having a partner. I thrive in collaboration! Am I thinking about this correctly or being too timid? Btw, though I work in book publishing, I'm constantly looking for cheaper book buying solutions (lol) so Pages on Pages is a godsend.

    1. 1

      Thanks! I appreciate the kind words. While collaboration can be great I think that reliance on collaboration is limiting. I believe you should be capable of doing everything yourself and collaborate only when you believe that there is a significant addition of value.

      Learning how to code and spinning up MVPs has never been easier than it is today. If you explain your MVP to a tool like ChatGPT it will explain how to do it, teach you which technologies you need, educate you on the essentials of these technologies, write most of the code for you, and even debug your code when necessary.

      I think you should believe in yourself and your own ability and try to get the MVP out yourself. If you give it your full effort you will be surprised how much you're capable of.

      1. 1

        Interesting... If I utilize a tool like ChatGPT, am I giving away a piece of my intellectual property? I'm building a marketplace, FYI. Do you still think I can code that on my own? I'm not a designer either, so my initial plan was find a coder Co-Founder and then hire someone to design a cool interface. I really appreciate the encouragement and insights. Thank you, Shashank!

Trending on Indie Hackers
7 years in agency, 200+ B2B campaigns, now building Outbound Glow User Avatar 105 comments How I built an AI workflow with preview, approval, and monitoring User Avatar 54 comments The "Book a Demo" Button Was Killing My Pipeline. Here's What I Replaced It With. User Avatar 45 comments I built a desktop app to move files between cloud providers without subscriptions or CLI User Avatar 26 comments Show IH: I built an AI agent that helps founders find the right people User Avatar 24 comments My AI bill was bleeding me dry, so I built a "Smart Meter" for LLMs User Avatar 20 comments