Find your workday in drifty.
Development, freelance work, and study. Start with the example closest to your day.
Developers
A day of code, documentation, and review.
Explore a developer’s day ↗
Freelancers
The making, research, and communication between deliverables.
Explore a freelance workday ↗
Students
The flow from lectures to notes and research.
Explore a study day ↗
Different workdays need different answers.
Each guide starts with the question that role is most likely to ask. None turns drifty into a team monitor, invoice system, or learning outcome score.
| For | The hard-to-reconstruct part | What drifty helps review |
|---|---|---|
| Developers | Code, docs, terminals, reviews, and quick checks across many windows | Whether those switches formed one focused work thread or broke it apart |
| Freelancers | Research, making, feedback, communication, and admin behind a deliverable | Where the workday went without presenting the result as an invoice-ready timesheet |
| Students | Lectures, notes, research, and study-adjacent browsing on the same services | Where study continued, where it drifted, and which patterns are worth adjusting |
Start with a feature, if you prefer.
See how activity is recorded, classified, and reviewed.
See your own day in the record.
Record Mac activity without a new timer for every task.