- General
-
Ideas
+2
Under review
Usability problems encountered by a new user
Thanks for a nice plugin. I've been trying to use it with Chrome for few weeks now (having switched from Firefox and Session Manager), but even though there are some great features here the workflow is not as smooth as with Session Manager.
1. Since all of the windows are shown in the tree equally the signal to noise ratio is very bad. Especially since the same window can show up in the tree many times due to the "Window (crashed...)" issue every time the browser is shut down. All of these windows overwhelm the actual saved ones, which should have the visual priority. I know it's possible to accomplish this with groups but IMHO it's too fidly. It's a safe assumption that if i named and saved a window i'd like to keep it for the future. So by default the named and saved windows should be displayed separately and more prominently than the other ones.
It could be implemented as a visual filters: Show named only, show "auto-saved only, show all.
2. "Collapse all" action is missing and is needed
3. Need better way to manage history. Session manager allows to set the number of auto-saved windows and discards the older ones once that limit is reached. TO keeps all of the old windows in the tree which gets crowded pretty quick. There needs to be a limit on the auto-saved windows and a manual action to delete them all.
4. The default window view mode should be collapsed not expanded. If a window has been saved a user can identify it by the name and can either open it without seeing the included tabs in the tree or explicitly expand that window to see the included tabs. If a windows was not saved the user will either browse by the date of the last browsing session for that window or will run a search for a tab name. Either way there's no need to automatically expand all of the auto-saved windows in the tree. These are the most frequent use cases.
I understand that TO follows a different metaphor but I think that Firefox's Session Manager has solved similar tab management problems in a useful and elegant way. Unfortunately it's not available on Chrome, which can be an opportunity for TO.
1. Since all of the windows are shown in the tree equally the signal to noise ratio is very bad. Especially since the same window can show up in the tree many times due to the "Window (crashed...)" issue every time the browser is shut down. All of these windows overwhelm the actual saved ones, which should have the visual priority. I know it's possible to accomplish this with groups but IMHO it's too fidly. It's a safe assumption that if i named and saved a window i'd like to keep it for the future. So by default the named and saved windows should be displayed separately and more prominently than the other ones.
It could be implemented as a visual filters: Show named only, show "auto-saved only, show all.
2. "Collapse all" action is missing and is needed
3. Need better way to manage history. Session manager allows to set the number of auto-saved windows and discards the older ones once that limit is reached. TO keeps all of the old windows in the tree which gets crowded pretty quick. There needs to be a limit on the auto-saved windows and a manual action to delete them all.
4. The default window view mode should be collapsed not expanded. If a window has been saved a user can identify it by the name and can either open it without seeing the included tabs in the tree or explicitly expand that window to see the included tabs. If a windows was not saved the user will either browse by the date of the last browsing session for that window or will run a search for a tab name. Either way there's no need to automatically expand all of the auto-saved windows in the tree. These are the most frequent use cases.
I understand that TO follows a different metaphor but I think that Firefox's Session Manager has solved similar tab management problems in a useful and elegant way. Unfortunately it's not available on Chrome, which can be an opportunity for TO.
0
Under review
vladyslav volovyk 9 years ago
Thanks for your review. Interesting points. Hope future versions will improve on some of them. for example some of the mentioned by you issues is a nasty result of the bug with incorrect crashed windows detection on Chrome close, and of course it's planned to be fixed.
Customer support service by UserEcho
