[{"data":1,"prerenderedAt":19},["ShallowReactive",2],{"blog-post-en-plain-language-ai-flows-phoma":3},{"slug":4,"lang":5,"title":6,"summary":7,"date":8,"tags":9,"tag_slugs":14,"thumbnail_url":15,"translations":16,"body":17,"asset_base":18},"plain-language-ai-flows-phoma","en","Turn Plain‑Language Descriptions into Automated Flows with Phoma’s AI Integration","Learn how to describe an automation task in plain English and let Phoma’s AI agent generate a visual flow for you. Verify the generated steps and run them on any number of Android phones instantly.","2026-11-05",[10,11,12,13],"android-automation","phoma-ai","visual-flows","android-testing",[10,11,12,13],"https://blog-api.phomaapp.com/api/blog/posts/plain-language-ai-flows-phoma/thumbnail.svg?lang=en",[5],"## Introduction\nAutomating repetitive actions on Android devices used to require writing scripts or learning complex tools. With Phoma, you can now describe a task in everyday language and let an AI agent build a visual flow for you. This approach lowers the barrier for QA testers, developers, and operations staff who need quick, reliable automation without coding.\n\nWhy does this matter? Many professionals think they need programming skills to automate UI interactions, but the reality is that most tasks can be expressed in plain sentences. By leveraging Phoma’s built‑in AI integration, you can capture intent quickly, let the AI translate it into a step‑by‑step visual diagram, and then run the flow on a single phone or across a fleet. The result is faster onboarding, fewer errors, and more time for higher‑value work.\n\n## Why Use AI to Generate Flows?\n- **Speed:** Writing a prompt takes seconds, whereas building a flow manually can take minutes.\n- **Accessibility:** Team members without coding experience can contribute to automation.\n- **Consistency:** The AI follows best practices for selectors and timing, reducing flaky tests.\n- **Iterative refinement:** If the generated flow is off, you can edit it directly in Phoma, preserving the intent while correcting the details.\n\n## Connecting Your Phone to Phoma\nBefore the AI can act on a device, Phoma needs a connection. Follow these steps for a reliable setup.\n\n### USB Debugging\n1. Enable Developer Options on the Android device (`Settings > About Phone > Build Number` tap 7 times).\n2. In Developer Options, toggle **USB Debugging** on.\n3. Connect the phone to your Windows PC with a USB cable.\n4. On the PC, launch Phoma and select **Devices > Add Device**. Phoma will detect the phone and prompt you to confirm the debugging certificate.\n\n### Wireless (ADB over Network)\n1. Ensure phone and PC are on the same Wi‑Fi network.\n2. Enable **USB Debugging** first (same as above).\n3. Run `adb tcpip 5555` in a command prompt on the PC.\n4. Disconnect the USB cable, then run `adb connect \u003Cphone_IP>:5555`.\n5. In Phoma, the device will appear as a wireless entry. Click **Pair** and confirm the prompt on the phone.\n\n**Tip:** If the phone refuses to connect, restart both devices, verify firewall rules, and double‑check that the driver for your manufacturer is installed.\n\n## Preparing the Plain‑Language Prompt\nThe quality of the generated flow depends on how clearly you describe the task. Use the following structure:\n\n1. **Goal verb** – what you want to happen (e.g., \"log in\", \"enter data\", \"take a screenshot\").\n2. **Target app** – the package name or recognizable app name.\n3. **Context details** – UI elements, data values, and any conditions.\n4. **Optional constraints** – wait times, loops, error handling.\n\n### Example Prompt\n```\nLog in to the MyBank app using the email \"user@example.com\" and password \"SecurePass123\". Tap the \"Sign In\" button after entering credentials. If login fails, wait 2 seconds and retry once.\n```\n\n**Why this works:** The sentence includes the action (log in), the app (MyBank), the data (email/password), and a conditional retry. The AI can map each clause to a UI Automator step.\n\n## Using Phoma’s AI Agent\nOnce you have a prompt, Phoma’s AI runs in the background and returns a visual flow diagram. Here’s how to invoke it:\n\n1. Click **Create New Flow** in the Phoma dashboard.\n2. Choose **AI Assisted** from the template list.\n3. Paste your prompt into the AI prompt box and click **Generate**.\n4. Phoma displays a preview of the flow with each step as a node (tap, type, wait, etc.).\n\n### Reviewing the Generated Flow\n- **Inspect selectors:** Hover over a step to see the element’s accessibility ID or resource‑id. If the selector is fragile (e.g., based on text that changes), replace it with a more stable one.\n- **Adjust timing:** Add a **Wait** node where needed, or increase the default wait duration.\n- **Add conditions:** Use **If** nodes for success/failure branches.\n\n**Real‑world example:** After generating a flow to capture public product listings from an e‑commerce app, the AI selected the element by its text label \"Product Name\". Because the app frequently updates the label to \"Item Name\", you edit the selector to target the resource‑id `com.shop.app:id/product_title` instead.\n\n## Editing the Flow Manually\nEven the best AI can miss edge cases. Phoma’s editor lets you fine‑tune the flow without rewriting code:\n\n- **Add steps:** Drag a **Tap**, **Type**, or **Swipe** node from the palette and drop it where needed.\n- **Remove steps:** Select a node and press **Delete**.\n- **Connect nodes:** Click the start node, drag a line to the destination node.\n- **Set properties:** Double‑click a node to edit its parameters (e.g., text to type, key codes, element wait).\n\n**Tip:** Use the **Preview** mode to simulate the flow on a single device before deploying it across multiple phones.\n\n## Running the Flow on One or Many Phones\nOnce satisfied, you can execute the flow:\n\n1. **Single device:** In the flow editor, click **Run** and select the connected phone from the device list.\n2. **Multiple devices:** Choose **Run on All Devices** (or use the **Batch Run** option). Phoma will start the same sequence on each phone sequentially, logging results separately.\n\n### Scheduling Runs\n- Open **Automations > Scheduled Runs**.\n- Click **Add Schedule**, pick the flow, and set a recurrence (daily, weekly, custom cron).\n- Enable **Run while app is open** to keep the phone’s screen on during execution.\n\n**Why schedule?** It ensures regression checks happen automatically each build, reducing manual oversight.\n\n## Sharing Phones and Flows Inside a Team\nPhoma’s Team plan introduces shared device pools and collaborative flows:\n\n- **Shared devices:** Admins can grant access to specific phones so any team member can run flows without needing physical access.\n- **Team flows:** Create a flow in **Team Library**, add comments, and let others edit or version‑control it.\n- **Access control:** Set read/write permissions per user or group.\n\n**Use case:** A QA lead creates a smoke‑test flow, shares the test phone pool with developers, and schedules nightly runs. Developers can view the results directly in the dashboard, speeding up feedback loops.\n\n## Troubleshooting Common AI Generation Issues\n| Symptom | Likely Cause | Fix |\n|---------|--------------|-----|\n| Flow missing a step | Prompt omitted a clause | Expand prompt with \"also\" or \"then\" connectors. |\n| Selector unstable | AI used text or position | Replace with a more specific resource‑id or accessibility‑id. |\n| AI repeats actions | Prompt contained ambiguous language | Clarify with time limits or conditions (\"once\", \"if successful\"). |\n| No devices detected | USB debugging not enabled or driver missing | Re‑enable debugging, reinstall manufacturer driver, restart PC. |\n\n## Best Practices for Prompting the AI\n1. **Be explicit about order:** Use \"first… then… after that…\".\n2. **Specify data values:** Quote strings, numbers, and special characters.\n3. **Add conditional language:** Include \"if\", \"when\", \"unless\" for branching logic.\n4. **Limit scope:** Break complex tasks into smaller prompts to improve clarity.\n5. **Review selectors:** Always check the AI‑chosen element and replace if it’s likely to change.\n\n## Conclusion\nLeveraging Phoma’s AI integration transforms vague ideas into concrete, executable automation flows in minutes, not hours. By describing tasks in plain language, you tap into a powerful assistant that understands intent, builds a visual diagram, and lets you fine‑tune it instantly. Whether you’re running a quick smoke test on a single device or orchestrating regression suites across a fleet, the AI‑assisted workflow keeps the process intuitive and reproducible.\n\nStart today: connect a phone, craft a clear prompt, let the AI generate a flow, and watch your automation become a shared, repeatable asset for the whole team.\n","https://blog-api.phomaapp.com/api/blog/posts/plain-language-ai-flows-phoma/assets",1793868178150]