Skip to content
Midscene logo

Midscene

Automates web, mobile, and desktop app testing by interpreting screenshots and executing actions in natural language.

Developer toolsSDKFor developers
midscenejs.com ↗XLaunched on Product Hunt · 2026-10-02
At a glanceswept 2026-10-09

≈ 166visits/mo

Emerging · estimate, read 2026-10-02

  • Midscene166
  • #1 Microsoft135M
  • Developer tools median25
For
QA engineers and developers automating UI tests across web, mobile, and desktop applications
Price
Price not read
Activity
Actively maintainedrelease 5 days ago · site updated 6 days ago
Company
Domain since 2024domain registered
Runs as
SDK
AlternativesSet it up for my teamIs Midscene yours? Claim the card →
What people do with it
  • test web and mobile apps using natural language commands
  • automate UI interactions on unlabeled elements and canvas
  • verify application behavior across multiple platforms with one API
The companyeach fact with its source · read 2026-10-02
  • Domain since2024domain registered
Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Developer tools tools →

Questions this page answers
  • What is Midscene?

    Automates web, mobile, and desktop app testing by interpreting screenshots and executing actions in natural language. It is listed in the Atlas under Developer tools.

  • Who is Midscene for?

    QA engineers and developers automating UI tests across web, mobile, and desktop applications

  • Do people use Midscene?

    Emerging: ≈ 166 visits/mo · estimate, 2026-10.

  • Is Midscene still maintained?

    Actively maintained: release 5 days ago · site updated 6 days ago.

  • What are alternatives to Midscene?

    In Developer tools, by use: Unleash the Power of AI for Your Business, JetBrains, TestMu AI (Formerly LambdaTest), Browserbase, Replit, IFTTT.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.