Teardowns / OpenClaw iOS
Design teardown · iOS app critique
OpenClaw iOS design teardown
In July 2026 we put the OpenClaw iOS app's onboarding and chat screens on one page and ran them through Pincushion. Pincushion AI pinned the confusing spots, independent OpenClaw contributors pinned what bothered them, and Pincushion's founder opened a PR with fixes from the approved pins. Here's the crit, the contributors' own pins, and what actually merged.
Why OpenClaw iOS caught our eye
OpenClaw is an open-source agent with a native iOS companion app. The friction sat where it usually does in a first run: pairing steps that assume context the newcomer doesn't have yet, status text that contradicts itself, and a connected chat that opens to an empty screen.
The annotated page
The pins above are live. Open the full annotated critique →
What we'd change — 3 findings
- 1A connected chat that opens to dead air. Nothing hints at what the agent can do, and the Talk/Control/Agent tabs go unexplained. Add two or three tappable starter prompts as the empty state.
- 2A '?' badge on the agent avatar. It reads as a broken image and nothing explains it. If it means no avatar is set, show initials; if it's a status, label it.
- 3The success screen prints the host twice. 'localhost' and then 'localhost:19001'. Show one host:port, so the moment that should feel clean isn't noisy.
What OpenClaw contributors pinned
Benji and Eisenh0rn40, independent contributors to the open-source OpenClaw project, pinned the same screens on July 2, 2026 (Benji 11 pins, Eisenh0rn40 3). Three of their pins, word for word, with what happened to each:
-
BenjiOpenClaw contributor
“It would be nice if there was option to easily copy this command, so users didnt have to type it out. Simple copy command button would do the trick”
Shipped: /pair qr now has a copy action with copied feedback (PR #99243).
-
Eisenh0rn40OpenClaw contributor
“Where does this button tale you when you are just connected?”
Shipped: The success button now reads Go to Chat and actually opens Chat (PR #99243).
-
BenjiOpenClaw contributor
“I think these tabs can be simplified. Voice/Chat could basically be in the same view. …”
Not shipped: The agent built it, but the merged PR deliberately kept Talk separate from Chat.
What shipped
openclaw/openclaw #99243: Polish iOS onboarding and chat critique fixes · merged Jul 4, 2026 by steipete
The PR cites this crit as its baseline. It landed a reviewed subset: starter prompts in the empty chat, the avatar fallback, the pairing copy action, one endpoint on the success screen and a working Go to Chat. It rejected changes that didn't hold up, such as merging Talk into Chat and a pairing command that doesn't exist.
Each of these is a pin. On your own site, Pincushion hands that pin straight to your coding agent with the selector, screenshot, and thread attached — so the fix ships, not just the note.
Want this on your own site?
Pincushion runs the same critique on your page, free. Stakeholders (or our AI critic) drop pins on the real elements, your coding agent reads them through the MCP server, and the deploy loop tracks the fix to a merged PR. No tickets, no Kanban.
FAQ
- What is a design teardown?
- A short, honest critique of a live page. We pin the two or three things that actually move clarity or conversion on the real page, and explain the fix for each. No score, no generic checklist.
- Is OpenClaw iOS involved in this teardown?
- Yes. Independent OpenClaw contributors pinned these screens on July 2, 2026. Pincushion's founder opened PR #99243 with fixes from those pins, and an OpenClaw maintainer merged it on July 4, 2026. Nothing here is sponsored.
- Are you OpenClaw iOS and want this taken down?
- Just ask — email hello@pincushion.io and we'll remove it, no questions asked. We only teardown pages whose owners publicly asked for feedback, but it's your call.
- Can I get a teardown of my own site?
- Yes, and it's free. Start here — Pincushion pins the issues on your real page and hands each one to your coding agent to fix.