This looks like a cool project. Here's a bit of feedback / thoughts I'm having related to a similar project, Archivy [0].
The problem I have with these type of solutions is basically the time it takes to just quickly bookmark. Browsers bookmarks are built-in, and do this pretty well - it's just one button next to the search bar.
Solutions like these are a bit more limited as they aren't embedded into your browser UI, so you have to open a new website and paste the link in. This mere effort adds a layer of complexity which can kind of turn the user off to bookmarking.
I wonder how this issue can be solved, in my project and yours... Maybe browser extensions can provide a more native experience with less "content to bookmark" time spent.
Sync is another way to kind of counteract this -> people use normal browser bookmarks or whatever they prefer - and then there are options to sync them to your software for better organization / whatever your functionality is.
However, hand-coding all of these integrations is difficult and that's why building a framework of plugins [1] so users can work and distribute these integrations themselves, is in my opinion, essential.
Thank you so much for the input! Indeed, the process of bookmarking can be improved a lot. Browser extensions could be a proper solution, but I wanted to publish the app without having to build the extensions for various browsers. That's why there is a bookmarklet. Will take a look into the plugins, maybe they can help making this easier.
+1 to the Bookmarklet, it's what I use now for another service and it's simple and works (and can be hotkeyed in most browsers); I suspect the GP did not find the docs with the bookmarklet option as it's on the User Settings page, not the Links page: https://www.linkace.org/docs/v1/configuration/user-settings/
bookmarklets are great, specially for a first version. I actually would usually prefer a bookmarklet if it wasn't for a lack of keyboard shortcut.
I use raindrop.io and notion, and before seeing the shortcuts, I didn't use them much. It was also kind of the reason why all my previous tentatives to use a cloud bookmark service didn't go well.
The second reason is how accessible it is to click on a bookmark. On the browser you have the bookmarks bar, so at least for your top bookmarks, there's no way to beat it. But for everything else, as long as I can setup the page as my new tab page - or the extension having a shortcut to open the full page - it's also great
Wallabag [0] may do what you require, with regard to having a browser extension to reduce friction when saving something. There's a bit of friction in getting the browser extension set up, but once you do so, it's there as a status bar button - click to save. Simple! On mobile, it becomes a "share destination" for iOS or Android.
normally you could also just create a bookmarklet and create a window for management within the page (all pages, where you can do bookmarks sensibly should support that)
I developed a solution which worked pretty well and monitored my clipoard.
When I Ctrl-X the url from the browser and then clicked on "new bookmark" link on my app, it magically appear.
You can also develop a small bookmarklet to do the same trick.
It was called http://daitanmarks.sourceforge.net/
> Solutions like these are a bit more limited as they aren't embedded into your browser UI, so you have to open a new website and paste the link in. This mere effort adds a layer of complexity which can kind of turn the user off to bookmarking.
That assumes the main goal is quantity of bookmarks. That you want to lower the cost of bookmarking as close to zero as possible. As someone that has been using bookmarks in the browser since the very early days of the WWW, I can't endorse that system for most bookmarks. The more important thing is to make it easy to add metadata, store the links, and then query/browse the information. A low-resistance system is simply opening the link in a new tab, and then when you decide it's time to clean up your tabs, you store them inside a system that holds the metadata necessary to make use of those links in the future. Everything is secondary to getting the metadata right.
> The problem I have with these type of solutions is basically the time it takes to just quickly bookmark.
This is a significant issue. I've been thinking of making my own bookmark storage/sorting thing as others didn't quite match my exact needs/preferences. But a key problem that I have, which I don't think I'm unique in, is that I'm often too lazy to even bookmark - I just open things in new tabs and leave them there until I get around to going back or forget the relevance and close a pile of windows/tabs to save memory...
> The problem I have with these type of solutions is basically the time it takes to just quickly bookmark.
You can write a browser extension to do this relatively easily. Mine is maybe ~200 lines of ES6 with login, bookmark-on-click, and ability to update with description + tags after.
I might also try a Bookmarklet that uses JS to send the page info over.
Edit: Looks like this is already included in ops solution.
I like bookmarklets because they are nice and simple, maintenance is much easier than a bunch of extensions, and extensions don't work in some browsers (i.e. mobile).
I made a thing like this for myself for fun, and I created a bookmarklet and hooked it up to Twilio so I can text URLs to automatically add links. Not sharing my project on here since it doesn't have authentication haha.
My solution is to use browser bookmarks as my inbox and my own yaml-based tool for archiving links only. For me, only a few links are actually worth keeping long-term.
The problem I have with these type of solutions is basically the time it takes to just quickly bookmark. Browsers bookmarks are built-in, and do this pretty well - it's just one button next to the search bar.
Solutions like these are a bit more limited as they aren't embedded into your browser UI, so you have to open a new website and paste the link in. This mere effort adds a layer of complexity which can kind of turn the user off to bookmarking.
I wonder how this issue can be solved, in my project and yours... Maybe browser extensions can provide a more native experience with less "content to bookmark" time spent.
Sync is another way to kind of counteract this -> people use normal browser bookmarks or whatever they prefer - and then there are options to sync them to your software for better organization / whatever your functionality is.
However, hand-coding all of these integrations is difficult and that's why building a framework of plugins [1] so users can work and distribute these integrations themselves, is in my opinion, essential.
[0]: https://archivy.github.io [1]: https://archivy.github.io/plugins