11–20 of 119 posts
As an iOS developer, this is probably the best comparison between iOS and Android development that I've read. I'm pretty scared of Eclipse and the slow-as-hell emulator doesn't sound fun, but coding layouts that don't involve lots of "how tall is this text for this given width?" calculations is a welcome addition.
I actually used it as my primary Latex editor while writing my PhD thesis this spring.
http://clayallsopp.posterous.com/building-an-android-app-fro...
This was great. Im curious, where you experienced in Java before jumping into Android?
Great write-up. I read the whole thing and bookmarked it as well for future reference. Thanks for sharing. Which resources (online or otherwise) did you find most helpful?
Interestingly (but inevitably) as a java developer who first learned Android and then moved to iOS, the sticking points he mentions are exactly the same ones I found, but the other way around. I think Eclipse makes sense if you think like a java coder, Xcode not so much, and Objective-C will fry your mind... That said, Eclipse and the Android SDK is a pain to install even if you are a java wizard.
Skip the ideological critiquing and start shipping some awesome products..
I guess that is really what separates the great developer from the good developer.
After you suffer the initial emulator load, changes appear in the app by simply bouncing the app. It's one big win for Titanium.
Question to Android devs with iOS experience: are there any tools available which would be counterpart for Instruments? Instruments do not get mentioned in these comparisons for some reason, I think these are great tools to debug and improve performance.
Instruments has no competition from traceview.
http://android-developers.blogspot.com/2010/10/traceview-war...
As an iOS developer, this is probably the best comparison between iOS and Android development that I've read. I'm pretty scared of Eclipse and the slow-as-hell emulator doesn't sound fun, but coding layouts that don't involve lots of "how tall is this text for this given width?" calculations is a welcome addition.
The emulator is very slow indeed, but they talked about it at I/O and they said they will improve it this fall with hardware acceleration (they think lack of it was the biggest issue). Another smaller issue would be that the Android emulator is basically running "ARM hardware" on top of x86 (it's not just a fake simulator like the one for iOS). They're also bringing a new UI builder this fall. They talk about all of…
Uh... no shit? That's exactly what the "emulator" part of "ARM emulator" means.
> it's not just a fake simulator like the one for iOS
It's not a fake simulator, it's a simulator period. There's nothing fake about it.