Skip to content
Appvecta

Appvecta Device Hub

One toolbar instead of five windows.

Run, device control, logs and app lifecycle are designed to live in the editor, so the loop from change to running app has no tab switching in it.

Planned for the private alpha

The toolbar

[ ▶ Run ]  [ 🧪 QA ]  [ 🧠 Brain ]  [ Device: Android_API_36 ▾ ]

Android run

Detect the Gradle wrapper and SDK → detect app modules, variants, application IDs and launcher activities by parsing, not by running Gradle → ask once when ambiguous → save the target → build the variant → select a device or start an AVD → install the APK → launch → attach filtered logcat → show status and errors with file and line.

Flutter run

Detect the Flutter SDK → discover Android devices → detect flavors and entry points → build and install → capture structured output and device logs. Hot reload is a later enhancement, deliberately not a QA dependency.

Run state machine

Cancel at any state kills the child process tree.

Idle → Preparing → Building → Installing → Launching → Running
                                        → Stopped | Failed | Cancelled

Device Hub

  • List devices and AVDs with serial, model, API level, state and connection type
  • Select the active target; start and stop an AVD
  • Install and uninstall the debug app
  • Launch, force-stop and clear app data (with confirmation)
  • Screenshot and screen recording
  • Filtered logs and the current foreground activity
  • Permissions and device state
  • USB and ADB-wireless

Errors that say what to do

Missing SDK, wrong JDK, Gradle sync failure, no device, install failure from a signature mismatch, launch failure from a missing activity — each classified, each with an actionable message rather than a raw stack trace.