I have always wanted a web browser with tmux/iterm2 style tabs/panes, as well as the ability to save the window configuration and tab contents to a file that can be checked in to projects and loaded.
Load all of your project's documentation links, local development browser tools (database viewers, etc.) into a set of views that can be source controlled with the project. Don't force people to use their daily driver browsers for this, or hack side-by-side views together with their OS window managers. Zen and friends have split panes, but it's not the robust tab/panel system that I wanted.
There is a simple tab widget system, which so far has:
- Viewport manager: basically 1:1 with what is in Chrome devtools
- Session manager: create and manage browser sessions as a first-class entity, and attach/detach tabs to these sessions. Includes a simple "incognito" toggle as well.
- System light/dark override: stop flipping this on/off for your whole OS to test "system" light/dark mode (tedious)
- Reload trigger: pick a target tab. if that tab reloads, so does this one.
- Log file viewer: if the tab source is a local file, change the tab's view to a structured log file parser with search/filter, play/pause, etc.
- Screenshot/Video capture: not built yet. pretty self explanatory.
Great keyboard controls are a hard requirement for me. It's a little tricky since content in web views can capture this too, so I have a global "nav mode toggle" you enter to move around between panes and the tabs within them. Actively figuring out the correct UX, but I am liking what I have so far.
Toying with the idea of a "tab link" which allows you to store a set of "source" tabs in a view, but create "links" in other views, where the navigation is synced across all instances. Useful if you want to have, say, the Tailwind docs open to a specific page, but have that page shared across different views. For example, if you want to have one view specifically for mobile view work and another for desktop view work, and not have to manually navigate to the same Tailwind docs page in both views.
I'm honestly just using it as I work on another real project, and adding features as I think "hey wouldn't this be nice?" Which is a pretty fun and satisfying process. I don't have it published yet, because I'm not entirely sure if it's worth sharing at the moment, but I feel like I'll discover that along the way here and go from there. Maybe someone here will chime in :P
Load all of your project's documentation links, local development browser tools (database viewers, etc.) into a set of views that can be source controlled with the project. Don't force people to use their daily driver browsers for this, or hack side-by-side views together with their OS window managers. Zen and friends have split panes, but it's not the robust tab/panel system that I wanted.
There is a simple tab widget system, which so far has:
- Viewport manager: basically 1:1 with what is in Chrome devtools
- Session manager: create and manage browser sessions as a first-class entity, and attach/detach tabs to these sessions. Includes a simple "incognito" toggle as well.
- System light/dark override: stop flipping this on/off for your whole OS to test "system" light/dark mode (tedious)
- Reload trigger: pick a target tab. if that tab reloads, so does this one.
- Log file viewer: if the tab source is a local file, change the tab's view to a structured log file parser with search/filter, play/pause, etc.
- Screenshot/Video capture: not built yet. pretty self explanatory.
Great keyboard controls are a hard requirement for me. It's a little tricky since content in web views can capture this too, so I have a global "nav mode toggle" you enter to move around between panes and the tabs within them. Actively figuring out the correct UX, but I am liking what I have so far.
Toying with the idea of a "tab link" which allows you to store a set of "source" tabs in a view, but create "links" in other views, where the navigation is synced across all instances. Useful if you want to have, say, the Tailwind docs open to a specific page, but have that page shared across different views. For example, if you want to have one view specifically for mobile view work and another for desktop view work, and not have to manually navigate to the same Tailwind docs page in both views.
I'm honestly just using it as I work on another real project, and adding features as I think "hey wouldn't this be nice?" Which is a pretty fun and satisfying process. I don't have it published yet, because I'm not entirely sure if it's worth sharing at the moment, but I feel like I'll discover that along the way here and go from there. Maybe someone here will chime in :P
Everything's made up and the points don't matter.
meet.hn/city/39.4064662,-105.4717013/Bailey