Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Is the Lawsuit Against Android Affecting Developer Interest?

DZone's Guide to

Is the Lawsuit Against Android Affecting Developer Interest?

· Mobile Zone
Free Resource

Discover how to focus on operators for Reactive Programming and how they are essential to react to data in your application.  Brought to you in partnership with Wakanda

1,800 cross-platform mobile developers who use Appcelerator's Titanium utility said that they're not worried about Oracle's lawsuit against Android according to a survey taken two weeks ago.  Scott Schwarzhoff, who was once an independent developer himself and is now Appcelerator's VP of marketing, released the survey today and DZone had a chance to talk with him about the results.  

"Developers are a savvy bunch, and they're looking right through it [the Oracle lawsuit]," said Schwarzhoff.  "This is a battle between two titans - you have a 115 billion dollar company suing a 150 billion dollar company, and they both have a collective interest in seeing Android succeed."  93% of the 1,800 respondents said the Oracle lawsuit has little or no impact on their enthusiasm for the Android platform.  

There also weren't many developers who were on the fence about iOS and decided to join their camp once Apple decided to allow third party tools.  Although I'm sure there's a bunch of Flash developers jumping on board, the Titanium crowd had 83% say that Apple's change of heart did not affect their enthusiasm (or lack thereof) for the platform.  Schwarzhoff says that these larger issues don't seem to affect developers as much as new version releases and changes in OS capabilities.

Apple and Google Compete for TV Platform Developers

A new area that this survey looked into was the competing AppleTV and Google TV platforms.  44% of respondents said they were very interested in developing for Google TV while 40% were interested in Apple TV.  72% of the respondents said that Android is "best positioned to power a large number and variety of connected devices in the future," but only 25% said the same for iOS.  As a result, 59% of those polled favored Android's long term outlook versus iOS, which had 35% in favor of it long term.  "These operating systems that started on the phone, moved onto tablets and now are moving into connected TVs," said Schwarzhoff.

However, iOS continues to dominate this poll in the tablet and smartphone interest.  91% are very interested in the iPhone and 82% are interested in Android phones.  Respondents also thought that iOS had the least amount of platform fragmentation (74%) while Google was widely seen as fragmented (only 11% thought Android was the "least fragmented).

Prioritizing Native Featuresd

One final interesting addition to the Appcelerator survey was a ranking of the most crucial nativized app features:


1)       Native user interface (91%)
2)       Local database (81%)
3)       Push notifications (74%)
4)       Web services/Internet connectivity (71%)
5)       Geo-location (69%)
6)       Facebook integration (65%)
7)       Google maps (62%)
8)       Twitter integration (60%)
9)       Camera support (58%)
10)    Filesystem (56%)
11)    Application analytics (54%)
12)    iAd (52%)
13)    Audio/Video playback (50%)
14)    iOS in-app payments (49%)
15)    PayPal payments (48%)

Enthusiasm was strong for the upcoming Android tablets, but few developers from Appcelerator's respondents cared about the immanent BlackBerry and webOS tablets.

Learn how divergent branches can appear in your repository and how to better understand why they are called “branches".  Brought to you in partnership with Wakanda

Topics:

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}