It's not about imagining what the best UI component would look like removed from any particular framework, but what the practical constraints are working within

It's not about imagining what the best UI component would look like removed from any particular framework, but what the practical constraints are working within the already-existing android UI framework. Android APIs were simply designed for inheritance-oo style to work with them, and trying to avoid this will cause pain. A similar situation has occured in ios development where the functional aspects of Swift do not complement the existing design of the coca framework.