Datasheet | Fact Sheet
Kobiton Mobile Device Cloud
Read More
Abstract
A solo developer shares how Claude helped build a personal app over 48 builds, completed entirely during nights and weekends. Claude Code wrote the application code and also authored the accompanying Appium test suite, while Kobiton’s MCP server connected both Claude Desktop and Claude Code to real devices. Using plain English instructions, the developer could simply ask Claude to run the app on real hardware, watching each test session live in the browser — this made hands-on acceptance testing possible without any manual device setup. Importantly, the workflow ensured Claude never validated its own work: every final verdict came directly from the physical devices running the tests, not from Claude itself. As a result, engineering, automated testing, and acceptance testing were all completed end to end within a single workflow. This shows how Kobiton’s MCP server and platform enable independent, real-device verification of AI-generated code, closing the loop between AI development and genuine hardware validation.
Key Highlights
Independent Verification: Test verdicts came from actual hardware, not from Claude itself.
AI-Built App: Claude Code wrote both the application and its Appium test suite.
Real Device Testing: Kobiton’s MCP server connects Claude Desktop and Claude Code to real hardware.
Plain English Control: Simple instructions triggered test runs on real devices, viewable live in-browser.
Claude Code & Kobiton for AI-Powered Testing
See how Claude Code wrote both an app and its Appium tests, then verified everything on real devices via Kobiton’s MCP server closing the loop between AI development and real hardware testing.
Additional Resources
Video Transcript
So I’ve been building my own app on nights and weekends, and it’s up to 48 builds now.
So Claude wrote the code, and Claude also wrote the test, or the Appium test.
The Kobiton MCP server runs both Claude Desktop and Claude Code.
So I could just say, in plain English, go run this on real devices, and it would handle it.
And I could watch the session run live in my browser, which is how I did my acceptance testing.
But it never got to grade its own homework.
That verdict came back from the hardware it couldn’t touch.
So I was able to do the engineering, the testing, and the acceptance testing, start to finish.
And that’s what the Kobiton MCP server and the Kobiton platform made possible.