Road to stable

[ZacSweers]

We're looking into moving Circuit to stable! We're feeling pretty good about where most of the development is at.

Some high level thoughts

• Would incorporate kotlin's binary compatibility validator
• Introduce an @ExperimentalCircuitApi to circuit's runtime
• Gate some remaining areas we are still working on with the above annotation
  • NavDecoration - @stagg is working on shared element transitions support in Shared transitions #1550 that we want to keep options open for here.
• Do an API review of our existing API, trim down areas where appropriate. Helpful to do this after incorporating the binary compatibility generator as that gives us a good overview.
• Likely mark non-stable KMP targets as implicitly experimental, namely iOS/wasm. If anything, start with only android/jvm targets as stable.

We're seeking inputs on areas you think are still rough, thoughts on the above, if you think Circuit is ready for stable, how much a stable release would affect you, etc!

[MiSikora]

[ZacSweers]

Would you mind filing a separate discussion Q&A for this? This feels more of a general usage question rather than feedback on stabilizing the public API?

[MiSikora]

Yes, no problem. Done here: #1805. I deleted original comment to unclutter this discussion.

[shaharKeisarApps]

Really exciting to see Circuit evolve—it reminds me of TCA that our iOS team uses, but simpler! Makes me wonder if in the years to come, Google might consider embracing such a unique approach, especially with KMP paving the way for truly multiplatform development.
Thank you for the amazing work on this project—looking forward to seeing this progress!

[ZacSweers]

Hi, please don't use this discussion to ask for release ETAs. It's also a bit rude to @ mention maintainers on top of that. I'm going to hide this as off-topic, please be patient or just build from source or snapshots if you're eager to try it.