mesa keith :damnified:, it's because most Android apps use Google libraries. Google really acts like those bloated libraries that provide useless indirection are the only way to build M3 UIs. I had to go out of my way to keep things sane. I had to reimplement some components from scratch because the only "official" implementation that exists depends on the Google way of doing things so much it's really easier to do what I did than to try to decouple them. And, let's just say that my approach is very controversial among the Android developer community. But users are happy, and that's what actually matters in the end.
@grishka @Gargron Thank you so much for making things invisibly better for the rest of us ( ̄^ ̄)ゞ