<@U3JQ35YQK> In your compose video, you made it so...

# compose

[spierce7]

@romainguy In your compose video, you made it sound like when alpha is released later this summer, that you encourage people using it in applications. Do you mean production applications, because it’s stable, and you are expecting that some APIs are missing, or there might be some slight changes, or do you mean only in non-production applications?

[Leland Richardson [G]]

I think the rough idea is:

“Alpha”: you can make quality applications with this, but the APIs are still subject to change.
“Beta”: Alpha but APIs are stable, barring any significant bugs/issues found in the wild
“1.0”: APIs are truly stable

[Leland Richardson [G]]

the dev previews have been extremely valuable to get feedback and iterate, but usage is still somewhat “toy app” level and APIs are incomplete. Once Alpha hits, we expect the real world usage will increase and as a result we might see feedback that didn’t come in at an earlier stage because the use cases changed. We want to have an opportunity to act on that feedback before APIs truly stabilize.

[rophuine]

I've been able to dive in and build a functional (somewhat complete) app for a real use case, and it's been stable and able to do what I need. My own testing suggests it would be stable enough to push out to the app store, but I'm in no rush.

I'd say the two biggest issues right now are discoverability (which is helped massively by being able to ask in here when I can't work out how to do something!) and obviously the regular API changes.

[romainguy]

Those two things are what will gradually improve from alpha to beta to 1.0

[rophuine]

Yep, I'm loving Compose even now so certainly looking forward to it getting even easier 🙂