jure_z

Good one. What happens if you actually do find the huge money making product? Let's say it's constantly bringing in around $5k/month from sales (I know that's hard for downloadable one-off sales). Are you still going to kill it after one year? :)

Highly agree. It will grow mature in time (probably a lot faster than iOS did - 30 years) and will feature a lot of new and useful paradigms.

Well yeah, there are numerous different approaches one can take. You could also build hybrid apps if you're familiar with HTML&CSS, you could use RubyMotion if you're a Ruby dev, etc. :)

Exactly, Apple doesn't do legacy for very long.

To tackle the argument that there is infinitely more Obj-C resources out there - think of how many iOS3, 4 or even 5 tutorials you'd still be able to fully use and implement in your app? I'd say close to none. :)

Of course, you definitely didn't waste time spent learning Obj-C - once you dig into more advanced stuff, you find that knowledge useful.

Although, I think that considering Swift is only around 7 months old, there are already a lot of really good and high quality resources available online.

That's one thing I should've mentioned as well, thanks!

I, for example, come from all sorts of different languages (C++, C#, Java ...) but Obj-C was still a pain to learn. I also do personal projects in Ruby, which I like a lot. That's why I'm really fond of Swift and I can see it going in a similar direction, maybe.

And I agree - Apple frameworks are still written in Obj-C, so you'll have to obtain a basic understanding of the language. But that can come in a bit later, once you've already built something and are looking to dig in a bit deeper. :)

Good point, would be interesting to see a comparison with cost of living included.

Insightful post!