Our team is 5 Android devs and since summer most of our PRs are written by Claude Code or Codex, mostly Compose UI and some Room migrations. Review time per PR is about the same as before, around 25 minutes, but it's a lot more tiring.
The code looks finished. Naming is consistent, previews are there, tests pass. What's missing is why it did things the way it did. Last month one PR hoisted some state two levels up so a whole screen recomposed on every keystroke, and nothing in the diff or the description said that was a choice. We only caught it profiling on a Pixel 6a.
What we've tried so far:
- coderabbit on every PR as the first pass. It's good with the Room and lifecycle stuff, last week it flagged a migration with no fallback
- A rule that the agent writes 2 lines explaining any change outside the ticket. Helps when it actually does it.
- Macrobenchmark on our 3 main screens in CI. Slow, but it's the only thing that caught the recomposition one.
Is anyone doing something specific for Compose performance in agent PRs, or is profiling on a low end device still the only real check?
submitted by /u/ParticularFan1122[link] [comments]