Edit:
I judged too quickly, and this is really cool. I did a quick setup from both Android Bootstrap and Android KickstartR. Android KickstartR worked with very minimal effort, and while there were a few things I had to do manually in Eclipse because of some weirdness in the latest Android toolkit (set JDK compiler to 1.6 to fix attribute errors, rename the projects...the usual), it worked and it wasn't so think with someone else's coding and project setup style that I could easily get cranking on this. When I set up from Android Bootstrap, it flat out didn't work with a simple Import from Eclipse and when I browsed through the source files, it looks really thick with boiler plate code. Bootstrap looked more like an app in a box and less like an actual bootstrap or kick start for my own app.
This KickstartR thing can go a long way actually if it maintains the lightweight feel. I don't like that AB uses Roboguice for that reason (as an example of what I mean about lightweight vs heavy-handed in this case). The second you introduce that by default, as seems to be the case in AB, you're now tied to that whether you like it or not. I personally gave Roboguice a try and just didn't think it added value for me and wasn't my style. I have other ways of achieving the same benefits that fit my style better, so I'd rather not have it, or at least have the option to remove it.
Something cool for this KickstartR would be to support arbitrary libs and not just the really popular ones. For example, I published my own lib which currently only I'm using AFAIK. But regardless, I use this lib in all of my own work. It would be nice to add a reference from that here, especially since I publish a jar with my library so it would be as easy as copying my jar into the libs directory. A former coworker of mine did the same, and I'd love to grab his libs in the process as well (as well as things like http-request, etc).
Sorry about the quick judgment...nice work.