We’re really happy to announce that Bugfender 2.0 went live in last quarter – a long awaited release that brings many feature requests from our users. We’d like to take this opportunity to thank you all for your feedback. It’s truly invaluable and helps us to improve Bugfender every day. As some of you may be aware, the service experienced some occasional down time during June.

A common practice in any development team is to conduct code reviews, or at least it should be. This is a process where multiple developers inspect written code and discuss its design, implementation, and structure to increase quality and accuracy. Whether you subscribe to the notion of formal reviews or a more lightweight method (such as pair programming), code reviews have proven to be effective at finding defects and/or insufficiencies before they hit production.

We created this resource to solve one basic problem: Once you go through all the work of building an app, how can you be sure to nail the landing? In the rush to get an app out, many developers can forget to tag releases or lose depository information that simply needed to be earmarked for a future update. There are some final security measures that need to be taken to protect your app. Whether it’s due to excitement or fatigue, it happens.

In today’s world of readily available apps, whether on your phone or a cloud service, consumers do not expect a lot of training before starting to use them. Apps are designed to be intuitive and lead you through them in the way that you would expect them to work – as it relates to the purpose of the app. Same is true with analytical applications. The best ones are intuitive – they look familiar and are intuitive to navigate.