# parcelize Published articles for parcelize. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bundling Data for Android Components with Bundle DevFeed: [Bundling Data for Android Components with Bundle]() Original publisher: [Read original article]() Author: Zarah Dominguez Published: 2023-08-21T00:00:00Z Content type: tutorial Language: en Sources: [Zarah Dominguez]() Topics: [Android](), [Code](), [implementation]() Tags: [android](), [code](), [data-class](), [implementation](), [parcelize]() ### AI overview This Android development tutorial explains how to pass multiple values between components using Bundle. It compares passing values individually with grouping them in data classes and discusses using generated implementation to reduce required boilerplate. ### Source excerpt Of all the projects that I have worked on over the years, one thing they all have in common is the need to pass things around. Whether passing stuff to an Activity as Intent extras, a Fragment as arguments or its onSaveInstanceState, or even a ViewModel's SavedStateHandle, the most common way to do it is through a Bundle. ## Пишем плагин Parcelize для компилятора Kotlin под iOS DevFeed: [Пишем плагин Parcelize для компилятора Kotlin под iOS]() Original publisher: [Read original article]() Author: arkivanov (Badoo) Published: 2021-07-09T07:30:01Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [Kotlin](), [iOS](), [Android]() Tags: [android](), [ios](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [native](), [parcelable](), [parcelize](), [tag-25559b1b0132](), [tag-9e9e5e80d07a](), [tag-a071763eb5bb](), [tag-e076f05a03bb]() ### AI overview The article describes the author's experience creating kotlin-parcelize-darwin, a Kotlin compiler plugin for iOS using Kotlin/Native. It explains the Android kotlin-parcelize and Parcelable model as background, then discusses preserving iOS application state with NSCoding and the motivation for an analogous solution. ### Source excerpt В этой статье описан мой опыт по написанию плагина для компилятора Kotlin. Моей главной целью было создание плагина под iOS (Kotlin/Native), аналогичного kotlin-parcelize под Android. Дело в том, что в iOS, как и в Android, приложения тоже могут быть убиты системой, а значит, может возникнуть необходимость сохранять стек навигации и другие данные. В результате работы над этой задачей получился kotlin-parcelize-darwin. Подробности о его создании и применении -- под катом. Читать далее ## A study of the Parcelize feature from Kotlin Android Extensions DevFeed: [A study of the Parcelize feature from Kotlin Android Extensions]() Original publisher: [Read original article]() Author: Christophe Beyls Published: 2019-11-19T07:31:01Z Content type: tutorial Language: en Sources: [Stories by Christophe Beyls on Medium]() Topics: [Kotlin](), [Android](), [Code generation](), [Gradle](), [Android Studio](), [jetbrains](), [Google]() Tags: [android](), [android-app-development](), [android-studio](), [androiddev](), [code-generation](), [google](), [gradle](), [gradle-plugin](), [jetbrains](), [kotlin](), [kotlin-android](), [kotlin-android-extensions](), [parcelable](), [parcelize](), [plugin](), [production]() ### AI overview This article examines Kotlin's Parcelize feature, formerly part of Kotlin Android Extensions, as a production-ready way to generate Android Parcelable implementations. It discusses the feature's generated-code efficiency, plugin support, handling of unsupported types, and lack of runtime library overhead, then introduces the required Kotlin and Android Studio setup. ### Source excerpt Life is too short to waste time on writing Parcelable code Two years ago, I wrote about how you can leverage features of the Kotlin programming language to manually write your Android Parcelable implementations in the most concise and readable way. Does it mean that I always prefer writing this code manually rather than letting a library or tool generate it for me? Of course not: like most developers, I believe that the best code is the code you don't have to write. But I expect the tools I use to meet my quality standards. That's why I tend to be conservative about the dependencies I add to my projects and will always favor official libraries from Jetbrains or Google over third-party solutions. Things have changed for the better since I wrote the previous article: with the release of Kotlin 1.3.40, @Parcelize is now a stable feature provided by the Parcelize Gradle plugin (formerly known as Kotlin Android Extensions). And since version 1.3.60, the Android Studio plugin also properly recognizes the feature as non-experimental so it can finally be considered as production-ready. I previously enumerated a list of some of the negative aspects of third-party Parcelable code generation libraries compared to manual implementation. Here's why I believe @Parcelize stands out from the rest in regard to that list: It's an official plugin made by JetBrains with the collaboration of Google and is guaranteed to be well supported in the future The generated code of @Parcelize is very efficient (as we'll discover further in this article) The CREATOR field doesn't have to be declared at all, along with that easy-to-forget @JvmField annotation Thanks to the Parceler interface, it is possible to write simple plugins to handle unsupported types or override the default implementation No extra classes are created by the plugin. All the generated code is embedded in the annotated class so the app will behave exactly as if you wrote the code yourself There is no runtime library overhead a