iDeviceFarm Capabilities Deep Dive: L1 Atomic → L2 Workflow → L3 AI

The Problem With One-Layer Thinking

Most people think of phone automation as one thing: “AI tells the phone what to do.” But that oversimplifies what actually needs to happen. Real phone operations require three distinct layers, each solving a different problem:

Layer	What It Does	Who Uses It	Example
L1: Atomic Actions	Single device operations — tap, swipe, input, wait	Every user indirectly	“Tap submit button”
L2: Workflows	Multi-step processes tied to specific scenarios	Ops teams, power users	“Post video with caption + hashtags”
L3: AI Orchestration	Understand natural language, dynamically chain steps	Anyone who can speak naturally	“Post today’s product listing on TikTok”

Layer 1: Atomic Actions — The Foundation

Atomic actions are indivisible unit operations. Each has a clear success condition, timeout behavior, and no side effects beyond its stated purpose. Key capabilities include:

• launch_app(app_id): Open a specific app and confirm it’s in foreground;
• tap(selector): Tap a UI element; optionally verify post-tap screen state changes;
• swipe(direction, distance): Swipe up, down, left, or right with configurable distance;
• input(selector, text): Type text into a field and validate the result;
• wait_ui(text_or_selector, timeout_ms): Poll for an element until it appears or times out;
• album_import(path/url): Add a photo/video to the media picker.

Key principle: every call returns a receipt. Not “I tapped” but “I tapped and the screen navigated as expected.”

Layer 2: Workflows — Templates That Save Hours

A workflow chains multiple atomic actions into a repeatable process, parameterized so the same template handles different data. Think of it like a restaurant recipe: same steps, different ingredients.

Scenario	Workflow ID	Steps (abbreviated)
Short Video Publish	publish_short_video	launch → pick_media → input caption → select hashtag → set cover → submit
E-commerce Listing	list_products	launch → search_category → fill_title → set_price → sync_inventory → confirm
App Login Smoke Test	smoke_login	launch → input_credentials → tap_login → assert_homepage_shown

Workflows run independently of L3 AI—you can invoke them directly via MCP tools or REST API without any natural language understanding. They’re the most reliable path for known, repetitive tasks.

Layer 3: AI Orchestration — Your Words Become Actions

This is where AI phone control truly shines. When you say “post today’s products on TikTok,” the system:

1. Identifies intent: Matches your request to a known pattern (product listing → publish workflow).
2. Extracts parameters: Finds which products, which platform, any special instructions from context or follow-up questions.
3. Generates execution plan: Maps the abstract task to ordered steps, selecting appropriate atomic actions and workflows.
4. Executes + verifies: Each step completes with a check against expected outcome. Failures report exactly where, not silently retry.

L3 is the least deterministic—it depends on model quality, clarity of instruction, and complexity of the task. For anything mission-critical, prefer L2 workflows over relying purely on natural language.

Which Layer Do You Need?

Your situation	Start with	Why
New to AI phone control, want to understand what’s possible	L3 (chat demo)	Low barrier to see results; learn the vocabulary
Have a fixed, repetitive task done daily	L2 (workflow)	Most reliable, fastest, no model dependency
Occasional varied tasks, fast-paced ops	Both L2 + L3	Use L2 for known flows, L3 for ad-hoc requests

Bottom line: atomic actions make it possible, workflows make it reliable, AI makes it accessible. Most successful teams use all three—but start at the layer that matches your current need, not the one you think sounds coolest.