OmniPlanner

Problem

Personal planning breaks down when the system is split across too many surfaces.

Goals live in one place. Weekly planning lives somewhere else. Habits become a separate tracker. Calendar blocks sit in a calendar app. Email keeps pulling attention back into the inbox. The result is not a planning workflow. It is a collection of disconnected reminders.

Generic productivity apps can fail from the other direction. They become heavy enough to avoid, or abstract enough that they stop helping with daily execution. A task list is not the same as a week. A week is not the same as a goal system. A calendar block is not the same as a habit.

AI assistance is only useful if it attaches to structure. A floating chatbot can suggest plans, but it does not become the place where the user’s week, goals, habits, calendar, and email workflow actually live.

Solution

OmniPlanner is a desktop-first local planning workspace.

The app is aimed at the practical overlap between weekly structure, goals, habits, calendar blocks, email, and optional AI support. It treats planning as a working surface instead of a passive database.

The product direction is close to an “executive life OS” style app, but grounded in local workflows: open the desktop app, see the planning system, adjust the week, and use AI as assistance inside that structure rather than as the entire product.

Core Systems

Weekly Planning

The central planning surface: organize the week as a concrete operating unit instead of a loose pile of tasks.

Goals

Goal structure gives the week direction and keeps planning tied to longer-running intent.

Calendar Blocks

Time blocks connect plans to execution windows, making the schedule part of the planning workflow.

Habits

Habit tracking keeps recurring behavior visible beside goals and weekly execution.

Email Workflow

Email is treated as part of the organization surface instead of a separate attention trap.

Optional AI Assistance

AI support belongs inside the planning system, helping organize and reason over structure without replacing user ownership.

Local Data / Desktop Launcher

App data is stored locally on the device, and the project is built as a desktop app rather than a browser-only planner.

Windows Launch + Shortcut Flow

run.bat provides the launch path, while create-shortcut.bat creates a desktop shortcut. The launcher installs dependencies on first run, builds if needed, then opens Electron.

Technical Highlights

Built a desktop-first productivity app rather than a web-only planner.
Used Electron with a Vite/React/TypeScript app structure.
Designed around local-first app data.
Created a simple Windows launch path with dependency install, build, and app launch behavior.
Added shortcut creation so the app can be re-entered like a normal desktop workspace.
Structured planning around goals, weeks, habits, calendar blocks, and email instead of one generic task list.
Framed AI as optional assistance inside a planning system, not the entire product.

Current Status

OmniPlanner is a working desktop app and active secondary project.

The Windows launch flow exists: the top-level scripts route into the app folder, run.bat launches the app, and create-shortcut.bat creates a desktop shortcut. The app stores data locally on the device. The project also has developer commands for install, build, launch, Vite dev server, and Electron start flows.

This is not being presented as a polished public release. Public polish, packaging, and deeper documentation are still ongoing work unless the repo proves otherwise.

What This Demonstrates

Desktop app development Product design for personal workflows Local-first data thinking Practical launcher/setup design AI-assisted productivity design UX structure for planning systems