Paul Poutanen

December 7, 2007

WURFL - the Wireless Universal Resource File

One of the difficulties re mobile testing is trying to determine what a handset can do.

The people at WURFL (the Wireless Universal Resource File) have compiled an amazing database of handsets from around the world. (from their main page)

The main scope of the file is to collect as much information as we can about all the existing mobile devices that access WAP pages so that developers will be able to build better applications and better services for the users.

This project is open-source and is intended for developers working with the WAP and Wireless. All the information listed here has been collected by many different people from many different countries. You are allowed to use WURFL in any of your applications, free or commercial. The only thing required is to make any modification to this file public, following the original spirit and idea of the creators of this project. This will help WURFL to grow better and better every day.

Mob4hire is a proud contributor of data to add to the database. We have already found multiple examples of new handsets that we have added to the database.

We are using the WURFL database to identify handsets and will be using the database for the beta version of Mob4Hire which will be ready soon.

I salute the people and contributers to WURFL!

If you are a mobile application developer, please check it out.

November 28, 2007

More on Verizon openness

Filed under: technology trends, wireless — Tags: , , , , , , , , , — admin @ 7:20 am

Testing of handsets to make sure they make the grade can be tricky and political.

From business week this morning..

For starters, Verizon Wireless will need to test any new device model before letting it connect to its network. The degree of openness will hinge on how difficult Verizon Wireless makes it for products to get a green light. Columbia University law professor Tim Wu, a leading proponent of wireless open access, points out that the old Ma Bell-era phone companies often used testing requirements as a way to control their networks. “There’s testing requirements and there’s testing requirements,” says Wu. “One is routine—and there’s another thing of deciding what products they don’t want on their network. It can become a black hole from which products never emerge.”

Developers have to have a clear picture of what will be accepted and what will not be accepted. If a developer spends 6 months on a project and then finds out a carrier blocks them on a technicality because it does not meet their business needs, this will further close the whole system.

Further more if the delay in testing handsets amounts to months, the same objective has been fullfilled. 

Openness is like being pregnant. There is no half being pregnant.

Powered by WordPress