Hacker News new | past | comments | ask | show | jobs | submit login

Exactly. I've got a couple of apps about to hit the app store so I'm gradually making my way up the curve. I agree it's not the easiest API to learn. The basics are actually pretty straightforward but the details you have to consider once you start doing real apps can be tricky.

I'm really hoping Kotlin takes off as an alternative Android development language though. Java's OK but a more modern and flexible language would certainly help.

Do you have any good pointers or references for Android dev in these kinds of environments?




Do you have any good pointers or references for Android dev in these kinds of environments?

No, not really. I haven't really done much of it myself, just seen a lot of chatter about it. The specs I see, compared to the average smartphone app, have a lot more in the way of very specific UI specs and binary protocols, and less in the way of reposting tagged pictures to Facebook. So it's a different part of the system to study.

I can recommend http://commonsware.com/ for coming up to speed on the system in general. One of the best references out there, and it stays up to speed with a rapidly-evolving ecosystem.


I do have the CommonsWare books and I agree they're good. I should probably go grab the updated set.

I thought Reto Meier's book was also pretty helpful.


I built a site to share tips for Android development. See http://android.steerway.com.

I'm behind on the content updates but I'll have them by the end of the year.


> a more modern and flexible language would certainly help.

I hope Clojure for Android gains popularity. It would make Android development a hell of a lot more tolerable.


I'm not so sure about that. Most of the pain points in Android development have to do with the complexity of the API and state management. Clojure would cost you the tight tooling integration and not do much to help. You don't often encounter the kind of gnarly concurrent algorithm stuff where Clojure shines in mobile dev.

Kotlin, on the other hand, modernizes Java, but should fit the Android toolkit like a glove thanks to Jetbrains backing. Presumably they're also designing it with Dalvik in mind, unlike Scala and Clojure.

I could be wrong though. If some of the memory/efficiency issues get ironed out I'll certainly try it.


Clojure on Android offers the possibility someday of live debugging on a customer's phone, very similar to the way pg talked about fixing customers' bugs while they are on the phone with tech support by attaching to the server with a REPL and fixing it live. I can imagine a popup on a phone saying "This app is having problems. Press here to connect to our tech team for live repair."


> You don't often encounter the kind of gnarly concurrent algorithm stuff where Clojure shines in mobile dev.

Perhaps this is an issue specific to me. I've been working on algorithm development for an Android app, and being tethered to Java has been driving me up the wall.


Sounds like a good problem to have. Most mobile apps are just shunting images and text between social services these days it seems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: