v1.0.0 roadmap

[arkivanov]

Required tasks:

• [ ] Stabilise the Compose Animations API (see #110)
• [x] Improve the "Check failed" error message (see #77)
• [x] Comply with the new predictive back gesture in Android 13 (see #156)
• [x] Move Router to stack sub-package and rename it to StackRouter (see #134)
• [x] Remove all deprecated code
• [ ] Add persistent argument to childContext function (see #197)
• [ ] Add extensions for Value (see #200)

Desired tasks:

• [ ] Stabilise Web Routing API (see #111)
• [ ] Stabilise extensions-android module
• [ ] Support Compose for iOS and macOS (see #74)
• [x] Allow safe Router access from childFactory function
• [ ] Remove extensions-compose-jetpack module (see #11)

[Solace-Studios]

@arkivanov For someone starting a new project, would you still recommend using Decompose in its current state?

[arkivanov]

@Solace-Studios Decompose is already used in production in various projects. Version 1.0.0 should be released within a month, however I don't expect any significant API changes. If you like Decompose then absolutely go ahead and use it.

[Solace-Studios]

@arkivanov That's great news! I actually just found out about it. I've been looking into RIBs as an architecture for a new cross platform comparable product to Uber these last few weeks. I was wondering how I was going to support navigation, recovery from process death, and integrate Compose and SwiftUI. This just happens to support all those things it seems. I'm running through the sample, I like it so far. Are you aware of any more companies using Decompose than this list?

[arkivanov]

Are you aware of any more companies using Decompose

Yes I am, however I'm not sure if I can mentioned anything about it, sorry. You can try searching through GitHub, there are 3k+ code search results.

[arkivanov]

Version 1.0.0 is released!