My problem with Android development is that, being a non-Java developer, I never knew when to use the Android SDK or the Java SDK or the Apache stuff for certain tasks. For example, networking. Googling online for solutions, I don't know if any of the Java code I find is Android compatible.
A few days of programming on iOS and Android illustrates a vast difference.
21–30 of 97 posts
Re: A few days of programming on iOS and Android illustrates a vast difference.
#22Java APIs are not designed to "just work" but rather to "eventually work with anything".
Re: A few days of programming on iOS and Android illustrates a vast difference.
#23Screw it, I'm psyched! It's a great time to be a mobile developer! I was going to write a whole response regarding iOS vs Android until I realized the debate is like religion or politics. Currently both platforms are great and only getting better with each iteration. I'm developing for both platforms and loving it. Just in the latest iterations look at what we can do. iOS * AirPlay - My phone will be my gaming consol…
Here's my question. In this (somewhat ungrounded in Android reality) article the poster makes the claim that on iOS, you 'just get' a few seconds to finish off everything.
This does not seem like a sustainable model. If my app and the next app a user launches are both memory heavy, I expect my app to be killed to make space. How does this process work on iOS?
Also, nobody really seems to understand how amazing Intents are before they use Android :)
Re: A few days of programming on iOS and Android illustrates a vast difference.
#24Android is not a toy, you can easily see it's an improvement over traditional mobile, and it highly influenced by the web. 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 gian…
Just a point that needs clarification: how is any of this comment relevant to the points raised in the OP? That is, how does this help against the fact that Android has: * 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 wha…
Could you give me an example of exactly why the claims you've made are true?
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.
Re: A few days of programming on iOS and Android illustrates a vast difference.
#25Haven't tried programming Android, but not crazy about objective c. But Apple's documentation is stellar and easy to access.
Re: A few days of programming on iOS and Android illustrates a vast difference.
#26Develop for the iOS platform in Cocoa, develop for Android in Adobe AIR.
Best combo I have found!
Re: A few days of programming on iOS and Android illustrates a vast difference.
#27Screw it, I'm psyched! It's a great time to be a mobile developer! I was going to write a whole response regarding iOS vs Android until I realized the debate is like religion or politics. Currently both platforms are great and only getting better with each iteration. I'm developing for both platforms and loving it. Just in the latest iterations look at what we can do. iOS * AirPlay - My phone will be my gaming consol…
[deleted]
Re: A few days of programming on iOS and Android illustrates a vast difference.
#28My problem with Android development is that, being a non-Java developer, I never knew when to use the Android SDK or the Java SDK or the Apache stuff for certain tasks. For example, networking. Googling online for solutions, I don't know if any of the Java code I find is Android compatible.
My rule of thumb:
- if you see "java.awt" or "javax.swing" in any package import, run away.
- if you need to download a native library to run a hello world, run away too.
The rest is/should be fair game. Try to run a hello world on the device.
Re: A few days of programming on iOS and Android illustrates a vast difference.
#29Maybe I am going off on a tangent here, but... why not just use an AsyncTask with a synchronous HTTP petition inside? I am a novice in the Android SDK, but it just seems easier.
Re: A few days of programming on iOS and Android illustrates a vast difference.
#30Earlier quoted context omitted.
I'd love to hear a good java book recomendation. Is there a K&R kind of book for java? 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.
Hortsman & Cornell's, two volume "Core Java 1.2". I only read the first. 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.
Don't forget Java Puzzlers, also by Bloch: http://www.javapuzzlers.com/
Not only is it a fun read, but it delves very deeply into case studies of the dark corners of the Java language.