We talk to a number of developers and ask whether they like Androids, or Apple's platform best.
If you ask developers which is better, the iPhone or the Android, they’ll give you a strong, resounding “It depends.”
Writing applications for two different platforms poses significant challenges but developers say the differences between iPhone and Android can be summed up into three key areas: ease of development, speed of approval for apps and of course how much money you can make selling the apps.
Ease of Development
Coding language plays a big role in how easy it is for a developer to work on both iPhone and Android platforms says Anders Brownworth, who has developed Voice over Internet Protocol-related apps for companies such as bandwidth.com. “If you have a Java background, which most developers do, then Android is best for you. iPhone is coding Objective C – it’s an older language, but you can get up to speed. As a developer you have to remember stuff like in Java the system garbage collects for you while with iPhone you have to do it on your own,” he says.
The iPhone’s major development advantage is hardware uniformity. DoApp, a third-party developer of branded mobile apps on Android and iPhone for newspapers, has worked extensively on iPhone. Its senior excecutives agree with Brownworth’s assessment of the different coding languages, but say having one phone to deal with is a plus. “An advantage on the iPhone side is it’s one device. There are going to be 16 Android phones on the market, that makes for a very fragmented situation,” says Wade Beavers, CEO of DoApp.
Brownworth agrees. “If you’re going to put a couple of buttons on the screen you know it’s 360 pixels high for Android, some are 640 pixels, your interface may include multiple copies of the same button image. ”
Alex Moazed, CEO of Applico, which develops applications for the iPhone, Blackberry, Android and Windows Mobile, says this is a bigger deal than one might think. “I’ve done projects where customers need Android apps upgraded and it requires three different screen sizes etc. Your costs add up in terms of backwards compatibility.”
Developers add that if you’re a new developer you’ll need to absorb the cost of buying a Mac as well as a PC if you want to work on both platforms.
Speed of Approval
Once developed your app must be approved and that’s where Android phones tend to shine. ”I just finished nine months of working on an iPhone app,” Brownworth says. “It’ll be two weeks maybe middle of January because of the holidays to know if it’s approved,” he says.
Beavers says Apple’s convoluted approval process and the sheer app volume delay the process. “One of biggest challenges you hear is you get an app denied and no one tells you why,” he says. “The process Apple has for denial and acceptance is very arbitrary. Unpublished API suddenly becomes non available, I’m telling you if a developer gets a call from somebody at Apple, that number goes into a lockbox to be treasured.”
Android is a different story. “With Android everything is accepted by default but they reserve the right to pull. You may be pulled from the Apple store too, but you have to pass some sort of unknown bar to get in then you may be pulled,” Brownworth says.
“We can’t give our client a specific date for approval,” says Dave Borrillo, CTO of DoApp. “Plus if you have a bug you can’t do a quick fix because of time lag. We have 200 apps, if we do a global change all at the same time, we send in the change and some get in and some we have to wait,” he says.
Developers could write Web apps to bypass the iPhone approval process as Peter-Paul Koch says, but even he agreed it isn’t a cureall.
Getting the Sale
Getting your app sold depends on the platform. Ben Kazez, president of Mobiata, makers of FlightTrack – a travel app available in both the iPhone store and for the Android – says Android’s ability to run apps in the background is big for his Android customers. “Running apps in the background is huge for FlightTrack,” he says. “You can get flight updates without interrupting what you were doing. We’re going to be adding integration features like a calendar that we can’t do on iPhone.”
But the iPhone app store is a gamechanger as far as some developers are concerned. A recent article on Wireless Industry News says, “On average, about 82 percent of those surveyed indicated the design of the Android Marketplace makes it very difficult for mobile apps to be noticed, and about 57 percent of the Android developers are not satisfied with the revenues generated so far.
Moazed says iPhone’s increased sales volume can be a negative for a small developer.
“For underdog developers, [the] iPhone store is also very crowded. It’s hard to get your marketing message out there. You can sometimes spend more on marketing than on development with the iPhone store,” Moazed says.
The Future
Although Moazed praises RIM for recent advances to Blackberry like their partnership with Adobe, developers say that Apple and Google will continue to vie for the number one and two spots in the market. “In 2010 it’s going to be all about two titans and it’s going to be iPhone and Android. I don’t think Palm Pre and Microsoft are even going to be in the market,” Beavers says.
Given that, Brownworth says developers looking to write for both should start with iPhone. “If I were to target both platforms for the same app I would write for the iPhone first, get the UI nailed first because the UI tools are prettier. Once you have an interface singing in iPhone it’s easier to go to Android.”
John Greaves is a writer living in Dallas, Ga. His work has appeared in newspapers, magazines and websites.
Check out Digital Trends Best iPhone Apps
Check out Digital Trends Best Android Apps
Showing 27 comments
RSSYour girl Mary :)
The following is meant to be constructive criticism and not personal.
The lawsuit dance tells me nothing other than to confirm that these are big stake games played by ruthless people who have no intention of missing any opportunity to protect & nurture their company.
Perhaps we should reflect upon the fierce nature by which IBM, QUALCOMM and Texas Instruments (TI) defend patents. They even make money at the whole process.
These companies like many other US companies who litigate are not selecting between innovation and litigation, they choose to do both: innovate and litigate. This idea of selecting 'A' over 'B' is known as the fool's dilemma and skilled businesses just don't do it.
As to who has infringed whose patents - there is a court system that will determine that. Anything else is just idle speculation. Of course, those with better insight and confidence can always look at how negative outcomes might affect stock prices and benefit from that. An ITC injunction on Apple would be have a significant even if final litigation shows no infringement. TSMC's recent win over a competing semiconductor firm shows the cost of losing and having worked at a company where injunctions prevented us from bring our product into the US for an extended time period are not isolate cases.
Perhaps we have forgotten that innovation is not a US right or unique to US. Our parochial view has resulted in us being late to the game in adopting mobile technologies (Asia leads Europe leads US). Motorola used to be a big player and lost to Nokia. While we're giving away products in the US (bandwidth, applications, etc), the SMS advertising business in Asia is a huge market that we ignore both in terms of extracting dollars there and leveraging it into a US business opportunity. To succeed in the global market, don't assume that a US view is the world view. (So it is probably not too surprising that many/most iPhone developers don't release products outside of the US market - I don't have exact numbers just impressions from talking with globalization/localization companies.)
Just some thoughts from an international business development person with a huge quota to meet.
I invest my time and money where I get a return. And I think that for most business people, it is unclear where/how the money will be made resulting in experiments.
Apple currently has 1st mover advantage, a loyal following and great infrastructure. Certainly the ability to reduce development overhead/costs with less fragmentation is a bonus. Push notification versus background processing will be decided by the market and the types of applications that make money. Apple has been able to work around many of the architectural / marketing limitations since the initial launch of the iPhone including no desire to support native apps if I remember correctly.
The closed versus open system is an issue. (Personally I truly hate not being able to change battery and SIM cards but I still own an iPhone in addition to others because of employer requirements.) When I looked at investing in some companies that wanted to do Made4iPhone hardware, I was surprised at all of the royalty touch points added by Apple and testing and lack of a transparent approval process. It is expensive to get into hardware and investors need bigger returns when risk is systemically introduced. There is room for opening the environment: the explosion of integrated circuits occurred because access to a broader people resulted in more creative products.
Google - IMO - seems to have the proven track record of executing the 'fast follower' strategy when they are behind. They too will have course corrections to make (is it sustainable to have such a fragmented platform a la RIM etc.) But they are a driven bunch of very creative people who should only be discounted at their competitors' peril.
I don't count RIM out, but they need to quickly get their act together.
But it is unclear that people are making money and the anecdotal information on the web seems to range from zero to a few thousands with some spectacular exceptions. That is for the iPhone. But these are early days and clever people will figure out that people will pay to solve problems that they want eliminated or to provide a new benefit.
Exciting times in progress and ahead
With 110 apps on the iPod Touch, mixture of free and paid, has been 100% maintenance, trouble free, and so easy, I rarely turn it off. I wonder is the tight control of the App Store partially responsible for this? If so, as an end user I support the control.
'