Competitive Matrix
Overview
Daylight competes on a different axis than most task apps. While mainstream tools optimize for convenience and features, Daylight optimizes for data ownership and reliability.
This matrix compares Daylight against popular alternatives on the dimensions that matter to our target users.
Quick Comparison
| Aspect | Daylight | Todoist | Notion | TickTick | Obsidian Tasks | Things 3 |
|---|---|---|---|---|---|---|
| Data ownership | ✓ Local files | Cloud | Cloud | Cloud | ✓ Local files | Local + cloud |
| File format | Markdown/YAML | Proprietary | Proprietary | Proprietary | Markdown | Proprietary |
| Offline | ✓ Full | Limited | Limited | Limited | ✓ Full | ✓ Full |
| Sync method | BYO (Syncthing) | Built-in | Built-in | Built-in | BYO | iCloud |
| Recurrence model | Instance-based | Series-based | Manual | Series-based | Plugin-based | Series-based |
| Price | Free | $48/yr Pro | $96/yr Plus | $36/yr Premium | Free (plugin) | $50 one-time |
| Platforms | Android + Linux | All | All | All | All | Apple only |
Detailed Comparison
Data Ownership
| Product | Approach | What it means for you |
|---|---|---|
| Daylight | Tasks are .md files in a folder you control | Open them in any editor, sync with any tool, keep them forever |
| Todoist | Data lives on Todoist servers | Export via JSON, but dependent on their service |
| Notion | Data lives on Notion servers | Export to Markdown possible, but lossy |
| TickTick | Data lives on TickTick servers | Export available, proprietary format |
| Obsidian Tasks | Local Markdown files (like Daylight) | Same portability benefits; plugin adds task features |
| Things 3 | Local database + optional iCloud sync | Export possible, but not plaintext |
Daylight’s position: Full ownership. Your tasks work without the app.
Recurrence Reliability
| Product | How recurrence works | The problem |
|---|---|---|
| Daylight | Each instance tracked separately with its own status | None—complete today without affecting tomorrow |
| Todoist | Series-based: tracks “next occurrence” date | Completing early can skip instances; history is limited |
| Notion | Manual: you create each recurrence yourself | No automation; easy to forget |
| TickTick | Series-based: moves to next date on completion | Same issues as Todoist |
| Obsidian Tasks | Plugin-dependent; varies by implementation | Quality depends on plugin; can be fragile |
| Things 3 | Series-based with “after completion” option | Better than most, but still series-based |
Daylight’s position: Instance-based tracking eliminates the “I completed Friday but lost next Friday” problem.
Offline Capability
| Product | Offline behavior | Reality |
|---|---|---|
| Daylight | Full offline—everything works | No network needed for any operation |
| Todoist | Read-only cache; limited editing | Can view and check off, but features degraded |
| Notion | Very limited offline | Essentially unusable without connection |
| TickTick | Cache with sync queue | Works for basic operations, sync on reconnect |
| Obsidian Tasks | Full offline (local files) | Same as Daylight |
| Things 3 | Full offline (local database) | Works completely offline |
Daylight’s position: Offline is the default, not a fallback mode.
Sync Approach
| Product | Sync mechanism | Tradeoff |
|---|---|---|
| Daylight | User-managed via Syncthing/Dropbox/etc. | Setup required; full control; no vendor dependency |
| Todoist | Automatic via Todoist servers | Zero setup; data lives on their servers |
| Notion | Automatic via Notion servers | Zero setup; data lives on their servers |
| TickTick | Automatic via TickTick servers | Zero setup; data lives on their servers |
| Obsidian Tasks | User-managed (same options as Daylight) | Same tradeoff as Daylight |
| Things 3 | iCloud (Apple only) | Easy setup; Apple ecosystem lock-in |
Daylight’s position: You control sync. More setup, more control, no vendor lock-in.
Time Tracking
| Product | Approach | Limitations |
|---|---|---|
| Daylight | Manual time entries with 15-min snapping | No timers—entry captures reality |
| Todoist | Duration estimates (Premium) | Estimates, not tracking |
| Notion | Custom properties possible | Build-your-own; no structure |
| TickTick | Pomodoro timer + duration | Timer-based; forgets when you forget |
| Obsidian Tasks | None built-in | Requires separate plugin or manual |
| Things 3 | None | No time tracking at all |
Daylight’s position: Manual entry beats forgotten timers. Log what actually happened.
When to Choose Each
Choose Daylight When
- You want to own your data as portable files
- You value offline reliability over cloud convenience
- You’ve been burned by recurring task bugs in other apps
- You’re already running Syncthing (or willing to set it up)
- You use Linux or Android as primary platforms
- You don’t need team collaboration
Choose Todoist When
- You want zero-friction cloud sync across all platforms
- You need sharing and collaboration features
- You prefer managed service over self-managed
- Natural language input is important to you
- You’re okay with subscription pricing
Choose Notion When
- Tasks are part of a larger knowledge/project system
- You need flexible databases and views
- Team collaboration is essential
- You’re invested in Notion’s ecosystem
- Task-specific features are secondary to flexibility
Choose TickTick When
- You want Pomodoro timers integrated with tasks
- You need calendar integration with time blocking
- Multiple list views (Kanban, calendar, etc.) matter
- Habit tracking alongside tasks is important
- Price is a factor (cheaper than Todoist)
Choose Obsidian Tasks When
- Your tasks live alongside notes in Obsidian
- You want the same file-based benefits as Daylight
- You prefer plugin customization over opinionated design
- Desktop-first workflow (mobile is secondary)
- You’re comfortable with Obsidian’s learning curve
Choose Things 3 When
- You’re fully in the Apple ecosystem
- You value design polish and simplicity
- One-time purchase matters (no subscription)
- You don’t need Android/Windows/Linux
- Offline reliability is important but iCloud sync is acceptable
Positioning Summary
Daylight’s Unique Position
Daylight occupies a specific niche: local-first task management with reliable recurrence, for users who prioritize data ownership.
No other option offers all of:
- Portable Markdown files (not proprietary database)
- Instance-based recurrence tracking
- Android + Linux native apps
- No cloud dependency or subscription
- Manual time tracking built-in
Competitive Advantages by Feature
| Advantage | Why it matters | Who cares |
|---|---|---|
| Portable Markdown files | Tasks survive any app | Power users, privacy-conscious |
| Instance-based recurrence | No lost or duplicated instances | Anyone with weekly/daily tasks |
| BYO sync | No vendor lock-in | Privacy-conscious, self-hosters |
| No subscription | One-time setup, forever use | Cost-conscious, subscription-fatigued |
| Android + Linux | Underserved platforms | Developers, Linux users |
Where Competitors Win
| Competitor | Beats Daylight when… |
|---|---|
| Todoist | User wants zero-setup cloud + NLP + collaboration |
| Notion | Tasks are secondary to knowledge management |
| TickTick | Timers and habit tracking are essential |
| Obsidian Tasks | User is already all-in on Obsidian |
| Things 3 | User is Apple-only and values polish |
Messaging Against Competitors
vs. Todoist
“Todoist is great until you need to export or they raise prices. Your Daylight tasks are files—export is instant, subscription is zero, and your data works without asking permission.”
vs. Notion
“Notion can do tasks, but it’s not built for tasks. Daylight is focused: create a task, schedule it, complete it. No database setup, no template hunting.”
vs. TickTick
“TickTick has more features. Daylight has fewer features you’ll actually use, and your data stays on your device.”
vs. Obsidian Tasks
“Obsidian Tasks is powerful but plugin-fragile. Daylight is a native app with instance-based recurrence built in, not bolted on.”
vs. Things 3
“Things 3 is beautiful but Apple-only. Daylight works on Android and Linux, and your tasks are Markdown—not a proprietary database.”