bluelinelabs/conductor

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

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 24 minutes ago
Type:FrameworkCategory(s):AndroidMobile & Desktop
Added to GitGenius on September 17th, 2026
Created on March 16th, 2016
Open Issues & Pull Requests: 111 (+0)
GitHub issues: Enabled
Number of forks: 338
Total Stargazers: 3,897 (+0)
Total Subscribers: 114 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 29.5 hours
Mean response time: 192.9 days
90th percentile: 384.6 days
Tracked items: 2

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 777 days
Stale 30+ days: 2
Stale 90+ days: 2

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

No issue events were indexed in the last 7 days.

Detailed Description

Conductor is a framework for building View-based Android applications using a single Activity architecture.

Conductor solves the complexity of managing UI state and navigation in Android by providing a lightweight wrapper around standard Views that replaces Fragments. The framework centers on the Controller, a simpler alternative to Fragments with more predictable lifecycle management. Navigation and backstack handling are managed through Router objects, which coordinate with ControllerChangeHandler instances to animate transitions between Controllers. This approach eliminates much of the boilerplate associated with Fragment-based architectures while maintaining full control over the View layer.

Conductor suits developers building single-Activity applications who want Fragment-like lifecycle management without Fragment complexity. The framework is architecture-agnostic and works equally well with MVP, MVVM, MVC, or other patterns, imposing no design constraints on developers. It handles state persistence, activity result callbacks, permission request callbacks, and view transitions out of the box. The tool is particularly valuable for teams that have found Fragments difficult to reason about or that prefer explicit View management over the Fragment abstraction.

Development on the project shows sustained production use at significant scale, with the framework already deployed in applications serving millions of users. The team has maintained the codebase through a major version transition, with version 4.0 in preview status while maintaining the same quality standards as the stable 3.x release. A demo application is included in the repository demonstrating both basic and advanced usage patterns.