{"id":2853,"date":"2015-04-21T09:08:52","date_gmt":"2015-04-21T07:08:52","guid":{"rendered":"https:\/\/usersnap.com\/?p=2853"},"modified":"2025-08-29T19:20:32","modified_gmt":"2025-08-29T17:20:32","slug":"launching-bugtrackers-lessons-learned","status":"publish","type":"post","link":"https:\/\/usersnap.com\/blog\/launching-bugtrackers-lessons-learned\/","title":{"rendered":"Launching bugtrackers.io – Here\u2019s what we\u2019ve learned."},"content":{"rendered":"\n

Maybe you\u2019ve heard the news. We at Usersnap launched a little side project, called bugtrackers.io<\/a>. Displaying stories of digital crafters and showing real people behind pixels, bytes and bug reports. That\u2019s the vision for bugtrackers.io.<\/p>\n\n\n\n

Starting with three interviews bugtrackers.io went live on April 16th. Following some great feedback<\/a> on our social media channels<\/a> as well as through direct feedback, bugtrackers.io experienced a great start. Within the first 4 hours after putting the platform live, more than 1.000 unique visitors<\/i><\/b> stopped by and spent more than 5 minutes on the site<\/i><\/b> (average session duration: 5:02 min.).<\/p>\n\n\n\n

Although the launch just happened a couple of days ago, there are some fresh lessons learned we want to share<\/b>, since they might help you for your next project. Here are 6 things we learned when launching bugtrackers.io.<\/p>\n\n\n\n\n\n\n

Try Usersnap for Bug Tracking<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n

Inspiration through domain search<\/h2>\n\n\n\n

You probably know the following situation: you browse the web and discover some free domain which you think is pretty awesome. Because the domain may be valuable for you in the future, you buy the domain.<\/p>\n\n\n\n

Well, this is what happened when we came across the free domain bugtrackers.io. To be honest, we hadn\u2019t had a clue what we are going to do with this domain, but we knew that it may help us to position ourselves in the bug tracker scene.<\/p>\n\n\n\n

We definitely knew that we don\u2019t want to use the domain for any promotional or self-branding thing for Usersnap<\/a>, but use it for some neat new content idea instead.<\/p>\n\n\n\n

After a couple hours of brainstorming we found the idea of providing insights in people\u2019s life in web development pretty interesting and something worth to follow. Inspired by other platforms like thegreatdiscontent<\/a> and communicatebetter.io<\/a> we pursued our idea.<\/p>\n\n\n\n

From idea to design within 5 days<\/h2>\n\n\n\n

After this brainstorming session, I made myself comfortable with moqups.com<\/a> to work on some first scribbles.<\/p>\n\n\n

\n
\"Mockups_LandingPagenew_\u00b7_Moqups\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

As you can see these mockups were pretty rudimentary, although we had a clear vision in mind. Our amazing web designer Pavel<\/a> then drafted some first designs for bugtrackers.io which were then discussed within our InVision projects<\/a>.<\/p>\n\n\n

\n
\"design-draft-bugtrackers-launch-lessons-learned\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

See full design draft version 1 here: design draft bugtrackers.io V1<\/a><\/p>\n\n\n

\n
\"invision-design-discussion-bugtrackers\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n

Try Usersnap for Bug Tracking<\/h2>Try Usersnap Now<\/a><\/div>\n\n\n\n

You do not necessarily need a CMS<\/h2>\n\n\n\n

After concluding on a final design draft, discussions on which technological basis our platform will be built arose. Since our blog already runs on WordPress, it stood to reason that bugtrackers.io will be build on WordPress too.<\/p>\n\n\n\n

However there were some clear signs which let us decide against WordPress and any other content management system. In the end we choose to build bugtrackers.io only with HTML + CSS. Here\u2019s why:<\/p>\n\n\n\n