I tend to agree with the not supporting flash a good idea, but not entirely. As some things would need flash, but over all, I am happy not using it at all.
I also agree and would rather do a web/html 5 app for the phones than an actual ondeck application. I would only do something on-deck if it needs filesystem or other hardware type functionality. Which is very rare.
The fragmentation however is not an issue for me. When you create an Android application, it asks you which is the minumn api you want to support. So if I choose 1.6 for eg. I can do anything that would work an v1.6, but nothing more. So if I want my app to use something specific that is only in 2.1 and up, then I will choose that and only support 2.1+. It is the same with apple. If you code in iOS4, you cannot use it on the older versions. So it is the exact same thing, just slightly less versions
IMO, iPhone is much better as compared to Android but Iām not sure about its features because currently Iām using iPhone and I donāt want to switch to Android. I have plenty of apps which are saved in my iPhone and there are so many left to install already.
This thread is about developing for each platform. I have both an Android phone and an iPhone, and to be honest, I do not even use the iPhone anymore, it is way to boring and restrictive than Android, but that has nothing to do with learning the to dev for either platform.
I have decided to just learn both. Even if it takes longer, as Android is exploding atm and iPhone has a strong app store/following. So I think it would be stupid to leave either of them out
First, I think the big hurdle isnāt which exact platform, but rather coming to grips with building software for mobile devices ā it is a far different beast with far different parameters than building server-side web apps. You are going from a land where RAM is cheap, processor cycles are nearly free and connectivity is is a given. So, getting past that hurdle is the big one, the other stuff is just semantics.
All that said, Iād start with android if I had to start somewhere given the freedom of the platform, the uptake it is getting ā which is only going to become faster as more and more devices run 'droid ā Google considers it a ātouchscreen OSā not a mobile OS.
Good points. You are right there. As slow hardware is a major factor. I am also thinking Android is the best place to start, as it is java, so me coming from a C# background, would feel at home with syntax. And it also has garbage collection, which Objective-C does not. So, java with GC will be very similar to C#, so it will allow me more time to concentrate on mobile stuff and low resources and learning their API. Objective-C is very similar to C++, syntax wise, but is very different in operation.
It is definitely going to be interesting. I cannot wait. Come the 4th of Jan, and I will be starting full steam ahead with both. Getting a few books to help.
Keep in mind that, while one currently writes android app using java syntax, it is NOT java you are writing ā it gets compiled into Dalvik. More important ā it has the android base libraries and such, not the standard Java stuff.
Yea, I know. Thanks. There are tons of Android specific libraries already available, but I am going to start with only using default android libraries and everything else manually for now. Dalvik is the Android VM. It is linux based. And android handles that, so I am not to worried, as all I need to learn is the java. At a later stage once I know what I am doing, I will look at the NDK and writing some performance tweaks, for games, etc in C++. But that is far in the future, do not want to think of that for now. lol
If youāre looking to have a larger market and potentially higher sales, (un)fortunately Apple may be the way to go. Now that they have integrated an App Store as a part of their operating system, youāre now dealing with a larger community and an increased temptation to purchase ā since the store will be right there in front of you.
