Comments on: Time for a Standard for Touch? http://gigaom.com/2009/11/16/time-for-a-standard-for-touch/ Thu, 23 May 2013 03:52:38 +0000 hourly 1 http://wordpress.com/ By: Ray http://gigaom.com/2009/11/16/time-for-a-standard-for-touch/#comment-230517 Mon, 16 Nov 2009 20:55:17 +0000 http://gigaom.com/?p=79868#comment-230517 I’m not sure standards designed to make developers lives easier would even be welcomed by developers. The key to success sometimes is to stand out in the crowd with something innovative and new; standards can make that difficult.

While standards can make life easier for hardware manufacturers (think Bluetooth, WiFi, etc.) when infrastructure and start-up cost can be high, that’s not true for software development. We can afford to let the market decide the direction of touch.

]]> By: Anon http://gigaom.com/2009/11/16/time-for-a-standard-for-touch/#comment-230516 Mon, 16 Nov 2009 19:03:12 +0000 http://gigaom.com/?p=79868#comment-230516 This is one of those ideas that at first seems like, “yes, that would be great,” until you stop to think about it and realize that it doesn’t make any sense at all in the context it is presented. It would be great if HP, Microsoft and Dell got their acts together and used a unified touch API on Windows instead of hardware manufacturers trying to lock developers into their hardware, but an API that also extended to Apple products? What exactly are you suggesting, a unified API for all Mac and Windows programming? The situation is even more complex when we start including smartphones and other devices, all with different capabilities, user interface conventions and operating systems.

Not to mention that a touchscreen interface on a desktop or laptop computer doesn’t even make sense in and of itself, except for kiosk applications.

]]>