Auditing Material 3 Before Expressive Ships — I Need Your Input

I'm doing a structured UX audit of Google Material 3's interaction design — specifically micro interactions (state layers, ripple, FAB morph, switch/checkbox animations) and macro interactions (Container Transform, Shared Axis, Navigation Bar/Rail, Predictive Back). M3 Expressive lands with Android 16 around September 2025 with bolder motion, richer shapes, and faster animations. Before it does, I want a clear picture of what's actually broken in current M3 — from devs and designers who work with it daily, not just the spec docs. Already found 9 structured findings from GitHub issues alone — the Container Transform return path is broken in 3 separate ways. If you've touched M3 in Compose, Views, Figma, or as a Pixel user, 4 minutes here would help a lot: https://docs.google.com/forms/d/e/1FAIpQLScb2o19Xt0MrnF0Uj4JkmScgYo3mFdXgodtX7jCON9DGhPStA/viewform?usp=header I'll share the full audit findings publicly when done — both the framework and the data. Tags: #android #ux #materialdesign