phones are full of tiny chores. unlock, find the app, wait, read whatever interface changed this week, tap through it, close. orca starts with the sentence you were going to say anyway and carries the task across the phone from there.
send a normal message on whatsapp or telegram, like “order a veg burger from the place down the street and book a cab to the office.” orca turns that into two jobs, maps each one to phone actions, and reports progress in the same chat.
how it moves
the webhook normalizes messages from both chat platforms into one request shape. intent parsing extracts the task, entities, account context, and any approval boundary. a request with food and travel becomes a small graph with two branches and an explicit dependency wherever one result feeds the other.
each graph node describes an app action and the screen state expected before it runs. the android executor uses adb and accessibility hooks to open apps, type, tap, swipe, and read enough of the current screen to know whether the action landed. retries belong to the node, so one ugly loading screen does not restart the whole task.
the run carries checkpoints, screenshots, and a compact event log. if a device drops halfway through, the scheduler can pick up from the last clean node. actions that spend money or send something irreversible stop for confirmation in chat, then the graph continues with the receipt or booking id attached.
the useful interface is the progress stream: opening swiggy, finding the item, waiting for approval, booking the cab, done. the phone can stay on the desk while the chat keeps enough context for you to interrupt or correct the run.
whatsapp already carries half of daily life in india. orca makes that chat a control surface for the apps underneath it, which is much closer to how people ask for help in the first place. also i know which city you opened this from.