Need help with Conductor?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

3.8K Stars 340 Forks Apache License 2.0 384 Commits 116 Opened issues


A small, yet full-featured framework that allows building View-based Android applications

Services available


Need anything else?

Contributors list

Travis Build Android Arsenal Javadocs


A small, yet full-featured framework that allows building View-based Android applications. Conductor provides a light-weight wrapper around standard Android Views that does just about everything you'd want:

| | Conductor | |-----------|-------------| :tada: | Easy integration :pointup: | Single Activity apps without using Fragments :recycle: | Simple but powerful lifecycle management :train: | Navigation and backstack handling :twistedrightwardsarrows: | Beautiful transitions between views :floppydisk: | State persistence :phone: | Callbacks for onActivityResult, onRequestPermissionsResult, etc :europeanpostoffice: | MVP / MVVM / MVI / VIPER / MVC ready

Conductor is architecture-agnostic and does not try to force any design decisions on the developer. We here at BlueLine Labs tend to use either MVP or MVVM, but it would work equally well with standard MVC or whatever else you want to throw at it.


implementation 'com.bluelinelabs:conductor:3.1.1'

// AndroidX Transition change handlers: implementation 'com.bluelinelabs:conductor-androidx-transition:3.1.1'

// ViewPager PagerAdapter: implementation 'com.bluelinelabs:conductor-viewpager:3.1.1'

// ViewPager2 Adapter: implementation 'com.bluelinelabs:conductor-viewpager2:3.1.1'

// RxJava2 Autodispose support: implementation 'com.bluelinelabs:conductor-autodispose:3.1.1'

// Lifecycle-aware Controllers (architecture components): implementation 'com.bluelinelabs:conductor-archlifecycle:3.1.1'


Just use

as your version number in any of the dependencies above and add the url to the snapshot repository:
allprojects {
  repositories {
    maven { url "" }

Components to Know

| | Conductor Components | ------|------------------------------ Controller | The Controller is the View wrapper that will give you all of your lifecycle management features. Think of it as a lighter-weight and more predictable Fragment alternative with an easier to manage lifecycle. Router | A Router implements navigation and backstack handling for Controllers. Router objects are attached to Activity/containing ViewGroup pairs. Routers do not directly render or push Views to the container ViewGroup, but instead defer this responsibility to the ControllerChangeHandler specified in a given transaction. ControllerChangeHandler | ControllerChangeHandlers are responsible for swapping the View for one Controller to the View of another. They can be useful for performing animations and transitions between Controllers. Several default ControllerChangeHandlers are included. RouterTransaction | Transactions are used to define data about adding Controllers. RouterTransactions are used to push a Controller to a Router with specified ControllerChangeHandlers, while ChildControllerTransactions are used to add child Controllers.

Getting Started

Minimal Activity implementation

public class MainActivity extends Activity {

private Router router;

protected void onCreate(Bundle savedInstanceState) {


    ViewGroup container = (ViewGroup) findViewById(;

    router = Conductor.attachRouter(this, container, savedInstanceState);
    if (!router.hasRootController()) {
        router.setRoot(RouterTransaction.with(new HomeController()));

public void onBackPressed() {
    if (!router.handleBack()) {


Minimal Controller implementation

public class HomeController extends Controller {

protected View onCreateView(@NonNull LayoutInflater inflater, @NonNull ViewGroup container, @Nullable Bundle savedViewState) {
    View view = inflater.inflate(R.layout.controller_home, container, false);
    ((TextView) view.findViewById("Hello World");
    return view;


Sample Project

Demo app - Shows how to use all basic and most advanced functions of Conductor.

Controller Lifecycle

The lifecycle of a Controller is significantly simpler to understand than that of a Fragment. A lifecycle diagram is shown below:

Controller Lifecycle

Advanced Topics

Retain View Modes

can be called on a
with one of two values:
, which will release the
's view as soon as it is detached from the screen (saves memory), or
, which will ensure that a
holds on to its view, even if it's not currently shown on the screen (good for views that are expensive to re-create).

Custom Change Handlers

can be subclassed in order to perform different functions when changing between two
. Two convenience
subclasses are included to cover most basic needs:
, which will use an
object to transition between two views, and
, which will use Lollipop's
framework for transitioning between views.

Child Routers & Controllers

can be called on a
in order to get a nested
into which child
s can be pushed. This enables creating advanced layouts, such as Master/Detail.

RxJava Lifecycle

If the AutoDispose dependency has been added, there is a

available that can be used along with the standard AutoDispose library.

Community Projects

The community has provided several helpful modules to make developing apps with Conductor even easier. Here's a collection of helpful libraries:


Copyright 2020 BlueLine Labs, Inc.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.