For a couple of reasons: 1. It's how I want to use the app, 2. it's the easiest way to support all platforms, 3. I am most familiar with web apps.

In short: Managing and consuming PDFs seamlessly on multiple devices. You can continue reading on your mobile device were you stopped reading on your laptop. I started implementing the app as there was no other app that satisfied my requirements:

• Complete control over my data.
• Easy to self-host via docker.
• Lightweight and minimal, should run on cheap hardware
• Continue reading where you left off on all devices
• Browser based
• Support single sign on via OIDC in order to leverage an existing identity provider
• PDFs should be shareable with an external audience with optional access control
• Open source
• Content should not be curated by an admin instead every user should be able to upload PDFs via the UI

Surprisingly, there was no solution available that could do this. In the following I’ll list the available alternatives and how they compare to my requirements.

Yes, I was also surprised they selected PdfDing as I thought it would be a bit to niche. In PdfDing's case it's a single grant. There is a project plan and once a task is completed the corresponding payment can be requested.

The naming and at the beginning the design as well were heavily inspired by the below mentioned linkding. The name is quite easy to remember and unique which is good for search results.

If mozilla's pdf.js is used for PdfDing's viewer. If this functionality would be added to the library then yes.