Melaya · Build high-trust AI agents for any workflow, and put them on your phone. The visual agent builder, with Device Control as its flagship: Claude Code, GPT, or Gemini operating your real phone apps, one verified action at a time, with your approval on every action.

Melaya Mobile · App Testing

Your app, on a real phone.Not an emulator guessing.

Agents walk your real user journeys on real devices: install, onboard, tap through, screenshot, report. Devs verify push notifications, deep links, and cross-device behavior on every build. PMs run A/B variants on physical hardware before release and get side-by-side recordings. It is your actual app on an actual phone, not an emulator guessing.

See the pipelines ↓
01
// What breaks today

The status quo costs more than the agent does.

Three pains every sales and BD team hits weekly. Each one is what your reps actually complain about, not what a feature page would call them.

  1. 01

    Manual QA on real devices is slow and expensive.

  2. 02

    Bugs in push notifications, deep links, and onboarding flows ship because nobody had time to walk every journey on every phone.

02
// Pipelines you can build

Compose. Approve. Replay.

Every pipeline below is a shape you wire on the canvas using the crew and tools further down. Not a feature we ship for you, a pattern you configure.

P01

Real user journeys, walked

Install, onboard, tap through, screenshot, report. Agents walk your real user journeys on physical hardware and file replayable evidence.

P02

Push, deep link, cross-device checks

Verify push notifications, deep links, and cross-device behavior on every build, before your users do.

P03

A/B variants on hardware

Run A/B variants on physical devices before release and get side-by-side recordings for the decision.

03
// The crew

Device QA crew

Real personas from the tech_team crew. Each ships with a tuned system prompt and a default tool allowlist. Swap models per persona on the canvas.

Tech Lead

TechLead

Plans the journey coverage and reads the evidence per build.

Frontend Engineer

FrontendEngineer

Walks the app UI screen by screen and captures each step.

DevOps Engineer

DevOpsEngineer

Wires runs into your release cadence and files the reports.

UI/UX Designer

UIUXDesigner

Compares variants side by side and flags what regressed.

04
// Scoped tools

Only the actions you grant.

Every tool below is a real shared tool from the Melaya bundle. Allowlist per agent; HITL-gate the writes; revoke any of them in one click.

shared/tools/phone/

Drives your app on a real device: taps, swipes, screenshots, step logs.

phone_open_appphone_get_screen_treephone_screenshotphone_tapphone_swipephone_batch
shared/tools/project_mgmt/

Files what it finds where your team already works.

jira_create_issuelinear_create_issue
shared/tools/knowledge/

Turns run evidence into a searchable record per build.

build_knowledge_from_textbuild_knowledge_from_file
shared/tools/core/

Reads configs and logs alongside the on-device run.

file_readgrep_search
05
// Three knowledge layers

The crew reads what you give it.

Every pipeline ships with three layers of knowledge access. Mix and match per agent on the canvas. No shared vector space with another tenant, no surprise reads, no opaque retrieval.

L1

Static context

includeContext

Per-pipeline documents appended to specific agents' input on every run. The ICP brief, playbook, pricing sheet, or won-deal email corpus. Whatever needs to be there before the agent thinks. You pick which personas get which docs.

L2

RAG retrieval tool

rag_retrieve

A scoped tool granted per-agent. When the agent decides it needs more depth, it queries the workflow's vector store on demand. Same knowledge base as Static context, accessed only when the model asks for it.

L3

Cross-run memory

pipeline_memory

Pipeline-level state that carries from one run to the next. Yesterday's research is in scope for today's follow-up. The crew remembers what it already prospected, what got approved, what was sent. The audit log is the second-order knowledge base.

07
// FAQ

Questions we get every week.

Is this an emulator?

No. It is your actual app on an actual phone. Agents walk the real UI and file replayable evidence: screenshots, step logs, repro scripts.

Do I need to instrument my app?

No instrumentation and no test-framework integration. The agent drives the app through the screen, the way a user does.

Build app founders, mobile devs & pms pipelines on Melaya.

Sandbox tier is free with no card. Join the waitlist and we will email you the moment a slot opens.

← Back to every use case
Join the community