[Survey] Parcelize for Darwin (Apple) targets
arkivanov opened this issue · 7 comments
I would like to understand, do we need Parcelize support for Darwin (Apple) targets? I built an experimental kotlin-parcelize-darwin compiler plugin, which is similar to kotlin-parcelize. We could enable it in a separate branch and start publishing the experimental version of decompose module, with a version suffix. More info in my article.
Please put 👍 if you think it is useful, or 👎 if you believe the state preservation is not important on iOS, watchOS, macOS, etc. Please feel free to leave a comment or ask a question.
It was actually strange to see you implementing this because I believe you've said parcelize plugin doesn't make sense on Apple platforms since if I recall the platform does it automatically, but I may confuse this with another state preservation (view or something else). But nonetheless Apple still has NSConding protocols, so they serve some value. I might investigate into it a bit and later provide more feedback. I very much appreciate your work and contribution into the community
It was actually strange to see you implementing this because I believe you've said parcelize plugin doesn't make sense on Apple platforms since if I recall the platform does it automatically, but I may confuse this with another state preservation (view or something else). But nonetheless Apple still has NSConding protocols, so they serve some value. I might investigate into it a bit and later provide more feedback. I very much appreciate your work and contribution into the community
Thanks! I don't remember such words from my side. On iOS, the process death due to memory pressure is much more rare than on Android. And so it might be acceptable to loose the state (both data and navigation stack) in such rare cases. But it is still the case, and it might be a requirement for an app to support it.
It probably refers to the fact that Android and iOS handle configuration changes differently, I'm trying to find the exact text so I could quote you, but I'm having a little trouble doing it, so maybe if you give me some time, I can provide it to you :)
Probably this, but maybe somewhere else too: https://proandroiddev.com/decompose-experiments-with-kotlin-multiplatform-lifecycle-aware-components-and-navigation-a04ef3c7f6a3
Thanks, but it does not sound like "parcelize plugin doesn't make sense on Apple platforms". Am I missing something? Anyway, I think it does make sense, but not so important as on Android. :-)
Probably doesn't, although I remember a little different approach to saying this, which as I said I couldn't easily find. If I find it, I'll definitely recall if you don't mind, but yeah. If you feel it makes sense, maybe it's a game-changer! Even a little :D. I'm interested in your colleagues opinion on this survey. What do they think about it?