Pyro

The numbers from our MVP release convinced me to ask a friend from college to become my co-founder and start working on Pyro full-time. So we started developing the newest version. We published it just hours before New Year's Eve 2020. It took us around a month to build this new version because we had to rebuild almost everything from scratch. But the effort was worth it. The result looks great, is way easier to use and we've included a bunch of features, our early users suggested. Now we're off to launch our product on HackerNews, ProductHunt and do some Social Media promotions to grow our user base.

It took roughly one month to finish the first version of the app. To be completely honest, it was quite bad. It was laggy, didn't work reliably, and lacked a lot of important features. Nevertheless, it was enough to test the waters and see if there's a market for it. So I published it and simply waited while working on other projects. After 2 months, Pyro has gotten to around 200 active monthly users. Note that I didn't run any ads or promo whatsoever. This was purely organic traffic.

I was sitting at a party when I got the idea to build Pyro. It was the birthday party of an old friend from school and it went pretty well. Everyone was excited about the evening and in a good mood. Until the music started playing...
Guests were complaining, people left, nobody could change the music because the host's phone had a passcode. The day after I started doing some research on apps that solve this problem. I found a couple of apps that tried something similar but were either really really bad, hard to use, or had a very limited selection of songs to choose from. So I started sketching out an app that lets hosts easily set up collaborative music voting for their party by connecting their Streaming Service account directly. This is how Pyro was born.