views:

867

answers:

7

For those developers here who have tried both platforms and published some apps in their respective app stores, how have the results been for you?

Pros and Cons?

I'm curious on current real-world experiences, not analyst projections.

I believe this too will help people get off the fence and choose which side to develop for.

Thanks.

+1  A: 

I've got no experience with the Android platform, but I'm super curious.

I am an iPhone fan, but it's a state of the art "NO" platform because most of the answers to interesting questions are NO.

It's kinda negative and wearing.

However, coming from the iPhone, the idea of an open platform sounds
like a PITA. How big's the screen? How much RAM, etc. etc. I'll miss
the homogeneity.

Is this what Stockholm syndrome feels like?

Rhythmic Fistman
With Android, as long as you do layouts properly, they size for any device.
Isaac Waller
I do game stuff, which is intimately tied to the screen res.
Rhythmic Fistman
You're right, that is the one situation where it is much harder.
Isaac Waller
A: 

Without any experience of Android development, the pros of the iPhone are that it is a platform that does not seem to be fragmenting (i.e. different screen sizes, different hardware controls, different shells) and that it provides a significantly larger market.

Code is code: you should not select a platform based on minor differences in tooling or ease of development.

Roger Nolan
Do you expect the iPhone to forever remain in its current form factor? A single button and the same screen resolution? Maybe another 2 years and that's it?
Sebastian Dwornik
I actually don't see the iPhone form factor changing. The size is pretty good, making it larger or smaller makes little sense. And the pixel DPI is already very good, adding more pixels in the same space would provide very marginal benefits.Where we will see change is in processor speed, and abilities like camera/gps/compass (not to hard to predict since we see that today).
Kendall Helmstetter Gelner
+1  A: 

I'm currently looking into developing for Andriod/iPhone myself, the one major benefit I can see with Android is that you can develop on Windows and don't have to buy a Mac or run OS X on a VM to do it unlike with the iPhone.

Also with Android you only have to pay $25 (just the once I think too) to get your applications onto the marketplace.

Yes, you can spend $399 on a dev version of the G1 but there's a pretty good emulator too.

Quite rightly, code is code at the end of the day, but you also have to factor in development costs. Android is significantly cheaper, however there's a smaller user abse in comparison to iPhone users.

Think who you want to cater for with your app.

As far as real world experience goes, I can't say I've touched the iPhone SDk on the basis you have to pay for it before you can even glance at it where as Android is free and I'm playing about with it at the moment. It's not too difficult and reasonably easy to use.

Liam
I don't think "code is code". Java versus Objective-C can digress into a whole other topic. But learning any new language contstructs, IDE and tools environment, platform architecture and such, all involve a huge time committment. None of which should be taken lightly if you plan to live and breath it for the next year or more.
Sebastian Dwornik
And it also depends on how much you're willing to pay for that committment. Much of my choice between the two was largely down to the costs involved.
Liam
The iPhone SDK is free to download and use with the simulator. You just need to create an Apple developer ID (also free). You only have to pay the $99 yearly fee if you want to deploy to a device and sell in the store.The iPhone simulator is also very good for testing.
Kendall Helmstetter Gelner
You still need to fork out for a Mac or Virtual PC (or is that free these days?) and an OS X license.
Liam
Entry costs are not interesting once you start spending time
Stephan Eggermont
+5  A: 

I made a app for iPhone. It was rejected, and my 4 months of work were for nothing.
I made a app for Android. It was rejected from the Android Market, but since Android is open, I could still sell it on my own website and I make a steady income.

Isaac Waller
Did you at least get feedback as to *why* your app was rejected?
Sebastian Dwornik
The response I got back was complete garbage - it had no relation to the application and showed the reviewer couldn't understand my application.
Isaac Waller
That sucks and its BS. What the hell do we pay good money for submitting to these app stores? Maybe you should simply re-submit again and hope for a better reviewer. I don't think it costs anymore to re-submit again. Become a nagging developer until you get a decent reponse or acceptance. :/
Sebastian Dwornik
It is pretty bad. I did try resubmiting as a whole new application, which either got the same reviewer, or all the reviewers are robots that follow a checklist looking for specific things. They said my application was just a webpage because it opened pages in Safari (???)
Isaac Waller
So out of curiosity, do you prefer iPhone or Android dev more?
Sebastian Dwornik
I prefer Android dev just because I like Java better and it opens much more possibility for integration with other apps. iPhone has really nice APIs too, but the problem for me is that it is just too closed.
Isaac Waller
Are you honestly making a steady income from selling it on your website though?That was always possible before with other platforms, but very few people derived much of an income from it.
Kendall Helmstetter Gelner
how much money did you make from the Android app?
Roger Nolan
A: 

Here's something to consider - the number of Jailbroken iPhones is probably larger than the overall number of Android phones currently on the market.

If you can live within the confines of the App Store, you have a huge potential market (make sure to always allow for Touches for maximum reach).

But if you have an app that cannot live in the app store for some reason, there's always the Cydia market.

Why not do an app for both platforms and see how it goes on either? I'm not sure there's a one size fits all answer here, since the correct answer for any one person depends both on the app, and on personal philosophy.

Kendall Helmstetter Gelner
A: 

I have found the iPhone documentation to be more complete and the Cocoa Touch API more intuitive. Android is a bit of a mess. However at least I have the source code so I can spend hours tracing functions in order to understand an undocumented method. As the sarcasm implies this is both a blessing and a PITA.

Max Howell
True, but you can *use* that undocument method without getting your app rejected from the app store
Richard Szalay
A: 

There is one thing I find very frustrating and just learned this after putting my first android ap up on the marketplace recently.

First let me just say I'm not a fan of Apple at all. I'll most likely never buy another Apple product. I run only linux at my home (and windows at work) so constricting me with iTunes lost this customer.

Having said that, I'm having force close issues with my new app on all devices other than the Moto Droid (which I'm deving on). This is extremely frustrating as I continue getting 1-2 stars on an app that I can't fix because I'm not going to buy like a 100 phones out there. My impression is the platform is not stable.

What I'm trying to say is that with Apple only having to dev on like 2 phones, the itouch and ipad means that eveyone is running close to the same platform. This is a HUGE plus.

Nick