One of Bitovi's earliest, and most important, development strategies was the introduction of the "modlet" workflow. It's a very simple concept - every module should be developed as its own application. In practice, this means that instead of a folder structure where files are grouped by type like:

Bitovi is providing a public 45 minute JavaScript training every week. The trainings are for intermediate to advanced JavaScript developers looking to take their frontend skills to the next level.

UX designers have long used documentation as a means of communicating functionality and interaction for digital products. It has been successful for a long time and thousands of digital goods have been delivered using this process. However, as our industry evolves, so do our processes and tools. Documentation alone is no longer enough. And prototypes on their own, do not provide enough detail. Bitovi combines documentation with prototypes to deliver a comprehensive handoff experience and project archive.

Make sure you’re building the right user interface before you build it. The old adage, "Measure twice, cut once" applies to digital projects, as well.

In this post, I'll explain the value of having a user experience designer from the perspective of our own process at Bitovi.

I've been attempting to organize how Bitovi approaches web application development. I'd like to draw a line from what users and businesses value (quality) to the techniques and tools we use to build web applications. I've organized my thoughts into a mental map: