AirCycle Compiler - flexible binding of Android Activity lifecycle callbacks to fields




Binds Android Activity lifecycle callbacks to Activity fields annotated with @AirCycle.

Fields annotated with @AirCycle that are defined in an Activity will receive lifecycle callbacks of the enclosing Activity. The Activity does NOT need to implement any interface or extend any specific base class.

The field itself also does NOT need to implement any interface or extend any specific base class.

The binding class is generated in compile time using Java annotation processing, NO reflection is used at runtime.


public class MyActivity extends AppCompatActivity {

    @AirCycle LifecycleListener myListener;

    protected void onCreate(Bundle savedInstanceState) {
        MyActivityAirCycle.bind(this); // generated by the AirCycle annotation processor

        myListener = new LifecycleListener();
public class LifecycleListener {

    // no arguments 
    public void onCreate() {
        // The bound MyActivity was created

    // can also pass the Activity
    public void onCreate(MyActivity activity) {
        // The bound MyActivity was created

    // or just a Bundle 
    public void onCreate(Bundle bundle) {
        // The bound MyActivity was created

    // ...

    // ActivityLifecycleCallbacks method naming is also supported
    public void onActivityDestroyed(AppCompatActivity activity, Bundle bundle) {
        // The bound MyActivity was destroyed

    // can pass the base Activity as well
    public void onDestroy(AppCompatActivity activity) {
        // The bound MyActivity was destroyed

    // arguments order does not matter in listener methods
    public void onDestroy(Bundle bundle, AppCompatActivity activity) {
        // The bound MyActivity was destroyed

AirCycle annotation processor will generate a binding class for the Activity, named <YourActivity>AirCycle with a static bind method.

You MUST call MyActivityAirCycle.bind(this) BEFORE calling super.onCreate(savedInstanceState), otherwise the bound listener will NOT receive the first onCreate call for the Activity.

Activity lifecycle callbacks

The following Activity lifecycle callbacks are supported:

  • onCreate() (with optional Bundle savedInstanceState argument)
  • onStart()
  • onResume()
  • onPause()
  • onStop()
  • onSaveInstanceState() (with optional Bundle outState argument)
  • onDestroy()


Fields annotated with @AirCycle can be plain Java classes or interfaces (POJOs) that have public lifecycle callback methods. Method name defines the bound Activity lifecycle callback.

lifecycle callback listener method alternative listener method optional Bundle arg?
onCreate() onCreate() onActivityCreated()
onStart() onStart() onActivityStarted() -
onResume() onResume() onActivityResumed() -
onPause() onPause() onActivityPaused() -
onStop() onStop() onActivityStopped() -
onSaveInstanceState() onSaveInstanceState() onActivitySaveInstanceState()
onDestroy() onDestroy() onActivityDestroyed() -

ALL listener methods can optionally have the bound Activity instance as the method argument. Unlike method names, argument names do NOT matter.

Listener callbacks

Listener callbacks are invoked on Android's main thread. Callbacks are invoked AFTER the respective method returns.

Built-in listeners

The following listener interfaces are bundled with the library:


Since its method names are also supported by AirCycle, you can also use Application.ActivityLifecycleCallbacks as a bound listener.

Custom listeners

Any class or interface that has at least one listener method can be bound as an AirCycle listener.

Custom listener from the example app:

public class CustomListener {

    public void onCreate() {


    public void onCreate(CustomListenerActivity activity) {


    public void onCreate(Bundle bundle) {


    public void onSaveInstanceState(AppCompatActivity activity, Bundle bundle) {


    public void onActivitySaveInstanceState(Bundle bundle, Activity activity) {


Multiple methods

As seen above, multiple methods are supported for the same lifecycle callback (either overriden with different arguments or using an alternative supported name). The order and naming of arguments is NOT important. No arguments are necessary for any lifecycle method.

Multiple listeners

A single Activity can have multiple fields bound to its lifecycle.

Multiple listeners Activity from the example app:

public class MultipleListenersActivity extends AppCompatActivity {

    @AirCycle ActivityAirCycleLogger airCycleLogger;
    @AirCycle final ActivityBundleAirCycleLogger bundleAirCycleLogger = new ActivityBundleAirCycleLogger();

    // ...

How does it work?

AirCycle generates one binding class per-Activity containing 1 or more @AirCycle annotated field(s). Upon calling bind on a generated class passing the Activity instance, Application.ActivityLifecycleCallbacks are registered on the Activity's app. These are automatically unregistered for the Activity once onDestroy is called.

The listener callbacks are invoked only if the listener instance is not null and are dispatched only to their respective bound listener instances.


Annotate your Dagger injected presenters to automatically bind them to the Activity lifecycle, i.e.

@AirCycle @Inject MyPresenter presenter;


AirCycle uses compile time annotation processing to generate Activity binding classes, NO reflection is used at runtime.


Since all classes are generated in compile time and no reflection is used in runtime, you can safely use AirCycle with ProGuard.

Include in your project

buildscript {
    dependencies {
        classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'

apply plugin: ''

dependencies {
  compile 'TODO'
  apt 'TODO'

Inspiration and motivation

Inspired by SoundCloud's LightCycle library. Kudos to those guys.

Compared to SoundCloud's library, AirCycle supports passing of Activity lifecycle callbacks without the need to extend from a specific base Activity. Additionally, the listener classes are completely flexible, without the need to extend from any class or interface. This enables more flexibility when developing and further promotes composition over inheritance.

The cost of this flexibility is only supporting Activity lifecycle callbacks included in Application.ActivityLifecycleCallbacks (since API level 14) and no support for Fragment lifecycle callbacks.

Change Log



Open source, distributed under the MIT License. See LICENSE for details.