Developing for iPhone or Android? (As a C# developer) [closed]

Answer 1

In my honest opinion - I see the recent changes in iPhone SDK a kick in the teeth. I'm an Adobe person and you would assume, an infinite number of developers begin building applications in CS5 would be great for you App Store? Apparently Apple do not agree.

However - if your looking for exposure, getting an App into the App Store will yield more results if you build a quality app. As the Android store hasn't got a footing yet (if they'll ever be one), all marketing is on your own head.

I recently defunct Apple as they force us developers to 'be them' and I don't agree with their ethos.

---

That said, having programmed for both, The Android is slightly tricker to get installed and took a very long time to sort itself out. Although the instructions are very good and the examples are well defined.

If you've got a mac, installing the iPhone SDK is a sinch and you ready to build apps. It does cost £50 for the developer connection and yes android is free. [Correction - this may cost a one of fee of $25]

If you are building an iPhone app thats heading for the wild, you will need the connection (this can take up to 3 weeks in my experience) so you can test it on your iPhone.

And you'll definitely need to purchase a Mac.

--

With Android, its java, and with the newest rendition, a very good API to work with. As an additional bonus its build upon Eclipse, so it'll take you seconds to understand whats going on.

--

As a final thought - being an Actionscript/JS developer, the transition to Java was a logical and simple step and (please don't shoot me if you don't agree) Objective C is a train wreck of two different language styles. I found it very very difficult.

but don't just take my word for it, definitely try them both, as I see Android emerging market just an ice berg right now, but Apples is established.

Answer 2

Two disadvantages of iPhone/iPad apps ecosystem are:

1. Apple test & accept apps before puts them into AppStore (this take time and acceptance depends on Apple current policy) -- Google seem not to care about that so much.
2. AppStore it's the only official place for iPhone apps -- on Android you can install apps from unsafe source (i.e. website or email attachment) -- so you can provide and charge for app in various ways.

Answer 3

Both can be good/bad for various reasons.

iPhone - good

• Great SDK & get to use Xcode which rocks
• Well documented online (many tutorials)
• Large deployed base of devices
• Well established app store
• Get to learn Objective (I find it a fun language)
• Most people tend to upgrade their iPhone OS so you can get away with only developing for the latest and greatest

iPhone - bad

• Crowded app store, very hard to break through (the "gold mine" is a myth)
• App Store apps need to be approved by Apple, with some often rejected for dubious reasons
• Have to buy a Mac (not necessarily a bad thing)
• Have to learn Objective C (can be a hassle)
• Have to pay $99/year to publish apps
• Can only multitask on iPhone 4.0+. Hardware restrictions will mean many devices will not be able to use this however

Android - good

• No restrictions on apps that you can develop/publish
• Wide deployment of devices and growing - set to overtake iPhone soon
• Can multitask on Android
• Get to code in Java which is widely known
• Some of the SDK tools integration with Eclipse is nice (although still needs a bit more work)
• Only have to pay $25 to publish apps (one off fee)
• Can develop on any platform (Mac/Windows/Linux)
• Great Android devices coming out this year - platform could really take off.
• Nice XML way of laying out views. While not as flash-looking as the iPhone Interface Builder, it is very powerful.
• Get to work in Eclipse (which some people think rocks)

Android - bad

• Have to support wide variety of screen sizes and devices
• Many people still using old versions of Android OS (1.5) so you'll probably have to support those if you want to reach that market
• SDK is not as polished as iPhone SDK
• Android Market is not as popular as iPhone App Store - hit apps will not make as much $$$

All in all, starting with whichever is fine in my opinion, especially as now Android is gaining ground. Given your background I'd say you should go for Android.

Answer 4

If you're a C# developer, and you're looking to begin iOS development, then you owe it to yourself to read Josh Smith's iOS Programming for .NET Developers.

It's exactly what you're looking for.

Answer 5

I would suggest getting your hands on the latest iPhone SDK and a Mac from a friend before taking the plunge unless the $600 minimum investment for a macmini(what I did in my case) doesn't bother you. You could try installing GNUstep for Windows and messing with Objective-C without buying a Mac to check out the language but it's not the same without XCode and Interface Builder,SDK,etc. The reason I say this is because I'm currently taking an iPhone class and just learning Objective-C is a lot larger learning curve than I thought it would be and eating up a lot more of my time than I cared for. Unlike C# or Java you have to manually keep track of memory management which is really annoying and a hassle not to mention Cocoa Touch, which is sort of like .Net or Java classes for Objective-C; another big learning curve! Bottom line neglecting the fact that it is a mix of SmallTalk and C and looks horrible if you can get over that it is still hard and easy to crash your program. Forget to hook up your outlooks correctly in Inteface Builder? CRASH! Forget to use an @ for an NSSTring due to the loose type checking? CRASH! I'm just saying that you'd probably be more productive and actually get applications completed in your spare time going the Android more familiar Java language route vs the Apple route. Also, I'm not sure how big Android is on the whole MVC concept, but it's everywhere in the iPhone SDK since Cocoa uses the Model-View-Controller (MVC) design pattern throughout. On the other hand, if you like a challenge or learning the Apple route is the way to go and if you are good you app will sell and you will make money. Like I said there is a ton to learn with the iPhone before you can even start thinking of selling the next killer app LOL.

p.s. Oh and unless you want to test something on actual hardware that doesn't work in the iPhone/iPad simulator or actually upload an app to the store you don't need to pay the $99 fee to develop.

Answer 6

MonoDroid for Android is in beta, which means you'll be able to write Android apps with C#. You can sign up for the beta here.

iPhones are getting more and more restrictive. Android is opening up. Android is also shipping more phones than iPhone. You decide.