What changed
FACT (source: Android Developers blog, June 2026): Android 17 enforces per-app memory limits scaled to device RAM and kills violating apps with no stack trace. FACT (source: Android Developers blog, May/June 2026): the Android CLI hit stable 1.0 and exposes builds, profilers, Compose previews, and device streaming to coding agents programmatically. FACT (source: Vercel blog): the autonomous-investigation-plus-approval-gated-remediation pattern is shipping in production at Vercel, proving the interaction model.
Why now
Apps are hitting silent kills during the Android 17 migration window right now (shipped June 2026). Pain is at peak, first-party diagnostics are absent by design (no stack trace), and the agent-drivable CLI is only weeks old — so almost nobody has built automation on it yet. This window closes as publishers fix their apps or Google ships better first-party diagnostics.
Converging signals
(1) Android 17 memory-limit enforcement with silent kills creates an invisible, urgent failure mode for every memory-heavy app. (2) Android CLI 1.0 makes heap profiling and builds agent-drivable without brittle scripting. (3) Vercel Agent validates investigate-then-approval-gated-fix as a sellable product shape. (4) Two separate Android posts push the same agent-tooling story, signaling Google wants agents in this loop.
Customer pain
HYPOTHESIS (mechanism is factual, magnitude is not yet evidenced): users experience the app 'just closing' with no crash report; Crashlytics/Sentry show nothing actionable because there is no stack trace; ratings and retention decay while the dev team can't reproduce. Deadline-driven, diagnosable, and invisible to existing crash tooling — the best kind of pain to sell against. No direct evidence of publishers complaining or paying yet; that must be validated in week 1.
Who pays
Small-to-mid Android app publishers (games, media, camera/photo, RN/Flutter apps with native leaks) whose revenue depends on retention and ratings, and Android dev agencies who can white-label the audit. Not enterprises — indie and SMB publishers reachable in dev communities.
Solved today
Manual Android Studio Memory Profiler sessions by senior devs; LeakCanary in debug builds; crash SDKs (Crashlytics, Sentry, Embrace, Instabug) that catch OOM signals poorly and catch silent LMK kills barely or not at all; or hourly perf consultants at $150-250/hr.
Why current solutions are bad
Silent limit kills produce no stack trace, so crash SDKs are structurally blind to the new failure mode. LeakCanary finds Activity/Fragment leaks in debug, not native/bitmap/service-level growth under real limits. Manual profiling is expert-scarce and episodic; consultants are slow and expensive. Nothing today runs continuous, automated heap analysis tied to fix PRs.
Proposed product
'Memory Compliance' agent service: customer grants repo access (or ships an AAB/APK for the read-only tier); pipeline builds the app via the stable CLI, drives scripted usage on device/emulator, captures heap dumps and memory timelines, an agent localizes leak roots to code, and opens approval-gated fix PRs with before/after memory graphs. Tier 1: fixed-price audit + report. Tier 2: recurring per-release regression check in CI. Human (Charles) reviews every PR before it reaches the customer — the agent does the labor, he does QA.
MVP version
No product UI at all. A pipeline (Python + Android CLI + headless Claude Code, i.e. exactly the stack he already runs for Convergence) executed against 5 popular open-source Android apps, producing public 'Android 17 memory compliance reports' and real fix PRs to those repos. The PRs and reports ARE the MVP and the marketing. Buildable in 2-3 weeks solo.
30-day build
Week 1: validate demand before building — search r/androiddev, GitHub issues, and X for 'Android 17 killed/silent kill/memory limit' complaints; if there is no visible wailing, kill or shelve. Weeks 2-4: build the pipeline, run it on 5 OSS apps, publish reports + upstream PRs, post results in r/androiddev, Android Dev Discords, and Hacker News. Open a simple order page: '$499 memory-kill audit, report + fix PRs in 7 days, refund if we find nothing.'
60-day build
Convert inbound from the public reports into 5-10 paid audits. Systematize: templated report, scripted device-usage flows per app category. Pitch 2-3 Android dev agencies on white-label audits. Start upsell experiments: per-release CI regression check at $199-399/mo per app.
90-day revenue plan
Target: 10-15 audits at $499-999 ($5k-12k one-off) plus 3-5 monitoring subscriptions ($1k-2k MRR). That is realistic solo revenue, not a startup outcome — this is a cash-flow wedge, not yet a company.
Distribution path
Demonstrated value, zero relationship sales — his stated mode: public teardown reports and real merged PRs on known OSS apps, posted where Android devs already are (r/androiddev, HN, Android Weekly, Kotlin/Android Discords). Cold outreach only to publishers whose Play Store reviews already mention 'app keeps closing' post-Android-17 — review mining is squarely his complaint-mining strength.
Pricing hypothesis
$499 intro audit (first 10, then $999) per app; $199-399/mo per app for per-release regression monitoring; agency white-label at ~50% margin share. Per-fix-PR pricing is tempting but misaligns incentives; avoid.
Technical difficulty
Moderate. The CLI handles build/profile mechanics, but reliable leak localization across arbitrary codebases (native code, Unity, React Native, obfuscated builds) is genuinely hard; expect a meaningful fraction of audits to need manual hours. Scripting representative app usage per customer is the hidden cost. Mitigation: constrain v1 to Kotlin/Java Compose-era apps and say no to Unity/RN initially.
Legal / regulatory risk
Low. Customer authorizes analysis of their own app/repo. Needs a basic services agreement, code-confidentiality terms, and care with signing keys (prefer customer-provided debuggable builds). No regulated data.
Platform dependency
High and two-sided: the whole pipeline rides Google's CLI (could change, though it's stable 1.0), and Google is visibly building agent tooling around Studio — first-party 'memory agent' absorption within 12-24 months is plausible, exactly as Vercel absorbed AIOps (that pattern is in the input signals). This bounds it to a 6-18 month cash window, which matches the founder's 30-90-day goal anyway.
Founder fit
Good but not his proven archetype. Matches: AI-agent pipelines, headless Claude Code orchestration (already in production), complaint mining, low-budget productized service, demonstrated-value selling. Does NOT match the ELDT gov-portal shape: no regulation compelling a filing, no submission portal, no per-transaction lock-in — Android 17 behaves 'like a regulation' only by analogy, and the buyer can always fix the leak themselves and leave. He also has no visible Android publisher network or Android-specific reputation, so credibility must be built via the public PRs. Score reflects strong mechanics fit, weaker moat/shape fit.
Breakout potential
Moderate. The same pipeline extends to ANR, startup-time, battery, and 16KB-page-size compliance — a general 'Android platform-compliance agent.' Agency white-labeling scales distribution without headcount. But Google absorption risk caps the ceiling; the realistic breakout is a $10-30k/mo productized service, not a venture outcome.
Final recommendation
CONDITIONAL GO as a 90-day cash wedge, not a company. Gate 1 (week 1, ~zero cost): complaint-mine Reddit/GitHub/Play reviews for real Android 17 kill pain — no visible pain, hard kill. Gate 2 (week 4): 5 public OSS audits must generate inbound interest or 3 paid audits — otherwise shelve and keep the pipeline as a portfolio asset. Sell one-off audits first; earn the subscription only if regression demand shows up. Do not build a dashboard, SaaS, or anything beyond the pipeline and a Stripe link until Gate 2 passes.
Next action
Spend one day mining r/androiddev, GitHub issues, X, and Play Store reviews for 'Android 17 app killed / closes silently / memory limit' complaints and save every URL — this is the demand-evidence gate that currently sits at hypothesis, and it costs nothing.