The Future of the Mobile Internet
Wednesday's post (along with Enrique's comment) got me doing even more thinking about the future of the mobile internet. What we need is a courageous browser manufacturer to take a leap into the brave unknown like MS did with the XMLHttpRequest object and create a DeviceRequest object. This object should allow you to query local device features/functions via a standardized JavaScript API which returns either a XML document or a JSON object array by default. Something like the below code example. Now that would be *very* cool and it doesn't even sound that difficult!
var user_contacts;
var device_request = new DeviceRequest();
device_request.get("CONTACTS", "") = function () {
user_contacts = eval("(" + device_request.response + ")")
}
};
~Comments~
~Add Comment~


It's already been done... www.5o9inc.com We have a set of Open API's which can link your program and any OS API and then become part of the browser httprequest headers. It wasn't that difficult, the hard part was the contextual menus which are added to the browser menu via web services.
Hi Peter,
I am advocating an open, non-proprietary, standards based approach to accessing device information through known and accepted web development technologies like HTML, DOM and JavaScript. While your solution is certainly interesting it doesn't meet those criteria. I want someone like WebKit or Opera to do this and then bring it to the W3C for standardisation. In order to be truly effective it must be universally and consistently implemented. If not, we just face more annoying and detrimental fragmentation.
HMM...sounds to me , that is at least 3 years after, that what you hope is finally adopted and implemented, Jason
Pls.. tell me about notes on future of mobile internet