Thank you for your comment. Yes, it is possible to import via ISBN scan. Currently, there are three ways to add a book:

- searching (which uses the Google Books API under the hood)

- manual addition (which nobody wants to do — I completely understand — but is the only option for old books that cannot be found online; I have a lot of these)

- scanning the ISBN (which also uses the Google Books API).

I'll certainly consider the labelling feature and add it to the backlog.

Thank you for your comment and for raising the issues.

When you set the book status to 'Read', an edit pen appears to the right of it (in the same area where you set the status), which you can click to edit the start and finish dates. Please note that when you set the status to 'Read', it's assumed that you've read the whole book, and this is added to the 'Pages read this month' statistic. Conversely, when you set the status to 'DNF' (Did Not Finish), you can set start and end dates again using the edit pen, as well as providing a progress update, i.e. how many pages you read before stopping.

I've been dedicating my time after work to this project for several months already, and I plan to continue doing so for a long time. I'm going to use it a lot personally too, so that's a big part of my motivation, to be honest.

There's actually. Currently there are three methods of adding a book:

- searching (which uses the Google Books API under the hood)

- manual addition (which nobody wants to do — I completely understand — but is the only option for old books that cannot be found online; I have a lot of these)

- scanning the ISBN (which also uses the Google Books API).

Thank you for your comment. The text on the dark mode page at https://app.librari.io/subscription should now be fixed. Thank you for pointing that out.

I plan to suggest a freemium tier and two affordable paid plans. However, as it's still in beta, it's a bit soon to provide any specifics, to be honest — I still need to figure those out, too!

Regarding the bulk import, yes, that's in my backlog and will start working on that soon.

Indeed, librari.io is designed for managing physical books. Moreover, if calibre was intended for managing not only ebooks, I would personally prefer to use google sheets because calibre's outdated UI is sufficient reason for me not to use it, although it may still be functional.

Calibre is very customisable. You can pretty much change everything about the UI.

Thank you for your comment. Yes, the ability to extract from a picture is something that many people would also like to see, as well as you. I'll definitely think about this and add it to my backlog.

looking forward to the feature! I tried the product but as of now it's too much work for me to migrate and enter each book one-by-one, especially since I don't have a digital file containing the log.

Thank you very much for this detailed comment — it is indeed very useful to me. The import feature is certainly on my radar and is something that I'll start developing very soon. You're absolutely right that it would make onboarding a large collection really easy. I'll take note of the other features you mentioned too. Thank you again!

Thank you for the comment. librari.io already uses OpenLibrary for metadata enrichment, but I'll definitely check out the others too. I'll definitely check out Colibri — thank you for sharing!

Likewise! The space of book-lover software is small, we should stick together :)

Yes, I can certainly be open and provide a lot of detail. The landing page is a standard Next.js application hosted on Vercel. The web app itself is a React app that uses Shadcn, Tailwind CSS and TanStack/React-Query, and the backend is a Node.js application. I use PostgreSQL and Redis instances to store data in the long and short term, respectively. For deployment, I use Dokploy, which is an excellent way of deploying stuff in containers and making them communicate with each other (and actually this is my first time that I use it). You can self-host it on a VPS, which is what I do. Finally, I use AWS S3 for object storage and backups.

I would definitely use this tech stack again if I were to start again. The only thing that may change in the future, when there's a lot of traffic, is how the app is served and hosted overall. Currently, it's on a VPS, but depending on the traffic volume, it would make sense to switch to AWS infra (e.g. using lambdas etc) at some point in the future.

Thank you for your comment and for explaining your problem in such detail. Currently, you can mark your library as public and share the link with others, but they can only see the books in it. What you're saying actually makes total sense, and I will add this feature to my backlog.