But the mockup they produced at the end seems to have several issues, at least when it comes to compatibility with my bookmarking habits. I wonder how they plan to address these issues:
1. Only a single level of hierarchy. There's a "pile" for "school work", but what about having sub-piles for each course that I'm taking? I don't want bookmarks for my CS course getting mixed up with bookmarks for my political science course.
2. Can I toss the same bookmark in more than one pile at the same time? The neat thing about tagging is that tags are many-to-many. The concept of piles seems to be a reversion to folders. Don't get me wrong, folders are cool, too. But they have the annoying limitation of being one-to-many.
3. Relying on screenshots and/or favicons instead of page titles to represent each bookmark would quickly get confusing when you bookmark multiple pages from the same website. Can you tell one NYT article from another from 120px thumbnails of each page? (Hopefully, those buttons in the top right are for toggling between icon and list view.)
4. What if I have 10,000 bookmarks? Is your idea highly scalable (pardon the buzzword), or is it optimized for ~200 bookmarks?
All of these nitpicks stem from the fact that a bookmark manager should not only help you save pages for later, but also help you manage the pages that you've saved. Here's the question: Does your product facilitate saving and organizing methods that allow the user to retrieve any page within 5 seconds, 5 years later? Because I do occasionally revisit pages after a decade or even more, after I've accumulated thousands of other bookmarks ranging from "read this afternoon" to "potentially useful to a future project".
But the mockup they produced at the end seems to have several issues, at least when it comes to compatibility with my bookmarking habits. I wonder how they plan to address these issues:
1. Only a single level of hierarchy. There's a "pile" for "school work", but what about having sub-piles for each course that I'm taking? I don't want bookmarks for my CS course getting mixed up with bookmarks for my political science course.
2. Can I toss the same bookmark in more than one pile at the same time? The neat thing about tagging is that tags are many-to-many. The concept of piles seems to be a reversion to folders. Don't get me wrong, folders are cool, too. But they have the annoying limitation of being one-to-many.
3. Relying on screenshots and/or favicons instead of page titles to represent each bookmark would quickly get confusing when you bookmark multiple pages from the same website. Can you tell one NYT article from another from 120px thumbnails of each page? (Hopefully, those buttons in the top right are for toggling between icon and list view.)
4. What if I have 10,000 bookmarks? Is your idea highly scalable (pardon the buzzword), or is it optimized for ~200 bookmarks?
All of these nitpicks stem from the fact that a bookmark manager should not only help you save pages for later, but also help you manage the pages that you've saved. Here's the question: Does your product facilitate saving and organizing methods that allow the user to retrieve any page within 5 seconds, 5 years later? Because I do occasionally revisit pages after a decade or even more, after I've accumulated thousands of other bookmarks ranging from "read this afternoon" to "potentially useful to a future project".