Another Reason I Love Qrimp

Posted: 8/21/2008 1:33:31 PM
There are many reasons I love Qrimp, but today I was faced with a problem that would have been much more difficult to solve without it.
A startup record label, Youthful Chaos, came to us a few weeks ago saying they were releasing the debut album for Bombazine Black called "Here Their Dreams." With traditional site development tools, that would be a really tight time line, but as you can see from the links above, it's already live -- nearly a week ahead of schedule and Youthful Chaos is taking orders now. The site includes PayPal integration and secure file download, management interfaces, content management and of course the flexibility to add a community, comments, ratings, and more albums in the future.

Beating tight time lines like this to build such a rich application is reason enough to love Qrimp, but that's not the reason I want to talk about today.

Today I'm going to talk about a little bug in some custom JavaScript that was causing problems with a couple browsers. Of course cross browser compatibility has always been a real pain. Solving them meant developing the site in one browser and moving over to another computer to test the changes. This process could take a very long time, especially if that other browser wasn't on site or the bug was happening somewhere inside some source code that has to be recompiled and redeployed to be tested.

Qrimp is 100% browser based so it helps developers solve cross browser issues much faster. Instead of going to another machine or browser to test changes, the changes are made using the very browser showing the compatibility problems. As soon as the test is made, refreshing the buggy page is all that is required to test it. There's no compiling and no need to redeploy.

Not only does Qrimp reduce the time it takes to get a web application up and running, but it also reduces the amount of time it takes to fix problems that arise later. The JavaScript problem on the Youthful Chaos site was fixed in a matter of minutes, not hours. The whole process of debugging, testing, and fixing the problem was done in a live environment and the change pushed out transparently to the customers. The site got better for the end user, but the site never went down.

So to fix this pesky JavaScript bug, I just went to the OSX partition of my MacBook Pro and loaded up the site. Sure enough, the bug was there. Using only a browser, I investigated, modified the JavaScript and some other deeper components that would have required a code change without Qrimp, saved them, and reloaded the page. Just took a minute or two. Bug gone!

That's just another reason I love Qrimp. I also love Here Their Dreams, you can buy it on the Youthful Chaos site. The album is $9.99 and you can download the MP3's immediately.