What changed
Two documented shifts landed together: Google now lets non-developers generate installable native Android apps from a prompt in AI Studio (source: Google AI Studio announcement), and Android 17 enforces per-app memory limits, killing violators with no stack trace (source: Android 17 memory-efficiency post). A third documented shift — agentic tooling inside Android Studio with open model choice (source: Android Studio I/O Edition post) — makes automated diagnosis buildable by one person.
Why now
FACT: Android 17 enforcement guidance is published and the prompt-to-app pipeline is live as of I/O '26 (both cited). HYPOTHESIS: the wave of unexplained-kill complaints arrives this quarter as Android 17 devices roll out; being first into the search results ('android 17 app killed no crash log') is a time-limited land grab.
Converging signals
(1) Prompt-to-native-app in AI Studio drops publishing cost to ~zero, growing the population of memory-naive publishers weekly. (2) Android 17 per-app memory limits kill over-budget apps silently — no stack trace means the builder's normal debugging loop (paste the error into the AI) fails completely. (3) Android Studio's agentic/CLI-driveable profiling tools mean a solo founder can script the exact diagnosis the victims cannot perform. All three from the cited Google developer blog posts.
Customer pain
HYPOTHESIS (strongly implied by the causal chain, not yet evidenced by complaint volume): app dies in the field, user reviews say 'app keeps closing', Play console shows no crash, the AI that built the app can't explain it because there's no error text to paste. The builder has no mental model of memory and no profiler skills. Pain is acute precisely because it is undiagnosable with the victim's toolset.
Who pays
Solo founders and SMBs who shipped prompt-built apps that earn money or serve their business (the only segment that will pay — hobbyists won't); secondarily small agencies pumping out client apps via AI tooling who need a pre-release gate to avoid support burden. No enterprise sales required.
Solved today
FACT: Android Studio Memory Profiler and LeakCanary exist and are free. HYPOTHESIS: the target customer cannot use either — they don't have Android Studio workflows at all (they built in a browser), which is exactly why a run-it-for-me service has room despite free tools.
Why current solutions are bad
Free tools assume a developer: install the IDE, reproduce the leak, read a heap dump, interpret retained-size graphs. The vibe-coder has none of that. Play Console vitals won't show a stack trace for these kills (per the Android 17 post's premise). There is no 'upload APK, get plain-English verdict + AI-ready fix prompt' product aimed at this population.
Proposed product
A web service: upload your APK (or connect your repo/AI Studio export). An automated harness installs it on real/emulated Android 17 devices, drives it (monkey/agent-scripted flows), captures heap profiles via the scriptable Studio/CLI profiling tools, and returns: (a) will Android 17 kill this app and on which RAM tiers, (b) the top leak/allocation causes in plain English, (c) a copy-paste remediation prompt engineered for the customer's own coding agent to apply the fix. Upsell: a GitHub Action / CI gate that fails builds over budget, and a done-for-you fix service.
MVP version
2-3 weeks: a scripted pipeline (perfetto/heap dumps + adb + emulator matrix at constrained RAM) wrapped in a single landing page with Stripe: 'Is Android 17 killing your app? Upload your APK — memory verdict in 24h, $79.' Manual/semi-automated delivery at first; the report template and the 'fix prompt for your AI' are the product. No accounts, no dashboard.
30-day build
Build the harness against 3-5 deliberately leaky sample apps (generate them with the same AI Studio pipeline — that's also marketing content). Publish 2 SEO/dev.to/Reddit posts targeting the exact symptom phrases ('android app closes by itself android 17', 'no crash log'). Run 10 free audits for visibility in r/androiddev, vibe-coding Discords, and X builder communities in exchange for testimonials.
60-day build
Convert to paid ($79-149/scan). Ship the GitHub Action + CLI check ($29/mo per app) for agencies and repeat shippers. Start a public 'Android 17 kill list' teardown series auditing popular vibe-coded apps (with permission) — demonstrated-value distribution, which matches how this founder sells.
90-day revenue plan
Target: 30-60 paid scans plus 10-20 CI subscriptions ≈ $3-6k/mo run rate. HYPOTHESIS — depends entirely on kill-complaint volume materializing this quarter; if Android 17 rollout is slow, revenue slips a quarter.
Distribution path
Symptom-driven SEO (victims will search the exact failure phrase and find nothing today), Reddit/Discord/X communities where vibe-coders congregate, free-audit-for-testimonial seeding, and public teardowns. No enterprise sales, no ads. Weakness: the audience is diffuse and there is no single channel or forced registry funneling buyers to you (unlike the ELDT play).
Pricing hypothesis
$79-149 per one-off audit; $29-49/mo per app for the CI gate; $500+ done-for-you remediation. Per-transaction pricing mirrors the founder's proven per-upload model.
Technical difficulty
Moderate and squarely in the founder's lane: adb/emulator orchestration, heap-dump parsing, and AI-assisted report generation are automation plumbing, not novel CS. Hard part is making automated app-driving generic across arbitrary apps; mitigated by starting with a semi-manual concierge tier.
Legal / regulatory risk
Low. Customers submit their own APKs; no scraping, no regulated data. Standard ToS disclaiming fitness guarantees. Public teardowns need permission to avoid defamation/goodwill issues.
Platform dependency
HIGH — this is the biggest structural risk. Google could ship 'memory compliance check' natively in AI Studio/Play Console and erase the gap; the product's existence depends on Google's tooling gap persisting. Treat as a 12-24 month cash window, not a durable moat.
Founder fit
Good but not the proven-edge shape: it is a compliance-monitor/audit tool with per-transaction pricing, AI-workflow-heavy, solo-buildable, demonstrated-value distribution — all matches. But unlike ELDT, no regulation FORCES anyone to buy; Android 17 kills apps but doesn't mandate filing, so there is no captive must-comply funnel. Fit is real, not VERY HIGH.
Breakout potential
Moderate: expands into a general 'pre-flight compliance lab for AI-generated apps' (memory, battery, policy, permissions, Play-listing rejection prediction) as each new Android enforcement wave creates the same diagnose-blind population. Each wave is a new SKU on the same harness.
Final recommendation
PURSUE AS A CHEAP PROBE, not a commitment: spend ≤2 weeks building the concierge audit + landing page and seed 10 free audits. The idea passes the fast-MVP and solo-feasibility gates and rides a real, cited enforcement change, but demand timing and willingness-to-pay are unproven hypotheses. Let 30 days of symptom-search traffic and conversion data decide before building the CI product.
Next action
Generate 3 test apps via the AI Studio prompt-to-app flow, run them on an Android 17 image with constrained RAM to reproduce and document a silent kill end-to-end, and publish that writeup ('Why Android 17 killed my AI-built app with no crash log — and how to check yours') with a $79 audit CTA.