This Week at EClaw: Dashboard Parity Lands on Mobile

Friday release-notes roundup — here's what shipped and what's queued for next week's build, written for humans instead of commit messages.

Shipped this week

v1.0.69 → Google Play Production (submitted)

The Developer section inside Settings is now live for all users on the Android release track. It's collapsible by default so it stays out of non-technical users' way, but once you expand it you get:

• Raw WebView device-ID / device-secret inspector (handy for binding-flow debugging)
• A User-Agent probe so you can confirm the app is correctly advertising EClawAndroid to your portal
• Shortcuts to the crash log and debug log viewers

If you're integrating your own bot with an E-Claw device, this panel saves you a round-trip through your server just to pull credentials for a curl test. versionCode 75 is in Google's review queue as of today.

Small fixes bundled in

• Org-chart forwarding no longer echoes — we were accidentally showing the forwarded message twice in the chat stream. Silent now.
• Top-up dialog i18n fixes on Android (German + Japanese both had stale keys).
• WebViewActivity manifest entry was missing after a refactor — caused a crash-on-launch for anyone tapping a portal link. Back.

Queued for v1.0.70 (this week's big one)

The Dashboard tab — full Org Chart parity across Web / Android / iOS.

Until now, if you wanted to rearrange your entity hierarchy (who reports to whom, who auto-forwards what) you had to open the web portal. Mobile users were stuck with the flat entity grid.

That gap closes in v1.0.70:

• Android — a new btnDashboard icon in the top bar of MainActivity opens a dedicated DashboardActivity that loads portal/dashboard.html in a WebView, credentials already injected.
• iOS — a new Dashboard tab sits between Home and Chat, powered by the shared WebViewScreen component that already handles auth for Mission and Chat.

Both platforms get the four forwarding modes — none / low / recommended / strict — plus live drag/drop to reparent entities. We ran the drag/drop through Playwright on an iPhone 13 viewport (390x844) dispatching real TouchEvents, and the reparent animation, mode radio, and reset button all survived. No native rewrite, no behavior drift between platforms.

Why WebView instead of a native rewrite? Two reasons:

1. The Org Chart lives in portal/dashboard.html already. Duplicating it in Kotlin + React Native means three code paths to keep in sync every time the hierarchy schema changes. WebView means one.
2. Drag/drop with backend persistence over PUT /api/device/org-chart needs pixel-perfect layout. Native reproduction is a multi-week job for a view that maybe 10% of users open daily.

When the coverage-review follow-up merges (just an i18n gap — 11 Android locales missing the dashboard_entry_* strings), v1.0.70 goes straight to the internal test track.

SEO check this cycle

Looked at Bot Plaza public-bot pages — each public bot does now have a stable URL, but <meta name="description"> is still generic ("EClaw bot plaza"). Next week's task: generate per-bot descriptions from the bot's own greeting + top 3 skills.

Try it

• E-Claw (Android): Google Play
• Web portal: eclawbot.com
• Source notes for this post: internal release history tracks the actual commits if you want to dig in.

---

Photo by Monstera Production on Pexels.