How Memoify works
A walkthrough of a typical day with Memoify, from opening the app to closing out the evening.
1. Open the app
The first time you visit, Memoify sets up a small PostgreSQL database inside your browser using PGlite. Everything you do — adding tasks, starting timers, reordering — writes to that local database first. You can install Memoify from the browser menu to launch it as a standalone app.
If you sign in with Google or email, the local database syncs to the cloud so you can pick up on another device. If you don't sign in, everything stays on the current device.
2. Plan the day
Add tasks to today's list. For each one, set a rough duration — how long you think it will take. Don't overthink it; you'll see quickly whether you're calibrated. If you connected Google Calendar, the smart suggestions panel will offer pre-filled tasks for today's events. Drag tasks up and down until the order feels right.
3. Work the first task
Pick the task at the top. The countdown timer locks on to it. Start the timer and work. The task's remaining duration ticks down. When you finish early, stop the timer and mark it complete. When you run long, stop the timer and either split the task (two smaller chunks) or punt the rest to tomorrow.
4. Handle interruptions
Something unplanned comes up. Add it as a new task, drag it to the top of the list, start its timer. When it's done, move on to the next thing. Memoify isn't trying to enforce your plan — it's trying to track the difference between plan and reality, so you can adjust.
5. Close out the day
At the end of the day, anything still unfinished stays in the list for tomorrow with one click. The calendar view shows the full shape of the week, so you can glance at what's ahead before closing the laptop. If you use shared collections, your collaborators see the updates next time they open the app.
What happens when you're offline
Nothing changes. Tasks, timers, edits, reordering — all of it runs against the local database. When the network returns, the app syncs your changes to the cloud and pulls down anything new from other devices. Conflicts are rare because most edits happen on one device at a time.