Historical passkey-related reviews surfaced by Grab Watch. Links are attached to the review text so the table stays readable.
| Metric | Result |
|---|---|
| Distinct Google Play SG reviews | 14 |
| Distinct Apple App Store SG reviews | 1 |
| # The One-Line UX Fix Nobody Remembers: `overscroll-behavior: contain` | |
| ## The Core Idea | |
| Scroll chaining — when you scroll inside a modal, dropdown, or sidebar and suddenly the page behind it starts scrolling too — is one of the web's most persistent micro-frictions. And it's fixable with exactly one line of CSS: | |
| ```css | |
| .modal__content { | |
| overscroll-behavior: contain; | |
| } |
| # Atlas Explore and the Rise of Runtime-Derived App Maps | |
| ## The Core Idea | |
| Atlas Explore (by Revyl) uses a swarm of exploratory AI agents to crawl a mobile app like real users, automatically mapping every screen, transition, and navigation path into an interactive graph. What was previously a laborious manual artifact — the app sitemap — is now generated from observed runtime behavior. | |
| But the real shift here isn't the automation. It's that **the runtime becomes the source of truth for what your app actually is**, replacing the hand-drawn diagram or stale Figma file. | |
| ## The Three Converging Threads |
There's a YouTube talk making the rounds — Mashi Kat's "How I Built MapConductor," an open-source abstraction layer that wraps 5 different mobile map SDKs (Google Maps, Mapbox, MapKit, HERE, AGIS) under one API. On the surface it's about Android maps. Underneath it's a case study in why loop engineering is real.
Mashi Kat tried to unify 5 map SDKs. He thought it would be easy — he'd done a Google Maps plugin 10 years ago. It wasn't.
Final smart home plan after extensive iteration. Covers 5× Mitsubishi Starmex ACs, 2× existing Novita fans, 1× new Shark FlexBreeze (outdoor/portable), 1× XGIMI projector, 1× ceiling fan. Apartment: SG PR household, Orbi router with IoT WiFi enabled.
Heartbeat fires, agent runs, but messages never reach Telegram/Discord. No error, no log, complete silence. Broken across 3 installs.
The agent responds with HEARTBEAT_OK every time. OpenClaw's heartbeat pipeline strips this token and silently suppresses the message. The delivery code works fine — it just never has content to deliver.
Previous version of this gist attributed the failure to 1Password exec:op: secret resolution. That was wrong. Further testing proved the to field doesn't work with ANY token format.
The agents.defaults.heartbeat.to config field is parsed but never acted on. Heartbeat fires, the agent runs, but output stays in the session — never delivered to the specified channel.