I am building my "dream tool" too, a cross-device roaming profile-experience context-focused UI. Many, many iterations that go back maybe 15y, even built a custom linux distro (iolinux) back in the day(ro root, containerized user-spac with composer-like app handling). Always worked on side-projects, consulting gigs or one-off implementations, often times across multiple customer-devices. Switching context is damn expensive, hence tried to build a tool to help with that. Always failed on the UI parts - native linux tooling was just awful. What do you specifically mean by "context" you ask? Well, you get a call, switch to work on `work://customer-foo/project-bar/task-baz`, every bound device / tool / application loads data related to that task (your filesystem mount shows relevant files, browser loads relevant tabs, obsidian relevant notes etc). Building my own small db engine to accommodate that use-case, getting more fun working on it every day
Reminds me a bit of qubes OS with different motivation.
This is awesome. I always have imagined my computer being well, my desk. So far I have to live with a bunch of i3 screens I name after whatever I'm working on. I'd love to be able to page through the bench to flip to a task. Unfortunately with apps going so mono-windowed (slack, etc) it's harder to do. If I could just say have my slack window for this client, with their docs, proposals, database, whatever up, that'd be sick. I love the idea thank you. good luckl
Hey - spent a lot of time in this world (solution / sales engineer, technical account manager to many clients), and thinking about this same problem.
Even experimented with per-client Linux users. Per-client calendars & routines. Per client knowledge-base, etc
Very curious to see what you come up with.