Inboxly

The interface is Dioxus rsx driven by explicit state. Compose state lives in its own signal, separate from the thread body, so typing a reply does not re-render and re-sanitise the message you are reading. Getting the signal boundaries right is what keeps the UI responsive under real load.

Incoming email is hostile HTML. It is sanitised before rendering, and links are rewritten through a sentinel scheme so a click goes through my own handler instead of straight out to whatever the sender embedded. Email is attacker-controlled input and the client treats it that way.

Conversations are threaded with the JWZ algorithm, the same approach mail clients have used for decades. On top of that, messages are grouped into Inbox-style bundles by a heuristic layer with user rules layered over it, so the important mail and the newsletters end up in the right places.

OAuth2 against Gmail and Outlook, with the token refresh and error handling that real accounts demand. This is the unglamorous part that decides whether an email client is usable or a demo.

PDF text extraction and image OCR run in pure Rust with no system C dependencies, so a scanned receipt or a PDF itinerary can be searched and summarised. When the OCR models are absent it degrades to a no-op instead of failing, so the feature never blocks the client from starting.