ComposeBridge — what's your biggest friction when iterating on Compose UI?

Hey Product Hunt 👋

I'm launching ComposeBridge next Tuesday (Sept 29), and I'd love to hear from the Android/Kotlin community before launch day.

The problem I built it for:

Every Compose developer knows the loop — change a padding, wait 15-30 seconds for Gradle, look at the screen, change again. It adds up. Especially when you're fine-tuning a design with a designer sitting next to you.

ComposeBridge takes a different approach:

• Tap any Composable on a real device to inspect it

• Adjust colors, dimensions, paddings live (<50ms)

• Persist the change back to Kotlin source with a single-line git diff

• Zero rebuilds — the change is surgical, not a full reload

The tricky part is dynamic lists, inline composables, and unkeyed scopes — I've documented those honestly in the repo.

Status: v0.3.0. Early, not production-ready. But the core loop works end-to-end.

Two questions for you:

1. What's your current biggest friction when iterating on Compose UI — build time, hot reload limitations, or something else?

2. If you've tried similar tools (CMP desktop hot reload, Compose Preview, Live Literals), what made you stop using them?

I'll be here in the thread — happy to go deep on architecture, limitations, or anything else.

GitHub: https://github.com/JALAL591/compose-bridge

Demo (38s): https://youtu.be/Hywyq7cBdDM

Launching Tuesday — set a reminder if it sounds useful 🙌