cesarferreira/dryrun

☁️ Try the demo project of any Android Library

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 30 minutes ago
Type:CLI ToolCategory(s):AndroidCLI UtilitiesMobile & Desktop
Added to GitGenius on September 18th, 2026
Created on August 19th, 2015
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 276
Total Stargazers: 3,787 (+0)
Total Subscribers: 77 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 81.0 days
Mean response time: 63.5 days
90th percentile: 84.0 days
Tracked items: 3

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

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

  • wontfix (4)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

dryrun is a command-line tool that lets you quickly test Android libraries hosted online without manual setup.

The tool solves the friction of evaluating Android libraries by automating what would otherwise be a multi-step process. Instead of downloading a repository, extracting it, opening Android Studio, importing the project, syncing Gradle, and running it on a device, dryrun handles all of this from a single command. It clones the library repository, builds it, and deploys it to a connected device or emulator in seconds. The tool also supports testing private repositories, eliminating the need to make code public just to evaluate it.

The tool suits developers who want to quickly prototype with or evaluate Android libraries without the overhead of a full IDE workflow. It is particularly valuable when you need to test multiple libraries in succession, since there is no cleanup required afterward and no need to wait for Android Studio to load. The README contrasts dryrun's approach with the manual alternative of downloading, extracting, importing, syncing, running, and then deleting the project and zip file.

The project maintains a stable codebase with closed issues addressed over time. Development activity shows consistent engagement with bug reports and feature requests through the issue tracker.