Google I/O 2010 - Android REST client applications

Google I/O 2010 - Developing Android REST client applications

Android 301

Virgil Dobjanschi

This session will present architectural considerations for developing RESTful applications on the Android platform. It focuses on design patterns, platform integration and performance issues specific to the Android platform.


For all I/O 2010 sessions, please go to http://code.google.com/events/io/2010/sessions.html

Category:

Science & Technology

Tags:

• Android
• Mobile
• Java
• googleio2010
• google
• Google I/O
• developer conference
• #io2010
• #android6

[cciach]

I am happy to see that even google employees can be nervous at presentations. Now I feel not so bad about my own presentations anymore :)

[850mph]

Ditto below post.

Very useful vid.

Where can we find sample SOURCE for the pattern(s) described here?

[theonedani]

wave? lol

[metafedora]

This guy has the most annoying voice, I wish they would dub it over with someone like Ian McKellen as narrator.

And like most Google employees, you get that slight I'm-soooo-much-smarter-than-yo­u attitude. Ugh.



[majdijr]

great session, i learned a lot from it

[lobais]

Guys... It's true that there is no use for this " hyper-redundant nonsense to get a simple JSON result back and parse it".

But if you are actually writing a two-way rest app, using put, post, delete and caching, things become a lot more complicated. Unless you are willing to sacrifice performance.

Just saying.

[xandy1979]

@russellperry Well Separation of role always comes with a cost. Android System design also makes these worse.. you have content provider but need to execute the operation in a separate Service with a separate thread.

[masiminder]

@pushingprimitives

if everything fails: google for an­droid-developing-RESTful-an­dro­id-apps.pdf

[khaled3anani]

Thanks alot , is there any sample code that we can look at ?

[russellperry]

I'm sorry, but this is Google's engineering culture run amok. REST architecture should never be this complicated. I get mobile small footprint, CPU management, radio, etc. There's still no excuse for this 5-layered, hyper-redundant nonsense to get a simple JSON result back and parse it. This tendency to over-complicate simple operations is all over the Android API, and seems to be the result of a bunch of PhDs writing APIs to satisfy CS theory rather than solve simple problems in a simple manner

[russellperry]

@GrEEnOneMK Exactly. Look, all you have to do is implement IUnknown, relate the ProdID in the registry to the GUID of your component...OK, let me back up. First you need to...no wait. See, it's very simple. No, wrong hive in the registry! Not HKCU -- HKLM, silly. Can't believe you thought it was HKCU, lol!

They also apparently called in the whole Windows Installer team to help with the architecture as well. This is complicated stuff. I mean you have to call a server and parse the result!

[GirlieBlues]

Cool. Rest Client Applications.