minitap-ai/mobile-use

AI agents can now use real Android and iOS apps, just like a human.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on August 16th, 2025
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 285
Total Stargazers: 3,172 (+1)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 45.8 hours
Mean response time: 17.0 days
90th percentile: 60.3 days
Tracked items: 38

How this project is maintained

Work labelled "bug" is answered fastest, typically in about 11 hours, while "enhancement" waits about 10 days. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (17)
  • enhancement (11)
  • documentation (1)
  • good first issue (1)
  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Mobile-use is a framework that enables AI agents to interact with real Android and iOS applications as a human would.

The framework addresses the challenge of giving AI agents the ability to control and navigate mobile apps through direct interaction rather than API calls or predefined integrations. It works by allowing agents to perceive the mobile interface visually and execute touch-based actions, mimicking human user behavior. This approach lets agents handle any app without requiring app-specific code or integrations, making it applicable to a wide range of mobile testing, automation, and interaction scenarios.

Teams should consider this tool when they need AI agents to perform tasks across diverse mobile applications without building custom connectors for each one. It suits projects involving mobile app testing, user workflow automation, or scenarios where agents must interact with apps as end users would. The framework is particularly valuable when dealing with legacy apps, third-party applications, or situations where API access is unavailable or impractical.

The project shows active development with regular commits and ongoing refinement of core functionality. The codebase demonstrates a focus on practical implementation of agent-app interaction patterns. Documentation and examples are maintained to support adoption and use case exploration.