Since the I-Phone’s release, the “general public” has been switched on to mobile computing in a new way. Previously expensive, high end, “smart phones”/mobile-devices were marketed to business users and geeks. Now the landscape has changed: devices are springing up from many manufacturers and Apple’s App Store model is popular across the board.

It seems logical that, as these devices become more widely used, the way users interact with web services will incorporate the mobile platform as a core method of interaction.

Next time I’m building a new service that needs to be accessible on multiple platforms I think it would make sense to build an API before a website. Until recently I’ve planned projects around browser based distribution, now the browser may become less dominant.

Having useful services open to many developers over an API will aid proliferation of the tool. Developers would be free to provide the applications for the various platforms (as Twitter have done, I suppose that’s why the next step on from “hello world” is becoming the Twitter client on many SDK tutorials). I know this is nothing new, but as mobile becomes more embedded into daily life: the way developers build services on the web will need to shift to accommodate it.

This isn’t really a “proper post” more of a stream of consciousness; I’m about to make the shift from Web Developer to Mobile Developer and am very excited about the new possibilities.