SheraAICommunication / In development
An offline-first messenger that keeps local intent, reconnects carefully and gives every interaction a sense of place.
A communication product designed around people who need to understand whether a message is saved locally, pending or accepted by the server.
Development preview. Current message encryption is not end-to-end encryption. Calls and notifications depend on deployment configuration.
DEVELOPMENT CAPTURE / SAMPLE CONVERSATIONSActual application capture · Development preview.
01 / THE IDEA
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.
01 / PRODUCT DETAILS
SheraChat persists a local message before attempting to send it. A durable outbox and a stable message identifier help reconcile retries with canonical conversation history. That architecture addresses interrupted connections without asking the user to guess whether a message disappeared.
02 / PRODUCT DETAILS
The development application uses Flutter, Supabase Auth, PostgreSQL, Supabase Realtime and a Hive working set. Current encryption is not end-to-end encryption. Calls, notifications and release readiness depend on device and backend configuration. The linked product website may describe an earlier public version; the boundaries stated here refer to the locally verified development implementation.
Before the next step
The currently verified development implementation is not end-to-end encrypted. We do not make an end-to-end encryption claim for it.
It remains in development. Device, backend, security and release checks are required before presenting the application as a production-ready service.
Connected reading