* A much more complex set of (good!) abstractions that are poorly documented;
* and, if I might add alongside the OP, requires a much higher workload in terms of code length and complexity, debugging, device configuration management and tools for what seems to be a much lower payoff?
I have a successful iOS app out, and I tried to rearchitect it in a manageable way to port it on Android. What I found out is:
* The code would be roughly twice as much as the iOS version.
* A proper UI effort would require roughly 2.5x work than the iOS version, as I need to prep up a flexible layout that will work on phones (the buckets 'small' to 'large'), and then another for tablets (actually up to two: 'xlarge' and Honeycomb, which may require some rethinking to accommodate the new action bar). Contrast this to two, fixed-size layouts for the iOS version.
* I already have a path for implementing backgrounding on iOS and it requires minimal change to account for services not available while backgrounded; otherwise, code is exactly the same. On Android, I would have to plan for it from the beginning and set up very poorly documented IBinder stuff to have my Activities talk to a background Service.
* The general unwillingness of Android users in the face of paid apps, and a use model that does not lend itself easily to the insertion of ads, would make my (more costly) effort go unpaid.
I must admit I have never used resources other than developer.android.com and Google, and the latter didn't help me as much as (as little as) developer.android.com did. There might be an excellent book on all of this, but I haven't bought any — any recommendations are welcome.
And you can try these sites for code snippets on anything:
Why would your app need twice as much code? Why is using the Android ui designer so much harder than iOS's equiv?
What is so undocumented about IBinder? It's basic IPC?
I would really like to hear reasons, not abbreviations.
http://developer.android.com/reference/android/view/ViewGrou...
I actually use this to inflate a series of layouts, and then to arrange them inside an existing layout dynamically.
An Android developer grows up once they have to deal with Activities going poof.
To be fair, services and content providers enable widgets. Widgets are a differentiator.
I also have to say that maybe iOS is bit easier to get started with but have the author come talk to me after doing ten or twenty apps wrangling core data, list view, sprites, physics engines, universal apps and mixing c c++ and objectice-c and tell me that rabbit hole is not pretty damn deep.
Gosling's "The Java Programming Language".
And Josh Bloch's "Effective Java".
After that, Java Concurrency in Practice.
Langr's "Agile Java" is good for just that.
Bloch, Goetz, and Doug Lea have each written excellent books on java concurrency.
That's just about all the java books I would want to recommend. Many j-books are trash.
Effective Java is a must-read once you understand Java. It points out what is magic and what is not. What takes up processing time and what doesn't.
It pulls the sheet back on the abstractions and shows you how everything works and what you should be aware of.
Doug Lea is a brilliant developer in the concurrency space. With his Executor framework that went into (Java 5?) he suddenly made threaded programming as easy as possible to get right.
I've been exploring iOS using Objective-C and I'm about half-way done with my first real app for the Appstore and I can't wait to try and rewrite it using ECL once it is done.
Otherwise it will probably be Unity for me since my main interest is games and game-like apps. I really don't have the time to become and expert in each and every differing mobile platform.
Our Android apps are all on the galaxy tablet, we plan to roll out a deployment of 50 devices by year's end.
I fought Android until I decided to throw my entire weight behind Java and settled on it as a platform. Don't fight it: learn Java proper, do a few SWT & Swing apps, feel the burn .. then do Android.
You can ignore the abstractions and just "draw up" your application with Eclipse, inside one giant activity, but you would be doing yourself a disservice.
I told myself "Java sucks, it's bloated, it's big, yada yada yada. Just man up and learn it; no sense in bitching about what you don't know" :-) Glad I did. It gets work done.