Flycricket

After 6 slow-going months (and another separate product launch), I slowly built Flycricket up to where I wanted it to be.

A ton of time was spent on the landing page, messaging, and pricing to make sure the idea was conveyed clearly. Some new features were added, and overall design was greatly improved for a more professional feel.

Now, it's time for round 2. I'm confident enough in the product to send it to a wider audience, but feedback will still be key.

I'm excited to have my first users on board!

Within a month, I had a very rough beta available. Looking back, the website was gross, the features were light, and the pricing was ???

However, it was enough to start talking to some fellow IndieHackers. I reached out individually and got some great feedback on the concept, what features they might like to see, etc.

After a couple weeks of this, I realized I wasn't ready, and went back to the development board.

I recently released an iOS app, and was driving some traffic to my website landing page. However, I noticed the download numbers didn't really budge. So I took a deeper look at the analytics.

Over 70% of my traffic was coming from the desktop, and I realized there was no Call-To-Action for any desktop visitors, and they were bouncing.

I realized I needed a way to allow users to easily download from any device, so I started working on Flycricket.