Yesterday, I wrote about why I stopped trusting most scheduling tools.
Today, the UI is done.
And the database is done too.
What remains now is the part that often looks small from the outside, but matters the most in practice:
- polishing the UX/UI
- refining the flow
- finalizing the app name
It Started Simple
This project began as something small:
a lightweight posting companion for people who want more control over their writing before it goes public.
The core idea was simple:
- write offline
- tag the platform
- set a reminder
- when ready: copy, paste, publish
No account.
No cloud.
No subscription.
Your drafts stay on your device until you decide they are ready.
It No Longer Feels Like a Scheduler
The more I build it, the less it feels like a βscheduler.β
It is starting to feel more like a private space for words that are not ready yet β
a calmer layer between writing and publishing.
That shift matters.
Because the goal was never just automation.
It was always about:
- ownership
- privacy
- intention
- reducing friction without giving up control
Whatβs Left
The foundation is already there.
The database is in place.
The interface works.
Now the focus is on the part that actually shapes the experience:
- making the flow feel deliberate
- making the UI feel quiet
- making the tool feel reliable
- making the naming feel honest
I already have a few name ideas, but I am still not fully convinced by any of them.
That part matters more than I expected.
If the tool is about ownership, privacy, and intention, the name should not feel disposable either.
Still building.
