Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Concurrency in Android

Concurrency in Android



G. Blake Meike discusses concurrency in Android, focusing on AsyncTask – what can be done with it, what problems using it and how to circumvent them.


G. Blake Meike is an engineer with more than 30 years of experience, much of it with Java. He has built systems as large as Amazon’s massively scalable AutoScaling service and as small as a pre-Android OSS/Linux based Java-like platform for cell-phones. He is currently deep in Android. He is co-author of two Android books: “Android Application Development” and “Programming Android”.

About the conference

Strange Loop is a multi-disciplinary conference that aims to bring together the developers and thinkers building tomorrow's technology in fields such as emerging languages, alternative databases, concurrency, distributed systems, mobile development, and the web. Strange Loop was created in 2009 by software developer Alex Miller and is now run by a team of St. Louis-based friends and developers under Strange Loop LLC, a for-profit but not particularly profitable venture.

Recorded at:

Oct 26, 2012

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Thank you for your talk!

    by Noah Seidman,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    As a professional Android developer I found your presentation wonderfully consistent with one of my most favorite topics. The limitations of AsyncTask generally cause a mess of code, especially when posting results back to the ui thread. Recently I've published on GitHub a framework to gracefully manage all asynchronous activity, and coordinate how info is posted back to the ui thread. The TaskExecutor (GitHub link below) consolidates all asynchronous activity to a single, unique, app wide ExecutorService that provides a gracefully managed callback that always posts to the currently visible Activity. The location of the Task is always known, and the exact location of updates/completion results is always known.

    A new Activity can be opened and the callback will be gracefully managed to point to the new activity. The app can be closed and the result will be queued and delivered to the app when a new Activity is launched. I personally wanted to take AsyncTask to a new level, for my projects, and for the benefit of the entire Android community.

  • Android-style concurrency for native C++ code development

    by Daniel Himmelein,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    If you want to do Android-style concurrency for native C++ code development, check this out:

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p