Replies: 1 comment 3 replies
-
Parcelable allows us to hook screens (and by extension, our whole back stack) directly into the Android bundle system. In K2 parcelize supports custom annotations, so it's trivial to support and you can continue to write screens in commonMain. The only real annoyance I've ever seen put forward for kotlinx-serialization is the source set bit (which is solved in K2 above), but never anything actually gained from using serialization or acknowledgement of what we lose from dropping parcelable. So - what would we gain that is worth that cost or at least offers equivalent integration? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Parcelable
is an Android only thing and, because of that, it requires theCommonParcelize
thing. Is there any disadvantage on moving to Kotinx Serialization instead?Beta Was this translation helpful? Give feedback.
All reactions