HTML 5 Development Just Got Harder
Life in the technical field just changed, drastically.
The chasm between those companies who try and build systems to support others through HTML 5 (presently the ‘go to’ system to consider not building Apps specifically for iOS and Android) just got a huge awakening (I hope they realize).
One of the arguments for creating HTML 5 applications for most companies was to bypass the iOS AppStore (and Android to some extent). If a company can build a compelling, fast and user-friendly website without need for direct connectivity to the Operating System It is a huge win. The company has saved a considerable amount of development and anguish working to move the application through the (Apple) AppStore acceptance process.
However; if the world has finally been introduced to a working, fun and practical method of user interface extraction (AI voice control) and your HTML 5 application cannot gain access without becoming an App where does that leave you?
Grasping at straws.
I have no doubt that HTML 5 has a future, however; the obvious path to superiority was just given a smack down by Apple through the implementation with SIRI.
I have been wondering what Apple would do regarding the forward momentum HTML 5 had been attaining in response to their AppStore applications. While discussions on TWIT (www.TWIT.TV) discussed the better experience of using an application (especially Apple applications) I don’t believe that is ‘enough’ of an advantage to slow HTML 5 application growth.
However; while I considered many of the implications of SIRI regarding Sales and Marketing, I failed to think about how access to such an interface change would effectively blunt the effort to move to HTML 5.
Not any longer.
Momentum Swings back to OS Manufactures
The Mobile OS manufacturers have always had an advantage to offer those developers who create applications in their playground an advantage to those who use the browser as their means of accessibility, but I didn’t figure it was enough. I was thinking that the cost, annoyance and opportunities to keep 30% more profit (the typical cost of delivery through Apple and now Microsoft’s AppStore’s) would generate enough momentum for companies to get HTML 5 applications ‘right enough’.
Not any more. SIRI (and whatever Microsoft and Google come up with to counter SIRI) is the ultimate ‘requirement’ to force a OS specific application to be built.
The only one of the three companies mentioned above to have a significant reason to not use the AI as a carrot (or stick) is Google. Microsoft has spent huge sums of money into voice recognition and AI development over the decades and I believe that allows them to quickly try to blunt the SIRI effect and no compelling reason not to use Apple’s model of routing Applications through their AppStore.
Google, however; doesn’t care to push profit through the AppStore model. It is both their strength and greatest weakness to allow so many modifications to their system and it is much more open than either of the competitors. One could argue that with their purchase of Motorola we might have witnessed the eventual change in this attitude.
I will save the discussion regarding Google’s decision (allow web access to Android’s voice interface or not) for another time. Suffice it to say that 1 year ago I would lean towards Google ‘would’ try it, and now I believe they have a hard decision and could choose to not allow such functionality.
As for me and my Interface – I choose SIRI
Two years ago I used SIRI and fell in love with the technology even as limited as it was at the time. When Apple purchased SIRI I was very happy. When Apple didn’t ‘do’ anything with the technology for so…so… long, I was getting annoyed.
Today, the day after I have received my 4S (I pre-ordered at 6:00 in the morning when it was released) I feel confident that we are literally at the same point in history as when the first rocket was successfully launched into space and children started dreaming of becoming astronauts.
If there are options in the future for applications and one of those applications will interact with SIRI and the other cannot (not due to programmer’s ability, but rather due to no API (Application Programmers Interface)) guess which application I just chose?
Yes – the one I can talk to.
This might be SIRI 2.0, but it feels like a whole new world – welcome to the future whether you want it or not.