zfdang/android-touch-helper

AdSkip — an Android assistant for automatically skipping app launch ads

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 36 minutes ago
Added to GitGenius on September 12th, 2026
Created on October 16th, 2020
Open Issues & Pull Requests: 64 (+0)
GitHub issues: Enabled
Number of forks: 506
Total Stargazers: 5,312 (+0)
Total Subscribers: 28 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 81.2 days
Mean response time: 363.8 days
90th percentile: 1077.6 days
Tracked items: 4

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

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

Android-Touch-Helper is an Android accessibility service app that automatically skips splash ads and launch advertisements.

The tool addresses the problem of intrusive splash ads by leveraging Android's Accessibility Service to inspect on-screen content and detect skip targets. It offers three detection methods: keyword-based detection that looks for buttons containing specific skip-related text, UI control detection for app-specific predefined controls, and screen position detection for clicking configured areas. The project prioritizes privacy by design—it is open source, requires no network or storage permissions, and does not collect or upload personal data.

Developers should adopt this tool if they want to automate ad-skipping across multiple Android apps without the privacy risks associated with closed-source alternatives. It suits users frustrated with repetitive splash screens across their installed applications. The project explicitly acknowledges it is a personal project with limited active maintenance, so contributors should expect slower response times for feature requests, though pull requests are still reviewed and merged when feasible.

Development activity shows the project is in maintenance mode rather than active expansion. The maintainer has stated they no longer have substantial time for active improvement or new feature support. However, the project remains responsive to community contributions through pull requests, indicating willingness to integrate external work despite bandwidth constraints.