AsyncTaskLoader: Populate a Static List View

One of the first things I tried to do while developing an Android app is asynchronously populate a statically defined list view. This turned out to be a much more challenging task than I anticipated, and apparently nobody else on the entire world wide web is attempting to do this (or I just didn’t google right 0_o).

Specifically, I wanted to define a ListView (or Spinner or whatever) in a layout XML file, and populate it via data from a restful web service. Initially I tried to do this in the onCreate(), but got theĀ android.os.NetworkOnMainThreadException. So, obviously I needed to pull the data from a restful web service asynchronously. This post is going to explain how I did that.

I’m going to accomplish this with an AsyncTaskLoader, and I’ll use a back to front approach, starting at the service layer and work towards the UI. The example app is an extremely simple app to list some blog posts.

First, the BlogPost model object:

public class BlogPost implements BlogPostRow {
    public DateTime date;
    public String title;
    public String content;

    public BlogPost(String title, String content, DateTime date) {
        this.title = title;
        this.content = content; = date;

Obviously the model is extremely simple for the sake of example. No getters/setters because 1) I don’t want the code bloat in a blog example, and 2) I’ve been using getters/setters for 15 years and I still don’t know what the point of them is. (Not really true.)

The service:

public class BlogPostService {

    public List getPosts() {
        //TODO: Could you imagine if this was a real service and actually hit a restful data service endpoint?
        return Arrays.asList(
                new BlogPost("Android with maven", "blah blah blah maven rocks blah blah android this that the other thing."),
                new BlogPost("Dynamic ListView loading static ListView", "Whole lotta talking, not saying much.")

Also incredibly simple. But just pretend it’s making an HTTP request and converting a JSON response into those BlogPost objects with some library like Jackson.

Now the AsyncLoaderTask implementation, which leverages our supposed rest service:

public class BlogPostLoader extends AsyncTaskLoader> {
    private BlogPostService service = new BlogPostService();

    public BlogPostLoader(Context context) {

    @Override public List loadInBackground() {
        return service.getPosts();

Extending the AsyncTaskLoader class requires only an implementation of loadInBackground() and a constructor that provides a Context. Our code will not call loadInBackground() however, that is the responsibility of a Loader implementation. For this, we’ve made it to the Activity:


public class ListBlogsActivity extends Activity {
    public void onCreate(Bundle savedInstanceState) {

      final BlogListAdapter blogListAdapter = new BlogListAdapter(this, new ArrayList());
      ListView blogPostListView = (ListView) findViewById(;


      getLoaderManager().initLoader(0, savedInstanceState,
        new LoaderManager.LoaderCallbacks>() {
          @Override public Loader> onCreateLoader(int id, Bundle args) {
            return new BlogPostLoader(ListBlogsActivity.this);

          @Override public void onLoadFinished(Loader> loader, List data) {

            @Override public void onLoaderReset(Loader> loader) {
            blogListAdapter.setData(new ArrayList());

A few points to note:

  • The first parameter passed to initLoader() is an integer used to uniquely identify the loader. I’ll be honest, I don’t really know why this is necessary or why the caller has to provide this. But I can tell you that if you have two loaders and give them both the same ID, you will get some unexpected behavior (like, only one of the loader’s will be used, for both of the purposes you created them for). So just make sure each call to initLoader() provides a different integer ID as the first parameter.
  • The examples I found of how to use an AsyncTaskLoader did NOT include calling the forceLoad() method on the loader object returned by initLoader(). However, nothing worked until I called this.
  • As I’ll show in the next block of code, it’s critical that the Adapter method notifyDataSetChanged() is called when the data in the adapter is updated. Not calling this results in nothing changing in the UI.

The adapter:

public class BlogListAdapter extends BaseAdapter {
    private static final DateTimeFormatter dtf = DateTimeFormat.forPattern("MM/dd");
    private static final int MAX_SUMMARY_LEN = 100;
    private LayoutInflater inflater;
    private List blogPostRows = new ArrayList();

    public BlogListAdapter(Context context, List blogPostRows) {
        this.blogPostRows = blogPostRows;
        inflater = LayoutInflater.from(context);

    public void setData(List data) {
        if (blogPostRows != null) {
        } else {
            blogPostRows = new ArrayList();
        if (data != null) {

    public View getView(int i, View view, ViewGroup parent) {
        BlogPost post = (BlogPost) getItem(i);
        if (view == null) {
            view = inflater.inflate(R.layout.blogpostdetail, null);
        TextView blogDate = (TextView) view.findViewById(;

        TextView blogTitle = (TextView) view.findViewById(;

        TextView blogSummary = (TextView) view.findViewById(;
        String summary = post.content.substring(0, Math.min(MAX_SUMMARY_LEN, post.content.length()));

        return view;

    public int getCount() {
        return blogPostRows.size();

    public Object getItem(int i) {
        return blogPostRows.get(i);

    public long getItemId(int i) {
        return i;

Nothing particularly interesting here, other than the call to notifyDataSetChanged(). Nothing happens if this method is not called! Don’t forget it.

Finally, I’ll include the layout XML.