Slashdot Mirror
Should I Learn To Program iOS Or Android Devices?
HW_Hack writes "In my early career in the '90s I had a hardware tech degree, but also a strong interest in software. I completed software courses in assembly, Pascal, HTML, and C as I prepped for a CS degree. I then got my chance to do hardware design for a major US firm and went that direction for a good 18-year career. I now work in a good sized school district doing IT support work at a large high school. I plan to revive my programming skills this winter so I can write apps for the flood of mobile devices. I am very much platform / OS agnostic and I support on any one day OS X, XP, Win 7, Linux servers, and now iOS as we pilot iPads in our school. My question focuses on three topics: Which programming environment (iOS or Android) is easier to jump into from a technical perspective / number of languages needed to master? Which one has a better SDK ecosystem of documentation, programmer support, and developer community(s)? Where is the market and the money going? I do not expect to get rich doing this, but with my insights into K12 needs I hope I can write effective apps for that market."
Also you have to pay $100 *per year*. Android is $25 once.
On the other hand Java and Eclipse are shit.
go iPhone. There is no market for payed Android apps. While it's technically possible to sell paid apps, the people that buy Android are either opensource "I don't think it right to pay for software" or are just too cheep to pay. Combine that with the fact that you will have to support 10X the number of model of device with their variations in screen size and support for touch or buttons etc and the clear winner for an independent developer is iPhone. Do you really want to ship software for devices that you haven't tested on?
Disclaimer: I enjoy writing for iOS devices. It's fun!
Had many apps rejected?
In the free world the media isn't government run; the government is media run.
There's only one reason to develop for iOS: you're retarded.
You're retarded.
Well if you can put up with a stupidly complicated and slow UI, annoying project organisation and a healthy sprinkling of null pointers, I guess you might like it.