Don’t Break Your Product on Launch Day

Hi everyone, recently I launched my product Coding Font. Today I wanted to share some learnings regarding my launch.

Write Launch Content Ahead of Time

This helps tremendously. On the day of the launch, we had all the launch content ready to go. My co-founder posted them on several subreddits and updated the posting throughout the day with how we were doing on Product Hunt. Having it ready to go also free us time to respond to comments and feedback.

Scheduling Tweets of Projects

A product launch is a 24-hour game – the sun rises at every hour in a different part of the globe. But I have to be away from my computer during certain hours to sleep. A new technique I tried this time is scheduling tweets with snippets (gifs or screenshots) of the project throughout the day to get on people’s radar. I think this was a very effective strategy in getting the project more exposure. It’s a method I plan to keep using for our next launch.

Don’t Break Your Product on Launch Day

The worst thing that can happen on launch day is going to sleep with a working product and waking up with none, which is what happened this time. Try to test and stress-test all the moving parts. Especially if you rely on a third-party API, make sure it can hold the traffic if the launch goes well. Many people only saw a broken screen and thought my post was a troll – it is more damaging than I initially thought. The app broke because it went off the Google Fonts API rate limit. In hindsight, I should not rely on the Google font API.; instead, I should self-host the data to minimize the risk.

Hopefully, with all the learning bagged, the next launch will be better than the last one. The post was originally published here if you want to see additional info regarding my product and launch.