DawdleMobile
A mobile workflow system for real daily planning
Dawdle was built to support real routines instead of idealized productivity systems. The app combines tasks, events, and calendar context so planning and execution happen in one place.
The product direction was shaped around reducing context switching and making it easier to decide what to do next, especially when plans change mid-day.
Most task apps separate planning from execution
Many productivity tools make users jump between disconnected screens for tasks, events, and priorities. That fragmentation creates friction and weakens consistency.
"The product should reduce decision fatigue, not create more of it with endless setup and context switching."
The goal here was to create one coordinated flow where date context, priorities, and scheduling decisions work together instead of competing for attention.
Designing for daily clarity and momentum
The UX emphasizes guided input, progressive disclosure, and clear status feedback. Instead of forcing large forms, users move through structured steps with visible progress.
A dual-view layout supports both strategic planning (calendar context) and immediate action (upcoming list), helping users adapt without rebuilding their entire day.
State and data flows built for consistency
Dawdle uses context providers and custom hooks to centralize auth, date state, tasks, and events. This keeps screen-level components focused on UI while behavior stays modular.
The architecture supports pull-to-refresh updates, predictable data access patterns, and a clear boundary between app logic and service-layer persistence.
Task setup needed richer input than a single form while still feeling fast on mobile.
Implemented a multi-step wizard with clear progress indicators and compact, focused prompts for each decision.
Users needed different planning modes depending on whether they were scheduling ahead or acting now.
Added complementary calendar and upcoming-list views with shared date context to maintain continuity across screens.
Key takeaways
This project sharpened how I design and engineer around daily-use behavior instead of feature checklists.