A modern programming language that makes developers happier.

kotlinlang

Hi all!
It seems like material3-compose went to stable (latest version is 1.0.1) But there are still stuff annotated with `ExperimentalMaterial3Api` like Scaffold, which makes it a little bit confusing. Is it safe to use Experimental api in prod? Are there going to be breaking changes for that api?

&gt; Is it safe to use Experimental api in prod
Should be, yes

&gt; Are there going to be breaking changes for that api?
Probably also yes. That's the point of experimental annotation

Usually, I would expect from production ready api's not to have an "experimental" annotations...

"production ready" could mean something else for different people. Some people consider API to be production ready only after it's been out for several years :slightly_smiling_face:
Read the Android/Kotlin experimental annotations as "_Possibility of API change until stable_". It does not have other meaning as far as I know.

<https://kotlinlang.org/docs/opt-in-requirements.html#opt-in-requirements-for-pre-stable-apis>

"Once your pre-stable API graduates and is released in a stable state, remove its opt-in requirement annotations from declarations."
Based on Kotlin requirements to OptIn the experimental should be removed if version is stable.

Not if *version* is stable but if the *API* is stable.

Depends on the context. By API you could mean the "whole API surface of a library" or "API of some class" or "API of package" or just API of some functionality that spans across several files/packages

Relevant thread: <https://kotlinlang.slack.com/archives/CJLTWPH7S/p1644326373737959>

_*Version*_ can be stable as in it has been sufficiently tested to the point of not having any
glaring bugs or _runtime stability_ issues.

_*API*,_ as in the _naming/architectural implementation_ is still up for debate and subject to possible change.

The car runs and the engine is stable, but the doors might change to gull wing as opposed to classical or the media interface might change.