Jetpack compose is production ready :tada:
# android
h
Jetpack compose is production ready 🎉
😂 3
nope 9
g
Ehh, I really hate this “production ready/not ready” applied to anything, it's such a vague term, which is completely useless
☝️ 1
➕ 1
Beta itself means more API stability, but does something super significant changed from previous alpha which made it more “production ready”? Yeah, maybe some bugs fixed, more API stability, but nothing significant changes in terms of "ready"
production ready is not some global category or state of library, it's ready or not for you and only for your production, stability of library/framework is not determinate by it version numer: 72.2.2 or is it 0.7.0
sorry for this runt, but I have feeling that many developers expect super simple answers for complicated questions like “can we use N for our project and release it”
👍 3
p
No it's not production ready
To quote https://android-developers.googleblog.com/2021/02/announcing-jetpack-compose-beta.html
Now is a great time to start learning Compose and begin planning for how you will use it in an upcoming project or feature once it reaches 1.0 later this year.
That's not the exact definition of production ready
☝️ 1
👍 3
g
Again, I think this quite for announcement doesn’t discurage anyone from using on prod, it’s always your own risk, fact that it’s not perfect experince and that API is not 100% stable (and definitely will be at least changed, deprecated) doesn’t mean that you cannot use it for production
p
To me that reads like I sould not use it in production before 1.0
g
It just an announcement text with some vague sentences 🤷
p
Yeah these shouldn't be vague, these should give information
g

https://youtu.be/vRjJAWh6JPE?t=1433▾

these should give information
It's your decision, what kind information do you expect? Beta just means more stable API
Do they recommend to release it now? No, they do not recommend of course, because next day someone will come to them and say that their project is blocked by a bug. would they actively prevent it? Why should they do this? It will be released this year, they actually need early adopters before release
z
What even is “production”? Eg if you are building things with compose and ship them behind a feature flag to a closed beta group of users. Is that production? It probably is as far as those users are concerned, but you’re acknowledging and mitigating the risk by limiting exposure and keeping the ability to turn it off quickly if issues pop up. “Ready” is just as ambiguous. If you build a feature with compose, developers like it, you test it internally, and it meets all your requirements, gradually roll it out to beta users and everything looks good, roll it out generally and still looks good – I’d call that ready, even if there is some major feature missing that you don’t care about for your feature.
➕ 2