Raindrop is great! Its written by one guy and the polish / quality of his work is top notch.

Our roadmap is going to bring us in a different direction than Raindrop, but more details on that later.

Can you elaborate on how you will be better or in what ways you are already better ?

I don't want to claim that Linkidex is better than Raindrop. Raindrop and Linkidex will serve different audiences. That said, we aren't quite ready to share our long term roadmap.

1) sharing is on our roadmap and core to our long term value proposition.

2) That is a great idea. Right now we default the title to the URL if a user doesn't input a title. Your suggestion is superior, will look into this.

3) This is something we have considered, but isn't currently on our road map. Right now we are looking at making Linkidex a great productivity tool as opposed to yet another social network.

100% agree. A browser extension is on our roadmap.

The database is PostgreSQL.

We are using Material UI (https://mui.com/material-ui/getting-started/overview/) on the front end which is what makes the website responsive and mobile friendly. MUI has been great to work with, I highly recommend it.

The Progressive Web App part of things (https://developer.mozilla.org/en-US/docs/Web/Progressive_web...) is what makes Linkidex still mostly work if your internet goes down, and lets users "download" the front end web application to their phone so it behaves like a native mobile app would. For example, users who download Linkidex get an icon on their home screen that opens Linkidex, and the url bar isn't visible when the app is open, despite the downloaded app just being a web page thats opened with your phone's default browser.

Awesome, material UI does look nice.

How is it you can use postgresql as database but your app still works offline? Been looking for a bookmarking app that works offline so that sounds cool

The front end app maintains its own state. The front end fetches all of a given users links when it loads and stores them in application state (memory within the front end application.) If you lose your internet connection, the front end will continue to use the links that it has in its application state.

This isn't how Linkidex works right now, but using Linkidex as an example, the front end could queue up tasks such as "create link abc", "delete link "bcd", and "edit link cde" when offline. Then when your device regains an internet connection, it could send all of its queued up tasks to the back end and reconcile the changes with the database. PWAs make this kind of thing possible, and fairly simple to implement.

I am a huge fan of "The net ninja" on YouTube, and he has a great tutorial on PWAs: https://www.youtube.com/watch?v=4XT23X0Fjfk Note this is 3 years old and front end stuff changes quickly so this may be slightly out of date, but I still recommend this video series. PWAs are awesome.

Edit:

To clarify about linkidex working offline, you can still search your links when offline, assuming you loaded your links before going offline. You can't create, edit, or delete anything though, and if you refresh the app it will fail to reload just like any other web page. Maybe its unfair for me to say it 'mostly' works offline. I'll do a better job communicating this in the future.

archivebox is neat. Also it looks like they have the option to backup links to Archive.org, which was mentioned in another comment too.

I hope it does!

It would be great if you could import open tabs.

What I really want/need is a tool that helps auto-categorize/group all my open tabs into areas of interest and enables full-text search across all of those pages so that I can context switch back into whatever I was working on at that time.

Manually bookmarking and tagging doesn't scale for me.

I don't think a web app can do this, but a browser extension, which is on our roadmap could!

Regarding auto-categorize, how would you want that to work? I imagine this could be a machine learning problem, but I wonder if there is a naive solution that solves most of the problem instead of just throwing ML at it?

Text search across pages has come up multiple times in this thread. I shall add it to our list of features to investigate.

I'm envisioning a number of categories that I can predefine or select as seed. I think Flipboard use to ask for a number of interest areas upon first use. Something like that.

I'm not always in favor of ML but I'd think this would be something ML would excel in.

Making the error reporting of import / export is very high on my todo list. Right now the user just has to wait and doesn't get feedback, which is a bad experience.

I see one import failed due to something on my side. I've identified the issue and have a fix, I'll follow up as soon as its deployed. Sorry for the inconvenience!

Yeah that may have been mine, no worries. Thanks!

Thanks for your patience on this! This issue has been fixed.

We haven't plugged into a phone's "share" functionality yet, great suggestion!

Using web.archive.org is a fantastic idea I had not considered. I wonder if its ok to use their API to serve 'saved' versions of a given site instead of storing it myself. I shall look into this!

by local storage / export, do you mean storing your URLs, or downloading the archived text versions of pages?