Traffic Android Blog

Had I spent my time just working on the next patch for the existing application, there would probably have been 2 or maybe even 3 new updates at this point, but as it stands, I ended up taking the plunge and diving straight into getting the web-based version of this system out as quickly as possible.

To those who have been waiting patiently for the new release, I apologise for the delay, but I believe what I am doing is worth it. Here are my reasons for converting Traffic Android into a web-based product:

• Piracy will cease to be an issue.
• There will be no further problems with people trying to get the application to run across a myriad of different system configurations.
• Mac users will finally get to use it!
• Your computer won’t have to be switched on for tasks to run; Traffic Android will be truly as set-and-forget as you need it to be.
• I can handle proxy support on the server side, meaning it will not be an issue users need to worry about.
• I can easily handle automated CAPTCHA processing, which means all tasks will become properly automated and thus schedulable, as opposed to just the tasks that didn’t require CAPTCHA input.
• I can deploy updates, quickfixes and new types of tasks as often as I want without having to think about it in terms of pushing out an application update which will generally always result in a new set of support requests.
• I’ll be able to charge a modest monthly fee which will provide me with the financial resources needed to maintain this as a high quality product indefinitely. (If you already bought Traffic Android, you get to ignore the monthly fee).
• I can roll out and test experimental advanced features while they’re still in “alpha” mode without having to manually send selected testers updates and files every time I change something.
• Utilising a proper server-hosted database makes it easier to support users who are very heavy users of the product.
• There are a bunch of high-end features I want to develop that are really only feasible if done from a server-based product.
• Web development is what I’ve been doing for over ten years, so it’s easier for me to develop and maintain a web-based product than it is a desktop product.

So what will happen to the desktop product? In all likelihood it’ll be scaled back as an introductory product and work similarly in scope to services such as OnlyWire, although just from the desktop. It’ll be a natural choice to upgrade from the desktop product to the hosted product. I may even release a simple free version of the desktop product in order to attract more potential subscribers. Nothing’s set in stone though.

Here’s a screenshot of the web-based product to tease those of you waiting with bated breath: