Skip to main content

Feature overview

老猫4/24/26About 2 min

This page summarizes what Auto.js Pro is good for. Capabilities differ between v8 and v9 (engine and APIs); the sections below are grouped by what you can build or automate.

Automation

  • Accessibility-based UI automation (recommended)
    • Find and act on controls (tap, long-press, swipe, type, …) via selectors.
    • Generally more stable across resolutions and devices.
    • Docs: v8 automator
  • Coordinate and gesture automation
    • Fits games, canvas-like UIs, or views the accessibility tree cannot see well.
    • Clicks, swipes, multi-touch gestures, RootAutomator, etc.
    • Docs: coordinates-based automation
  • Keys and system navigation
    • Back, home, recents, notification shade, etc. (accessibility or root).
    • Docs: keys

Native UI

  • Rhino UI module (v8)
    • Declare layouts in XML: "ui"; plus $ui.layout(...).
    • Update widgets on the UI thread: $ui.post() / $ui.run().
    • Docs: v8 UI
  • Custom widgets
    • Register reusable components with $ui.registerWidget() (properties, events, methods).
    • Docs: customWidget
  • WebView / web-driven UI
    • Embed WebView, load local or remote pages, and bridge to scripts.
    • Docs: webview

Threads and concurrency

  • threads module
    • Run heavy work off the main / UI thread.
    • Coordination patterns depend on version and APIs.
    • Docs: threads

Scheduling and background work

  • Timed tasks (WorkManager)
    • Daily / weekly / one-shot / intent-triggered jobs.
    • Useful for schedules and “keep running” style scenarios (mind battery impact).
    • Docs: timedTasks
  • Power management & battery optimization
    • Detect / request exemption from aggressive battery savers (use responsibly).
    • Docs: powerManager
  • Internal toggles
    • e.g. “volume up stops script”, foreground-service notification, …
    • Docs: settings

Networking and realtime

  • HTTP / WebSocket
    • OkHttp-based HTTP client patterns (requests, responses, …).
    • WebSocket for bidirectional, long-lived channels.
    • Docs: http, webSocket

Images and vision

  • images module
    • Screenshots, read/write images, crop / scale / rotate / filters.
    • Color find, template find, feature matching (see version-specific docs).
    • Docs: images
  • OCR
    • Pluggable engines (e.g. PaddleOCR, MLKit OCR, …).
    • Docs: ocr

Plugins

  • Plugin store
    • Install and manage official and third-party plugins (OCR, 7-Zip, FFmpeg, …).
  • Plugin SDK (advanced)

Files and storage

  • files module
    • Common read/write, copy/move, paths, text/bytes, file handles, …
    • Docs: files
  • storages (local KV)
    • Simple persistent key–value storage shared across scripts (not for secrets).
    • Docs: storages

Packaging and engineering

  • Project packaging
    • Package projects or scripts into standalone APKs (details depend on version and settings).
  • Resources & Android assets (UI)
    • Use res/ assets, styles, etc. in UI (see UI API docs).
    • Docs: ui/api
  • Encryption & protection
    • Packaging and toolchain options for stronger script protection (varies by engine).

Debugging and developer experience

v8 vs v9

  • v8: Rhino-first API and docs—great for quick scripts and classic UI flows.
  • v9: Adds the Node.js 16.x runtime and a newer API surface (see v9 docs). Some patterns can still show memory leaks; treat v9 as optional unless you need npm / throughput—prefer v8 for everyday automation unless you know you need v9.

For the Node.js / v9 reference tree, open v9 reading guide from the sidebar.

Copyright © 2026 老猫