Products/CommunicationIn development
Conversation with continuity.
An offline-first messenger that keeps local intent, reconnects carefully and gives every interaction a sense of place.
Actual interface
SheraChat, in use.
- Durable message outbox
- Local conversation history
- Realtime reconciliation
- Physical interaction design
Development preview. Current message encryption is not end-to-end encryption. Calls and notifications depend on deployment configuration.

Shown in house tone · hover for true colour
In motion
How it behaves.
A live, illustrative sketch of SheraChat at work — drawn in code, with sample content. The screenshot above is the real interface.
Ayesha
Illustrative conversation
01
The problem
Connections drop. A send acknowledgement gets lost. People still need to know whether a message is saved, pending or actually delivered.
02
The thinking
Keep the user's intent first. Persist a message on the device before sending, then reconcile it with canonical history using a stable message identifier.
03
The engineering
Flutter, Supabase Auth, PostgreSQL history, Supabase Realtime and a Hive working set. A durable outbox retries safely after interruption.
04
The result
An implemented messaging architecture and a distinctive interaction system. Production release remains subject to device, security and backend checks.
Next product
Room to think. Tools to act.
