Jetpack Compose

been refactoring a few legacy screens to compose. aside from dev velocity, the runtime perf seems identical or slightly worse on lower end devices. are we just shifting complexity to the runtime? overhead is starting to worry me in deep trees.

another week, another architectural pattern where we wrap basic state in five layers of abstraction just to avoid a single recomposition. if you need a for a toggle button, you aren't doing clean architecture, you're doing resume padding.