Device Role Design is the practice of intentionally assigning different PKM roles to different devices rather than seeking feature parity across all of them. Instead of making every device do everything, you let each device's form factor shape a specific workflow.
Key Points
A typical device role assignment might look like this: desktop for deep work and note-making (full plugin suite, complex queries, long writing sessions); tablet for reading and annotation (Readwise, PDF markup, highlight review); mobile phone for quick capture and evening journaling only (minimal plugins, simplified interface).
Mike Schmitz advocates this pattern. The core principle: not every device needs to do everything. This is constraint as a feature, not a limitation.
The benefits are both practical and psychological. On the practical side, you reduce the need to sync the full vault everywhere. You limit installed plugins per device, which improves performance and reduces maintenance overhead. You avoid the configuration sprawl of trying to make a phone replicate a desktop experience.
On the psychological side, device role design creates intentional friction. If your phone is only set up for capture and journaling, you can't fall into the trap of "just quickly checking" your notes and ending up in an hour-long rabbit hole when you should be present. If your tablet is dedicated to reading, opening it signals "reading time" rather than "do everything time." The device becomes a physical cue for a specific mode of work.
This aligns with the broader principle that constraints enable creativity and focus. Having fewer options on a given device means less decision fatigue about what to do with it. The form factor of each device naturally suggests its best use: phones are good at quick text input and voice notes; tablets excel at reading and drawing; desktops handle complex knowledge work.
The approach also reduces the "I need all my tools everywhere" anxiety. You don't. You need the right tools in the right place at the right time.
Open Questions
- How do you handle situations that cross device boundaries (e.g., reading something on your tablet that sparks a note that needs desktop-level linking)?
- Does device role design work for people with only one or two devices?
- How should sync strategies adapt to device roles?
References
- Mike Schmitz on intentional device workflows for PKM