Traffic Android Blog

My apologies for the delay in updates. I know many of you are quite curious about the progress on the new version of Traffic Android. The new version of Traffic Android is due for release very shortly and will be made available in a few short back-to-back phases. Right now it in use by a private group of beta testers with good success so far. Next it will be released to a group of early customers who bought Traffic Android long before a web version was planned. Other customers of the $67 Traffic Android desktop product will also be able to get access earlier than most people. We’ll have a special deal for you if you are in that group. The details of that deal are yet to be determined though. After that we’ll launch the product on a broader scale.

Now, onto features and technicals, for those of you who are interested.

• Proxies have been a tricky issue. Due to the nature of the web and the potential number of customers that will be coming on board, the one-private-proxy-per-customer strategy has needed to be adjusted to avoid cost issues. What we’re going to do is be running on a public pre-filtered proxy list that rotates periodically, with a list of exclusive private proxies rented as a backup measure if the public proxy list ever experiences issues. With that in place, Tor will be investigated as a potential way to truly randomize the proxies we use.
• I’ve now got all the subscription code, account settings editor and billing history page in place, which were loose ends to tie up.
• Shortly we’ll be taking the desktop product off the market for the time being, as it will largely be deprecated by the web product and we need room to get a pre-launch campaign in place. This means that you can either add yourself to the mailing list (scroll to the bottom of any page on the Traffic Android website) and wait for an announcement, or you can buy the desktop product in the next few days as a way of getting a pre-release special deal. This may be in the form of a several-month-long free trial, or a slightly different subscription price. As stated above, the details are yet to be determined.
• I’ve put in a nice error tracking system so that if the system ever throws one of those nasty errors you normally see when the programmer screws up, the entire details of the error are logged to disk so I can go through them and see exactly what happened.
• As soon as I finish up the adjusted proxy code (which will be done within a few hours of this post), my next task is to go through and tidy up any loose ends, including a small but very important task involving making the actual task processing engine a bit more robust and less prone to the occasional error that I’ve been logging during the beta process.
• Finally, we’re going to be adding a bunch more services to the release product if there’s time, and will be adding lots more services in the short term in any case.

Bottom line, development on the new version of Traffic Android is very active and we’re gearing up for an important launch will boost the product’s profile in a big way.