Concurrency in Android

Recorded at:

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.

github.com/nseidm1/TaskExecutor

If you want to do Android-style concurrency for native C++ code development, check this out: github.com/Himmele/Mindroid

vimeo.com/groups/waza2012/videos/49718712