What changed
Three platform facts landed together: (1) Android 17 now enforces RAM-scaled per-app memory limits and kills violators with no stack trace (source: Android Developers blog, Jun 2026); (2) Google AI Studio lets non-developers ship installable native Android apps from a prompt with zero tooling (source: Android Developers blog, May 2026); (3) the Android CLI hit stable 1.0 and exposes profilers/analysis to coding agents headlessly (sources: May/Jun 2026 Android blogs). FACT: all three capabilities are live per the cited posts. HYPOTHESIS: a meaningful population of prompt-built apps is already being OOM-killed.
Why now
The kill switch (Android 17 enforcement) turned on in the same quarter the skill floor collapsed (AI Studio prompt-to-app, launched at I/O '26). The victims are minted continuously and cannot self-diagnose: no stack trace means no crash report, and prompt-builders have no profiler skills. The diagnostic tooling (stable agent-drivable CLI) became automatable at exactly the same moment. This window closes if/when Google bakes memory linting into AI Studio itself.
Converging signals
FACT (cited): Android 17 silent memory kills; AI Studio native-app generation for non-developers; Android CLI 1.0 stable with agent-driven profilers; agents can drive Android Studio profilers/device streaming programmatically. INFERENCE: the intersection — un-debuggable apps failing invisibly at scale — is not directly evidenced in any source; no signal shows actual complaint volume from affected builders yet.
Customer pain
HYPOTHESIS with strong mechanism: an app that silently dies in the background loses alarms, syncs, and sessions; users leave 1-star 'app just stops working' reviews and churn. The owner sees symptoms but no crash log, Play Console shows nothing actionable for a silent LMK-style kill, and the builder has no dev environment to investigate. Pain is existential for the app but currently UNPROVEN in volume — no complaint data (Reddit/Play reviews/forums) is in the input. This is the single biggest gap to verify before building.
Who pays
Tier 1: small studios and agencies shipping many AI-generated or Compose apps who want a pre-release memory-compliance gate (recurring, CI-integrated). Tier 2: solo prompt-builders with a live app that started dying on Android 17 devices (one-off audits). HYPOTHESIS: Tier 2 is large but low-willingness-to-pay (many are hobbyists who paid $0 to build); Tier 1 is smaller but has budget and recurring need. Price and target Tier 1, let Tier 2 be top-of-funnel.
Solved today
Real developers use Android Studio Memory Profiler, LeakCanary, Perfetto traces, and Play Vitals — all manual, skill-intensive, and requiring a dev environment. Prompt-builders' realistic current option is pasting code back into an AI chat and hoping, or nothing. No known productized 'upload APK → memory verdict' service exists (INFERENCE from absence of evidence, not verified).
Why current solutions are bad
Existing tools assume you can run a profiler, interpret a heap dump, and reproduce the kill on a constrained device. The new builder population can do none of these. Even skilled devs face a new failure mode — RAM-scaled limits mean an app that survives on a 12GB phone dies on a 4GB one, so single-device testing gives false confidence.
Proposed product
A web service: upload APK or connect the AI Studio/GitHub project. An agent-driven pipeline (Android CLI + emulators configured at low-RAM tiers) installs the app, drives it through monkey/scripted flows, records heap and RSS against Android 17's published limits, detects leak patterns (retained activities, bitmap hoarding, unbounded caches, background-service growth), and outputs: (a) pass/fail per RAM tier, (b) plain-English cause localization, (c) for source-connected projects, a suggested fix PR generated by Claude Code. CI webhook mode for agencies.
MVP version
2-3 weeks solo: headless emulator matrix (4GB/6GB/8GB profiles) + Android CLI profiling driven by scripted Claude Code sessions + a report generator. No dashboard — intake via a simple upload form or even email; deliver a PDF/markdown report. Charge from audit #1. Founder already runs exactly this shape of pipeline (Python orchestration + headless claude -p) in production.
30-day build
Week 1: validate demand before building — mine r/androiddev, AI Studio Discord/forums, and Play reviews of known AI-built apps for 'app killed/stops in background on Android 17' complaints; if fewer than ~30 distinct complainants found, kill or shelve. Weeks 2-3: build the emulator+CLI audit harness on 5 sacrificial test apps. Week 4: offer 10 free audits in the communities where complaints were found in exchange for testimonials and permission to publish before/after.
60-day build
Convert free audits to paid ($49-$99/audit). Publish 2-3 teardown posts ('why Android 17 killed this AI-built app') as demonstrated-value marketing. Ship the CI/webhook gate and pitch the 3-5 agencies or template shops identified during complaint mining at $99-$299/mo. Add automated fix-PR output for source-connected projects (upsell).
90-day revenue plan
Target: $1.5k-$4k MRR-equivalent — e.g. 20-40 one-off audits/mo plus 5-10 CI subscriptions. HYPOTHESIS: achievable only if the complaint volume verified in week 1 is real and growing; if Tier 2 won't pay, the floor is the agency CI gate at ~$1k MRR.
Distribution path
Complaint-mining and demonstrated value, no sales calls: answer specific 'my app gets killed' threads with a free diagnosis, publish teardowns, SEO on 'Android 17 app killed no crash log' (a query with near-zero current competition), and a free lightweight 'will Android 17 kill your app?' APK scanner as lead magnet. All channels are founder-fit (build-in-public, evidence-led).
Pricing hypothesis
$0 quick static scan (lead gen) → $49-$99 full dynamic audit per app version → $99-$299/mo CI compliance gate for studios/agencies → $199+ audit+fix-PR bundle. Per-transaction pricing mirrors the founder's proven ELDT per-upload model.
Technical difficulty
Moderate. Emulator orchestration, driving real app flows automatically (login walls, permissions), and distinguishing 'leak' from 'legitimately heavy' are the hard parts; dynamic analysis of arbitrary APKs will have a meaningful failure rate. Mitigation: start with source-available AI Studio projects (easier) before arbitrary APKs. All within one strong operator's reach using agent tooling — no novel research required.
Legal / regulatory risk
Low. Analyzing a customer's own app at their request is clean. Avoid auditing third-party apps without owner consent. Standard ToS + no-guarantee language; not a regulated domain.
Platform dependency
HIGH and the honest weak point: Google owns every layer (Android 17 policy, AI Studio, the CLI). Two existential risks: Google adds memory linting/auto-fix to AI Studio's generation loop (likely eventually — INFERENCE), or relaxes enforcement. The bet is a 6-18 month arbitrage window, which matches the founder's 30-90-day cash goal; this is a fast-cash play, not a durable company.
Founder fit
Strong but not the VERY HIGH gov-portal shape. Structural rhyme with the ELDT win: an authority (Google, not a regulator) imposes a compliance requirement on a population that can't self-serve, and the founder sells the compliance layer per transaction. Differences that lower it a notch: no legally-compelled filing (churn pain, not legal mandate), and the 'portal' is a test harness he must build rather than a submission endpoint. His Python-orchestration-plus-headless-Claude production experience (this very system) is directly the required architecture. No enterprise sales, no capital, marketplace-adjacent micro-SaaS — all inside his preference set.
Breakout potential
Moderate: wins here generalize to a broader 'QA/compliance gate for AI-generated apps' product (security, policy, battery, ANR) as the prompt-built flood grows across platforms — a genuine trend to ride. Capped by platform dependency and by Google's incentive to solve it natively.
Final recommendation
CONDITIONAL GO — B-tier. Do not build first. Spend 3-5 days on complaint mining (r/androiddev, AI Studio community, Play reviews, X) to convert the core hypothesis into evidence. If ≥30 distinct real-world 'silently killed, can't diagnose' complaints surface, build the 2-3 week MVP and sell audits immediately; the mechanism, timing, and founder fit are all genuinely good. If mining comes up thin, shelve and revisit in 60 days when Android 17 device penetration is higher — the enforcement wave may simply not have hit yet.
Next action
Run a 3-day complaint-mining sweep for 'app killed / stops working / no crash log + Android 17' across r/androiddev, r/android, AI Studio forums/Discord, and Play Store reviews of known AI-built apps; log distinct complainants and whether any mention willingness to pay for a diagnosis.