Looks like a great idea. I have a few questions about it:<p>1. How does this work if you're using it in a ListAdapter? Should it even be used there?<p>2. It seems like it would play nice with jackson, as jackson will only call your setters and getters if they're there, anyway. Are you using it alongside any serialization libraries or ORMs?
This looks like an example of forcing a concept from one framework to another. Android doesn't have bindings, but instead uses adapters and notifyDataSetChanged().<p>This binding may be more useful for non-list data. However, do you really have a large number of views that are not is a list?
Looks nice, but as far as i can see this is using Reflection, which might be a performance penalty you don't want to take in your app.<p>B.t.w. I never really worked on data (input) intensive apps on Android.