Notes from
the team.
Product, engineering, trust & safety, design, and the broader phone-automation category. Written when we have something to say; not on a content schedule.
How we landed on $9 a month: pricing for a product that says no
Per-grab pricing was the obvious model and the wrong one. The four-month walk we took to a flat $9 tier, the three experiments along the way that failed, and the customers we deliberately price out.
A year of abuse reports: patterns, false positives, and what we changed
Twelve months of triaging reports to abuse@. The categories we expected, the ones we didn't, the false-positive rate, the four denylist additions that came directly from this channel, and one report that changed how we think about review SLAs.
Why we built smartordercapture
Phone automation has a trust problem and a design problem. We're trying to fix both, starting with a product that says no when no is the right answer.
How the denylist works (and why it has three layers)
Defense-in-depth for the categories of automation we refuse to enable: server validation, marketplace review, and a compiled-in on-device gate.
Two interpreters, one trace: how we test cross-language parity
The TypeScript builder simulator and the Kotlin on-device engine must agree to the byte on every fixture. Here's the test rig.
On Android's Accessibility API, used correctly
Google's policy for Accessibility apps tightened in 2023. Here's how we think about it, what we ship in the disclosure flow, and why we always plan for Play Store removal.
Designing the marketing site with the Wix design language
Why we adopted a Wix-flavored visual system, how pill buttons changed our marketing copy, and the tokens we kept vs. dropped.
Get new posts in your inbox.
Maybe one email a month. No tracking, no "sponsored content", no growth-loop referral nudges.