Product page
What works today and what does not
The Lycism page for olllo lists the working features, the limits and where it runs.
Open the product page ↗Loading your next stop
Independent product · In progress
Project in progress
Some things in a conversation should not disappear up the chat.

Current state
Chat sits beside a shared Space for notes, tasks, posts and a calendar. I have a working local prototype. Recovery, hosting and native apps still need work.
Evidence
The current state of the prototype, including what it cannot do yet.
Product page
The Lycism page for olllo lists the working features, the limits and where it runs.
Open the product page ↗Works today
Shown with demo accounts and test messages.
Not yet
These come before any public release.
Scope
Counts from the current build. They describe scope, not usage.
My part
olllo came from something I wanted in a messenger: a place for the plans that come out of a conversation. I came up with Chat and Space, worked out how they should fit together, designed the screens and wrote most of the app.
I used AI as an extra hand with the implementation. I still decide how olllo works and what needs fixing before I put it in people's hands. The frameworks and libraries underneath it keep their own licences and credits.
Starting point
Once a conversation moves on, I still need to find the note or the task we agreed on. Scrolling back through messages gets old. A task needs an owner and a date; a note needs somewhere I can find it again.
Space is the private area attached to a direct or group conversation. Notes, posts, tasks and a calendar stay beside the chat.
Working build
I can register, sign in, start a direct or group conversation, and save, reply to, react to, edit or delete messages. A failed send can be retried. Chat drafts and unsent messages survive a reload on the same device.
In Space, members can post and comment, search notes, switch between writing and preview, and give tasks an owner, priority and due date. Events and dated tasks appear in the calendar. Photo stories and short status notes can be shared with selected people and expire after 24 hours.
Behaviour
Each send has a retry key so trying again does not create a second message. Edits also check the saved revision. An old tab should not overwrite a newer version without telling me.
The service uses SQLite and server-sent events to tell the client to refresh. It does not support people editing the same document live. Notes and task drafts also do not yet survive interruptions in all the ways chat drafts do. I want to settle that before adding more screens.
Still in progress
Calls, voice messages, attachments, camera Instants, video stories and native apps are not built yet. Account recovery, blocking and reporting, device management, push notifications and running the hosted service also need work.
Conversations have membership controls, but messages are stored in readable form. There is no end-to-end encryption. The screenshot uses demo accounts and test messages.
Next
Before hosting olllo, I want to work through interrupted connections, account recovery and changes in group membership on real phones. I need to know what people will find when they come back to their conversation.
Next
Tell me what you’re working on and what needs work.
Email meLet’s see if I’m the right person.
You don’t need to know exactly what you need. Tell me where you are, and I’ll help determine where I fit.
Curious how this was made?
Open the Hood ↗