I'm Itamar. I run a construction business, and most of my real tasks arrive in WhatsApp groups, voice notes and email. I built Focus 100 to read those and turn them into tasks. Here's what mattered technically.
1. Input: notifications, not chat history
On Android, a NotificationListenerService limited to the apps the user picks (WhatsApp, WhatsApp Business, mail apps). It only sees new messages that post a notification, so muted chats are invisible. That limit is a feature for privacy: no scraping, no linked device.
2. Let the model plan, let code verify
Each message (with a bit of same-chat context) goes to a stateless server that asks Claude for structured JSON: task / promise-to-me / event / noise, title, due date, suggested reply. Then plain code checks it: weekday and "tomorrow" fixes, group rules (a task only when you're named, tagged, or everyone is asked), dedup, calendar clashes.
3. The assistant gets no PII it doesn't need
Poki, the assistant, receives a contact summary (names, relations, which channels exist, the usual channel) but no numbers or addresses. The phone fills those in at execution time. Every outgoing message is a card with editable text and a Send button.
4. Model choice was about latency
Our own open model (Gemma on a serverless GPU) was about as accurate as Claude Haiku on a small eval, but cold starts were 110-170 s. We switched to Claude (~$0.0006/request) and kept the open model as a fallback.
5. Storage and sync
Tasks live on the device. Optional sync is end-to-end encrypted (AES-GCM, key only on devices); the server holds one ciphertext per space; merge is last-write-wins per task with tombstones.
6. iPhone
iOS doesn't let apps read other apps' notifications, so on iPhone it's a web app (paste, import an exported chat, or talk to Poki).
It's free, no account, no ads; web app in 15 languages. I'm the developer, and I'd love feedback on false positives in busy group chats.
Android: https://focus100-il.netlify.app/get?ref=devto
Web: https://focus100-ios.netlify.app
Top comments (0)