|
 Originally Posted by innocentbystander
I'm really really worried that the Touch To Share APIs won't be opened up until it's much too late. Much like the microphone APIs. Imagine only having TTS on homebrew apps for a year until Palm finally gets their sh-t straight.
Quoted for truth. One of HP's biggest must-dos is definitely providing the developer community with the APIs they want. The App Catalog would probably be a bit bigger than it is now if Developers had had API access to the camera and microphone, among other things (I understand that the media indexer API has been a problem in the past, for example).
If developers can bake Touch-To-Share into all of their apps, it's gonna be a fantastic feature indeed. If they cannot use Touch-To-Share because of a missing API "to be released in the coming months", that would severely cripple the feature's basic potential, which is so huge it can scarcely be overstated.
A lot of people don't understand the concept of a continuous client just yet... but having the option of touching your phone against your tablet / PC and being able to take whatever you were doing with you is a true revolution in how we interact with computers because you are, in a very real way, no longer forced to interact with a computer to get to your content - but interacting with your content irrespective of which computer you're using to do it.
But yes - they'll need to release the API for it. A feature is only really a feature if it can be used by people. For example, people were laughing when Apple released the 3GS with a compass (I was laughing as well). The laughter would have been justified if the compass had just been a compass app - useless for most people in most situations - but it had an API attached so a lot of useful apps and new features in old apps followed.
|
|
|