HTC on Thursday announced it will soon launch the HTC OpenSense software development kit (SDK), which aids developers in creating apps designed specifically to interact with HTC's Sense software.
HTC Sense is the company's custom graphical user interface, built atop the Android platform. Since HTC is competing with other manufacturers like Samsung and Sony Ericsson — all three of which ship phones using the Android platform — Sense's custom interface acts to differentiate HTC phones from other devices.
Instead of having the stock Android interface, for example, the company's hardware comes with HTC's version of many common apps. On an HTC phone, Twitter is re-labled as “Peep,” for example. Menu screens also come pre-loaded with things like an HTC-branded media player, calendar and contacts apps.
“As the devices become more and more alike, manufacturers will do anything they can to differentiate themselves,” Gartner research analyst Ken Dulaney told Wired.com in an interview.
The OpenSense SDK looks promising. HTC says developers can create apps which utilize the stylus pen for HTC's new Flyer tablet device, as well as the stereoscopic 3-D display. If HTC lures more developers into creating apps that interact with Sense, that means more content available specifically for HTC devices. And that gives potential customers more reasons to purchase HTC-made products.
Software developers are the lifeblood of mobile platforms. Without them, places like Apple's App Store or the Android Market would be devoid of content. It makes sense, then, for smartphone manufacturers to court developers, drawing them to a specific platform.
HTC's approach of inviting programmers to code apps for its smartphones is a stark contrast to Motorola's relationship with developers. On the same day that HTC made its dev-friendly announcement, rival manufacturer Motorola had a few less encouraging comments regarding the apps coming from the Android developer community.
At a technology conference on Thursday, Motorola CEO Sanjay Jha deflected questions on the battery life of his company's products, placing the blame on the apps rather than the hardware.
“For power consumption and CPU use, those apps are not tested,” said Jha, referring to Android's “open” policy of not vetting applications submitted to its Market. Google removes apps that violate its developer distribution agreement, but no system of evaluating an app's power efficiency exists on the Market's side. Jha went on to say that 70 percent of Motorola's device returns are because of applications affecting performance.
Whether or not Jha's comments are accurate, it's a dangerous move for a company head to pass the buck over to quality issues related to apps on the Android Market. Apps, of course, provided by the developer community.
A Motorola spokesperson did not immediately respond to a request for comment.
Jha took the opportunity to make a plug for Motorola's own custom graphical user interface, Motoblur. Jha said Motoblur development is advancing to the point where it can warn users how much battery a given app will use. Depending on how much power there is left on the phone, you'll then be able to decide whether or not you want to run the app.
Two companies, with two very different approaches to drawing attention towards its graphical interface, with two very different effects on developers.
On a tech blog, commenter Daniel McDermott's opinion summed up the response to Jha: “It's insane to think Moto would pass on the blame of their crappy skin on to other 3rd party devs when they can't even get their own phones right.”
source: Gadget Lab
