Application development
Phoenix Daily Planner
Phoenix is an application for organizing daily tasks and projects. Its personal and work spaces are separate: everyday plans belong in one space, while work tasks and projects can be followed in the other.
Names, projects and financial figures in these images are demo data.
- Field
- Application development
- My role
- Product architecture, UX and implementation
- Platform
- Persian-first, RTL progressive web app
- Client
- Mr. Mojtaba Rashnoo
- Project status
- Built; actual personal and work interface captures with demo data. Product functionality has not been independently evaluated.
Project gallery
2 imagesDaily plans, alongside habits and goals
The personal view places the next action beside the day's schedule. Habits, the active goal and a financial summary are visible in the same daily overview, without requiring a separate visit to each area.
- Next action
- Daily schedule
- Habits and goals
A work space for decisions and follow-through
The work view starts with a decision queue: blockers, approvals and risks needing attention. My tasks, project health and team workload follow on the same page, connecting the state of the work with people's capacity.
- Decision queue
- Project health
- Team workload
One product, two distinct contexts
Simplicity is not only about fewer features. Boundaries between contexts, and deciding where each thing belongs, matter just as much.
Context
Personal routines and team work need different kinds of structure. Phoenix brings them into one product without treating them as the same context.
The problem
How can daily planning stay quick and simple without losing the structure needed for projects, teams and reporting?
Thinking
The first decision separates personal and work spaces: habits, goals and learning together; projects, teams and reports in their own context. Complexity is placed deliberately rather than simply removed.
Direction
A second decision offers different views of work: a list for scanning, a board for status, calendar and timeline for time, and Gantt and workload for dependencies and capacity. A third keeps data local and supports offline use.
The work
Personal and work spaces, multiple task views, Persian RTL and dark mode. IndexedDB keeps data in the browser; personal-os-v4 and PWA support offline use.