mARTin
a5371e7476
Files: - STACK.md - FEATURES.md - ARCHITECTURE.md - PITFALLS.md - SUMMARY.md Key findings: - Stack: React 18.3+ with Next.js 16+ and Jotai for state management - Architecture: Component-based with clear data flow - Critical pitfall: Inconsistent date/time handling and calendar integration fragility
72 lines
3.3 KiB
Markdown
72 lines
3.3 KiB
Markdown
# Feature Landscape
|
|
|
|
**Domain:** Weekly Scheduler with Calendar Integration
|
|
**Researched:** Sat Jan 24 2026
|
|
|
|
## Table Stakes
|
|
|
|
Features users expect. Missing = product feels incomplete.
|
|
|
|
| Feature | Why Expected | Complexity | Notes |
|
|
|---------|--------------|------------|-------|
|
|
| Weekly view display | Core functionality - primary user interface | Low | User needs to see tasks organized by week |
|
|
| Task creation/editing | Essential workflow for any task manager | Low | Users must be able to add and modify tasks |
|
|
| Task deletion | Basic CRUD functionality | Low | Users need to remove tasks they no longer need |
|
|
| Day navigation | Core usability feature | Low | Users need to move between weeks |
|
|
| Responsive design | Modern expectation for web apps | Low | Works on mobile, tablet, and desktop |
|
|
| Local storage persistence | Offline access and data retention | Low | Keeps data available between sessions |
|
|
| Drag and drop reordering | Intuitive interaction pattern | Medium | Improves task organization workflow |
|
|
| Date/time selection | Essential for task scheduling | Low | Users need to assign time slots to tasks |
|
|
|
|
## Differentiators
|
|
|
|
Features that set product apart. Not expected, but valued.
|
|
|
|
| Feature | Value Proposition | Complexity | Notes |
|
|
|---------|-------------------|------------|-------|
|
|
| Calendar integration (Google/Apple) | Sync with existing calendar systems to avoid duplicate entries | High | Adds significant user value by connecting with established workflows |
|
|
| Theme customization | Personalization enhances user satisfaction and retention | Low | Small visual improvement that increases user connection |
|
|
| Recurring tasks | Saves time for regular activities | Medium | Advanced scheduling feature that users appreciate |
|
|
| Task categories/tags | Better organization and filtering | Medium | Helps users manage complex task sets |
|
|
| Reminder notifications | Helps users stay on schedule | Medium | Adds utility beyond simple task tracking |
|
|
| Export/import functionality | Data portability and backup | Medium | Allows data migration and backup options |
|
|
|
|
## Anti-Features
|
|
|
|
Features to explicitly NOT build. Common mistakes in this domain.
|
|
|
|
| Anti-Feature | Why Avoid | What to Do Instead |
|
|
|--------------|-----------|-------------------|
|
|
| Complex permission system | Overcomplicates basic task management | Keep it simple with single-user focus |
|
|
| Email notifications | Noise and distraction for users | Consider only if specifically requested |
|
|
| Multi-user collaboration | Expands scope beyond MVP | Focus on individual task management first |
|
|
| Advanced reporting analytics | Increases complexity without immediate value | Defer to later phases if needed |
|
|
|
|
## Feature Dependencies
|
|
|
|
```
|
|
[Day Navigation] → [Weekly View Display] (Week view needs navigation)
|
|
[Task Creation] → [Task Storage] (Need storage to save tasks)
|
|
[Calendar Integration] → [Task Storage] (Requires data to sync with calendar)
|
|
[Drag & Drop] → [Task Storage] (Needs to persist reordered tasks)
|
|
```
|
|
|
|
## MVP Recommendation
|
|
|
|
For MVP, prioritize:
|
|
1. Weekly view display
|
|
2. Task creation/editing/deletion
|
|
3. Day navigation
|
|
4. Local storage persistence
|
|
|
|
Defer to post-MVP:
|
|
- Calendar integration
|
|
- Recurring tasks
|
|
- Theme customization
|
|
- Reminder notifications
|
|
|
|
## Sources
|
|
|
|
- Competitor analysis: TeuxDeux, Tweek.so, Google Tasks
|
|
- User experience research (2025)
|
|
- Task management applications market trends |