# parcelable Published articles for parcelable. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Пишем плагин 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. Подробности о его создании и применении -- под катом. Читать далее ## Decoding Handler and Looper in Android DevFeed: [Decoding Handler and Looper in Android]() Original publisher: [Read original article]() Published: 2019-12-24T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Android](), [class](), [callback](), [interface](), [Code]() Tags: [abstraction](), [android](), [callback](), [class](), [code](), [interface](), [object](), [parcelable](), [payload](), [thread]() ### AI overview This tutorial explains Android's Handler and Looper, describing Looper as an event-loop abstraction that drains a MessageQueue and Handler as an abstraction for posting, removing, and handling queued events. It also covers their relationships and the structure of Message objects. ### Source excerpt Introduction Handler and Looper are one of the main low-level Android OS things, which almost nobody uses directly (at least nowadays). But they are at the core, so many other high-level solutions are based on them. Therefore one should know what Handler and Looper are, what and how they are doing. In this article we'll try to understand Handler and Looper in Android. What, how and why we might need them. We'll start from some basic knowledge on classes and what they are doing, continue with relations between them. Then we'll look at each class separately trying to dive deep into details. And will finish with some canonical examples on where they can be used. ## 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 ## Note to Future Me -- Testing Intents with Matchers DevFeed: [Note to Future Me -- Testing Intents with Matchers]() Original publisher: [Read original article]() Published: 2018-01-26T14:54:45Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Testing](), [test](), [parcelable](), [Code](), [Library](), [Kotlin]() Tags: [code](), [data](), [data-class](), [error-messages](), [kotlin](), [library](), [parcelable](), [testing](), [testing-matchers](), [tests]() ### AI overview This tutorial demonstrates testing Android activity intents with Espresso and Hamcrest matchers in Kotlin. It passes a parcelable data object between activities, verifies the intent extra and its properties, and shows how custom matchers can improve error messages and test only selected properties. ### Source excerpt I want to make my little experiments public and save them as a reminder for future me. So here is yet another post on Matchers and Espresso testing. I want to test this: First activity starts another activity at a button click. First activity passes a parcelable object to the second activity. Test that the intent that starts the second activity contains the object with the correct properties. I built a contrived example, MainActivity collects some info and passes this to StarActivity in a parcelable called ContrivedParams. See the sample code on GitHub. To write the tests I brushed up on Hamcrest[1][2][3]: a library that makes it easier to write readable tests. Instead of assert(expected==actual) you can write almost-english assertThat(actual, is(expected)) which is a sugar coated version of assertThat(actual is(equalto(expected))) Sadly though is is a hard keyword in Kotlin so I ended up using the isA() and equalTo() varieties of calls rather than escaping is with backticks. Another reason to use Hamcrest -- better error messages. Compare these two messages. java.lang.AssertionError at net.maiatoday.hellointentmatcher.ContrivedParamsTest.showErroMessagesTest(ContrivedParamsTest.kt:37) with the message given by a custom matcher java.lang.AssertionError: Expected: title should return "Hello World" but: was "Hello World!" at net.maiatoday.hellointentmatcher.ContrivedParamsTest.showErroMessagesTest(ContrivedParamsTest.kt:42) or the error message given by an object matcher java.lang.AssertionError: Expected: but: was at net.maiatoday.hellointentmatcher.ContrivedParamsTest.showErroMessagesTest(ContrivedParamsTest.kt:47) The parameters for the second activity is passed in a parcelable data class. I used the Espresso-intents library . Start the activity with an IntentsTestRule. The IntentsTestRule initialises the Espresso intents before each ## ParcelablePlease: Generating Android Parcelable Code with Annotation Processing DevFeed: [ParcelablePlease: Generating Android Parcelable Code with Annotation Processing]() Original publisher: [Read original article]() Author: Hannes Dorfmann Published: 2014-09-24T09:00:00Z Content type: tutorial Language: en Sources: [Hannes Dorfmann]() Topics: [Android](), [Boilerplate](), [Code](), [Java]() Tags: [android](), [annotation-processor](), [blog-post](), [code](), [fragments](), [java](), [parcelable]() ### AI overview This tutorial introduces ParcelablePlease, an Android annotation processor intended to reduce boilerplate code when implementing Parcelable. It compares the approach with Parceler and AutoParcel, explaining their generated wrapper or subclass designs and compatibility trade-offs. ### Source excerpt In my last blog post I have introduced FragmentArgs an Annotation Processor for Fragments that reduces writing boilerplate code. In this post I want to talk about a similar problem android developer face: Writing boilerplate code for Parcelable This post is part of a series of posts about useful annotation processors like FragmentArgs or AnnotatedAdapter