Skip to content
Nichr
AI agentsNew techTop 22% of today's analysed ideas

Packaged voice control for any Android app

Build a packaged no-ADB voice-control layer on top of Midscene for Android: a consumer app that lets people operate any app (WeChat, banking, food delivery) by voice, aimed at accessibility users, elderly users, or hands-free/driving use cases, plus a developer-facing wrapper that lets other builders add voice-driven UI automation to their own apps without wrestling with Midscene's raw framework setup.

via Reddit
Original post

What to build

A packaged, no-ADB voice-control app for Android built on the Midscene automation framework, letting elderly, accessibility, or hands-free/driving users operate any third-party app (banking, food delivery, messaging) by voice — plus a lightweight SDK wrapper so other developers can bolt voice-driven UI automation onto their own apps without configuring Midscene from scratch.

A developer already proved voice control can drive arbitrary Android apps like WeChat without root or ADB using Midscene; the gap is a polished consumer app and a dev-friendly SDK that package this capability for non-technical and accessibility-focused users.

Demand

Accessibility users, elderly people, and hands-free/driving use cases are the natural first buyers, and the demo already struck a chord with solo builders on Reddit who want to replicate or extend it — but real demand is currently only validated at hobbyist/demo scale, not commercial.

  • r/SideProject (Reddit)Community

    Post titled 'I built a voice-controlled Android app—even WeChat works', describing a voice app powered by Midscene; used as the original demand/interest signal, exact upvote/comment counts not provided in available data.

  • Original signal post/demoNews

    Developer demonstrates a voice-controlled Android app that successfully operates WeChat, built on top of the Midscene automation framework, without using ADB.

Stack

  • Midscene (UI automation framework)
  • Android AccessibilityService API
  • OpenAI Realtime API or Whisper for speech-to-text
  • Android Speech-to-Text / TextToSpeech APIs
  • React Native or Kotlin for the app shell
  • Firebase for user accounts and command logging

Solo + AI difficulty

The hard part is not the voice layer (speech-to-text and TTS are commodity APIs) but making accessibility-service-based screen automation reliably hit the right UI elements across frequently-updated third-party apps, plus navigating Google Play's accessibility-API-misuse review process; a rough, narrow MVP (voice control for a handful of common apps) is feasible in 2-4 weeks solo with AI-assisted coding, but a robust, general-purpose version is a multi-month effort.

Entry threshold
Core automation engine is already open-source (Midscene), so the work is UX polish, voice command parsing, and packaging into an installable app with no developer mode or cable required; a solo builder can ship a usable version in a few weeks, though reliability across arbitrary third-party app UIs will need ongoing tuning.
Window
3-6 months

Where to find first users

  • r/SideProject and r/accessibility on Reddit
  • Product Hunt launch targeting accessibility-tech audience
  • Outreach to elderly-care and assistive-tech communities/forums
  • Indie hacker and no-code builder communities (e.g. Indie Hackers, Midscene's own Discord/GitHub community)

Competitors

Counter-signals & risks

  • Reliability and generalization across diverse, frequently-updated third-party app UIs (e.g., WeChat redesigns) may be fragile, since UI-automation-based voice control depends on screen-scraping or accessibility APIs that can break with app updates.

  • Platform risk: Android/app vendors (e.g., Tencent/WeChat) may restrict or flag automated accessibility-service-driven control as abuse, especially for banking apps, limiting commercial viability.

  • No-ADB accessibility-based automation may face strict app store policy scrutiny (Google Play accessibility API misuse policies), constraining distribution of a packaged consumer app.

Original title: I built a voice-controlled Android app—even WeChat works

Related signals

  • AI agents#6

    Build vertical agents on open-source durable harnesses

    Use Omnara's open-source durable-agent harness as backend infrastructure to ship a narrow, vertical AI agent product (e.g. a DevOps remediation agent, QA test-runner agent, or support-ticket agent) without building the agent loop, sandboxing, or state persistence yourself. The pitch to customers is a focused agent for one workflow, not generic agent infrastructure.

    Demand
    2/10
    measured
    Buildability
    6/10
    est.
    Competition
    6/10
    est.
    via Hacker News
    33 competitors
  • AI agents#10

    Sub-600ms voice API enables sellable AI phone agents

    Build niche voice-agent products on top of Eleven Realtime's sub-600ms latency speech-to-speech API: vertical voice assistants for clinics, restaurants, car dealers or real-estate agencies that handle phone bookings and FAQs, or a dev-facing wrapper/SDK that simplifies turning Eleven Realtime into a drop-in call-center replacement for small businesses. The low latency finally makes natural-feeling AI phone agents viable for solo builders to wrap and resell.

    Demand
    4/10
    est.
    Buildability
    7/10
    est.
    Competition
    5/10
    est.
    via The Decoder
    44 competitors
  • AI agents#12

    Verified daily job match with auto-filled application

    Build or niche-down a job-application-automation tool for a specific vertical (e.g. new grads, H1B/visa-sponsored roles, remote-only, or a single country's job market) that delivers one verified-open, well-matched job per day with auto-tailored CVs and pre-filled applications, competing on trust (no fabricated experience) rather than volume of leads.

    Demand
    5/10
    est.
    Buildability
    7/10
    est.
    Competition
    6/10
    est.
    via Reddit
    33 competitors
Packaged voice control for any Android app — Nichr