What is planned, what is being explored, and what has no date on it.
Buds started as a way to get work written down and moving without fighting the tool. What follows is where it goes next: history you can trust, search across everything, daily planning, dates and reminders, stats, and eventually accounts and sharing.
Multi-board workspaces, tasks and sub-tasks, Urgent workflows, real completion state, flexible sections, Undo/Redo, import/export protection, storage monitoring and automatic local backups are already done. Everything below builds on them.
The modular architecture, regression suite, developer documentation, and stable HTTPS deployment at pyips.com/buds/ are complete. The live v0.1.0 release passed static deployment checks and full browser E2E verification, including persistence across a complete Chromium restart.
The original monolithic HTML application was split into clear HTML, CSS, and JavaScript source without changing the app's behavior or local data format. Buds now builds and tests the hosted browser client directly from that modular source.
The refactor mapped the data model first, added automated coverage for major workflows, and documented the real module structure, storage contracts, completion rules, urgency semantics, backups, imports, and development workflow.
The product is now Buds and is hosted from its stable HTTPS home at pyips.com/buds/. The browser is the canonical client, with portable workspace export/import retained as a user-controlled safety and migration tool.
Next up is turning completion data into a History you can trust, and making the whole workspace searchable.
Choose the right long-term home for completed history. If accounts are close, skip a temporary migration. If the backend is still far away, IndexedDB can keep years of History from bloating the active workspace.
Browse completed tasks and sub-tasks by exact time, day, week, month, board, and tag. Preserve reopen events and the fact that work was Urgent when completed so future reporting stays truthful.
Search across boards for tasks, sub-tasks, notes, and tags instead of remembering where something lives. Over time, search can expand into History and richer saved views.
Kanban stays the planning system. Daily Plan becomes the lightweight execution layer: a focused list of what you intend to actually finish on a specific day.
A collapsible workspace-wide checklist above Queue with standalone items, linked Kanban tasks, recurring occurrences, date navigation, progress, and user-controlled overdue behavior.
Wrap up the day in one action. Depending on your Daily Plan settings, unfinished work can stay attached to its original day or carry forward to tomorrow until it is completed.
Give tasks due dates and optional times, then add a real Calendar for appointments and events. Upcoming work can surface in Daily Plan and eventually trigger reminders a day or two before it matters.
History and Daily Plan produce data worth trusting, which is what Stats and goals need. Motivation features are optional and stay optional.
See completed work today and this week, progress by board or tag, Daily Plan completion, Urgent success, and longer-term patterns.
Set goals that use real completion data: finish a number of tasks, complete a percentage of today's plan, clear all Urgent work, or hit a focused target for a board or tag.
Unlock rewards you picked yourself by hitting real goals, including locked reward cards that open when you finish one. Streaks and achievements might follow.
The hosted local-first edition does not need accounts. When the product is ready for them, Buds can move to a Django/PostgreSQL backend where the server becomes the authoritative source of truth.
User accounts, multiple workspaces, multiple boards inside each workspace, PostgreSQL persistence, server-side ownership checks, and a dashboard for managing the larger account.
Detect local Buds data and offer to import it into the user's account. Normal saves live in PostgreSQL; infrastructure snapshots protect the service; portable Download workspace backups remain available to the user.
Start small with shared tasks and boards, then grow into assignments, workspace membership, permissions, comments and team workflows.
Once server persistence is stable, browser and mobile capabilities can expand without forcing premature synchronization complexity into today's local-first build.
Add a service worker, installable app experience, and a proper offline-capable shell so Buds can feel more like an application while still running on the web.
Move beyond in-app warnings to browser/OS notifications for task deadlines, Urgent work, upcoming calendar events, and reminders that can reach desktop or phone when the app is not actively open.
IndexedDB can become a client cache, offline changes can queue safely, and reconnect logic can synchronize with the server. Real-time multi-user updates can follow after the basic conflict model is trustworthy.
None of this is committed. Any of it could change, get folded into something else, move to a different Pyips app, or just not get built.
Search, create, update, move and plan tasks by typing at it, if there turns out to be a sane way to do it.
Research firstA larger notes area linked to tasks and boards without turning Buds into a general writing editor.
ExplorationFriend/team connections, shared to-dos, lightweight messaging, and collaboration built outward from useful sharing.
ExplorationComplete real work to water plants, grow a garden, harvest resources, and feed optional pet-style progression.
Gamification labOnce the core app is solid, outlining, plotting and writing-project organization could live in templates or a Tale Tower edition.
Future branchOrder, names, details and whole ideas can change as Buds gets built and tested. What the app does today is on the Features page. This page is the part that is not built yet.