1.3 (Feb 22, 2018)
Feb 14, 2017
Feb 22, 2018
Source code
APK file

Show card


Let your IDE create your bundles/intents for you. This library is:

  • reflection free
  • typesafe
  • fast
  • very small - just the annotation interfaces are added to your akp (4 methods, 6 fields)
  • supports any class: Activities, Fragments and any other class => use one processor for all your needs
  • creates nice helper functions if appropriate

How to add it to your project - Gradle (via JitPack.io)

  1. add jitpack to your project's build.gradle:
repositories {
    maven { url "https://jitpack.io" }
  1. add the compile statement to your module's build.gradle and apply the apt plugin:
dependencies {
    compile 'com.github.MFlisar.BundleArgs:bundleargs-annotation:1.3'
    annotationProcessor 'com.github.MFlisar.BundleArgs:bundleargs-processor:1.3'

Usage - Definitions

Here's a simple example that demonstrates the use in ANY class that needs a Bundle argument:

public class Test
    Long id;
    String value;
    @Arg @Nullable
    String optionalValue;
    // define a constructor with Bundle args and the processor will create a build method that directly creates an object of this class
    public Test(Bundle args)
        TestBundleBuilder.inject(args, this);

And this is how you define it in an activity:

public class MyActivity extends Activity
 String stringArg;

 public void onCreate(Bundle savedInstanceState)
  MyActivityBundleBuilder.inject(getIntent().getExtras(), this);

Usage - Builder

  1. If you have defined the default costructor with a bundle as args in it, you can directly create a class like this:
Test test = new TestBundleBuilder()
  1. You can always just create a Bundle with the builder like following:
Bundle bundle = new TestBundleBuilder()
  1. You can always just create an Intent with the builder like following (if the annotated class is an Activity or if the boolean flag alwaysAddIntentBuilder of the BundleBuilder is set to true:
Intent intent = new TestBundleBuilder()
  1. If the annotated class extends Activity, following method will be added to start the activity directly;
new MyActivityBundleBuilder()
  1. if the enable useConstructorForMandatoryArgs in the @BundleBuilder annotation, the generated builder will force you to set mandatory fields via the constructor like following:
Bundle b = new TestBundleBuilder(1L, "Test") // you MUST supply mandatory fields
 .optionalValue("optionalValue") // optional fields can be set via builder functions



You can define some setup variables like following (each one is optional):

@BundleBuilder(useConstructorForMandatoryArgs = true, setterPrefix = "with", generateGetters = false, generateIntentBuilder = false)
  • boolean useConstructorForMandatoryArgs(): default: false... if true, all mandatory fields will be part of the constructor, otherwise all mandatory fields need to be set with the builder style
  • String setterPrefix(): default ""... if not empty, all setters for the builder will be prefixed with this String. I.e. the field customField will be settable via a function builder.withCustomField(...) if the setterPrefix == "with"...
  • boolean generateGetters(): default: false... defines, if the builder offers getter functions for each field to retrieve fields from a bundle directly
  • boolean generateIntentBuilder(): default: false... defines, if the buildIntent method is generated for non activity classes as well


 @Arg(value = "", optional = false)
  • String name(): default: ""... if set, the builder setter will get the custom name instead of the one derived from the field name
  • boolean optional(): default: false... if true, fields are optional, if not, they must be set via constructor or via setter


For an example with activities, check out the demo: Demo


This project is generally based on https://github.com/emilsjolander/IntentBuilder but was improved and restructured heavily in the meantime.


  • conductor/fragment/class demo?
  • ???