Skip to content

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.

SheraChat — actual interface capture

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.

A

Ayesha

Illustrative conversation

Offline · 1 message waiting
Are we still on for 4 pm?
Yes — I'll bring the notes.✓✓ delivered
Running 5 minutes late!
Message↑
  1. 01

    The problem

    Connections drop. A send acknowledgement gets lost. People still need to know whether a message is saved, pending or actually delivered.

  2. 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.

  3. 03

    The engineering

    Flutter, Supabase Auth, PostgreSQL history, Supabase Realtime and a Hive working set. A durable outbox retries safely after interruption.

  4. 04

    The result

    An implemented messaging architecture and a distinctive interaction system. Production release remains subject to device, security and backend checks.

FlutterSupabaseHive

Next product

SheraBot

Room to think. Tools to act.