johncarl81/parceler

:package: Android Parcelables made easy through code generation.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 19th, 2026
Created on July 3rd, 2013
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 272
Total Stargazers: 3,528 (+0)
Total Subscribers: 69 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

Parceler is a code generation library that eliminates boilerplate when implementing Android Parcelables.

Android Parcelables enable efficient serialization of Java objects between contexts, performing roughly ten times faster than traditional serialization. However, implementing Parcelable requires writing substantial boilerplate: mirroring read and write methods that access fields in identical order, and defining a static Creator field. Parceler solves this by generating all required Parcelable code automatically. You annotate a plain Java object with @Parcel, and the tool uses Java's JSR-269 annotation processor to generate the implementation at compile time, with no manual tool invocation needed. Objects are wrapped and unwrapped using the Parcels utility class, which integrates seamlessly with Android Bundles and Intents.

Parceler suits any Android project that passes objects between activities or fragments. It works best with public fields or getter methods; private fields incur a reflection penalty. The tool handles the common case of serializing all instance fields by default, making it immediately useful for straightforward data classes without configuration overhead.

The project maintains active issue tracking and community support channels. Development follows a continuous integration pipeline with automated testing on each change.