Why We Are No Longer Developing for the iPad

Re:Why We Are No Longer Developing for the iPad by piyush_soni on Friday April 17, 2015 @12:19AM (#9392246)

Are you sure? Saying Xcode is only available for Mac is like saying "Visual Studio is only available for Windows, so I'll stick with Windows". I thought you'd come up with some movie maker stuff which might not be as good on Windows.

I used Xcode a few years back and it was a nightmare with the limited things it allowed me to do when compared to Visual Studio.

[ Parent | on HN ]

Re:Why We Are No Longer Developing for the iPad by ryanSrich on Friday April 17, 2015 @12:25AM (#9392260)

Really? You're going to pick out Xcode out of the whole list? I even clearly stated what the most important app I use is and it wasn't Xcode.

...however, if you're developing iOS and OSX apps you need Xcode. So I'm not sure what your point is.

[ Parent | on HN ]

Re:Why We Are No Longer Developing for the iPad by numbermess on Friday April 17, 2015 @01:22AM (#9392389)

XCode is a pretty good choice for writing Mac applications. I'm not aware of many accepted alternatives.

[ Parent | on HN ]

Re:Why We Are No Longer Developing for the iPad by rimantas on Friday April 17, 2015 @01:57AM (#9392456)

There really is only one–AppCode, and not really an alternative, because usually you end up using both.

[ Parent | on HN ]

Re:Why We Are No Longer Developing for the iPad by piyush_soni on Friday April 17, 2015 @01:40AM (#9392420)

My point is that you can really come out of these forced incompatibilities if you want. There are multiple IDEs to develop the same thing on Windows, but of course, Apple does not want that. That's why, the author of the article had to leave developing for them - in my very personal opinion, everyone should do that, in the hope that it will force Apple to strive for a common/universal development language.

[ Parent | on HN ]