That's the idea behind the probe lib : https://github.com/lucasr/probe/blob/master/library/src/main...

So, when you write an android app, most of time you describe your ui's layout in xml files. This xml is then translated to a binary blob during the compilation (you don't have to know/care about this intermediary format though). When you need the corresponding ui, you use a layoutInflater in order to 'inflate' the xml : read its content and create the corresponding views.

One nifty trick is that since the LayoutInflater instantiate the views, it is the perfect place to replace a view by another. For example, that's how the support lib works (well, modulo some hacks, the layoutInflater was not thought out for this initially). When you ask for an ImageView in your xml, the support lib provides you with an AppCompatImageView instead, adding some new capabilities independently of the OS version.

probe goes a little bit further and dynamically add some methods to any class that it inflates, in order to add some layout debugging capabilities.

(OP here) I think that would be a useful thing to do in some situations, but it often won't get what you'd like. There's no guarantee that a view will ever call it's superclass' implementation, so inserting code has to be done a the leaf view classes not further up.

When it comes to Java, it might be simpler to decompile anyway; but yeah, totally doable.