Device Anywhere Gets Even Better

For a while now Japan has been a bit of a problem area when it comes to testing Mobile products and services. This is primarily down to the fact that Japan has it’s own proprietary network which is different to any other in the world. This mean the vast majority of Japanese devices (apart from those which are Dual-Mode with GSM as well) can’t be tested outside of the country.

To further complicate things Japanese carriers will also not allow Pay-as-you-go devices to create any type of Data connection so if you product depends on this then you’re out of luck and have to buy year-long contracts for every device you want to test. Needless to say this would be a huge cost and one that most companies would not be able to afford. What DeviceAnywhere has always done best is break down these kinds of barriers, initially with the US market, and now with Japan.

DeviceAnywhere have announced 4 new device packages covering all the major Japanese networks. These are KDDI, NTT DoCoMo, Softbank (formerly Vodafone Japan) and Willcom. So far there are 21 devices across the 4 Japanese packages and this is bound to grow every month. Now if all that wasn’t enough good news, DeviceAnywhere are making all the Japanese packages free until the end of April along with another new package from Bell in Canada. All you have to do is register and add the packages to your account and you’re all set.

In other DeviceAnywhere news, Mobile Complete have launched some new services to complement it. DeviceAnywhere Pro allows you to set-up automated testing (using scripts) for your product on any of their 1000+ devices. They can even offer a service that will do all the scripting for you. Definitely a service worth checking out if you have heavy loads of testing at regular intervals. DeviceAnywhere Monitoring allows you to monitor your service 24 hours a day and outputs reports which can include information like load time, error reports and other statistics.

So there you have it, more of you Mobile Devices testing needs solved, or at the very least made a bit more simple. For further resources check out these posts or just hit my posts tagged Developer.