# ParcelablePlease: Generating Android Parcelable Code with Annotation Processing

DevFeed: [ParcelablePlease: Generating Android Parcelable Code with Annotation Processing](<https://devfeed.tech/articles/parcelableplease-25462.md>)

Original publisher: [Read original article](<https://hannesdorfmann.com/android/parcelableplease/>)

Author: Hannes Dorfmann

Published: 2014-09-24T09:00:00Z

Content type: tutorial

Language: en

Sources: [Hannes Dorfmann](<https://devfeed.tech/sources/hannes-dorfmann.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>), [Code](<https://devfeed.tech/topics/code.md>), [Java](<https://devfeed.tech/topics/java.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [annotation-processor](<https://devfeed.tech/tags/annotation-processor.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [code](<https://devfeed.tech/tags/code.md>), [fragments](<https://devfeed.tech/tags/fragments.md>), [java](<https://devfeed.tech/tags/java.md>), [parcelable](<https://devfeed.tech/tags/parcelable.md>)

## 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