It reads like Supernotes wants to avoid large storage headaches for itself and instead push users to include links to customer-hosted, cloud storage. Understandable. Makes it easier for Supernotes, certainly. At a minimum, it feels like some connective tissue is missing to make that work as a practical matter but more preferably, it seems this is missing an opportunity for Supernotes by not building native file storage within cards.
To expound on the issue: Let’s imagine I used Google Drive to store these files. File formats could be all over the map, as expected (but PDF’s are included within the concept, certainly). By pasting in a sharable link within Supernotes cards, it causes two issues. The first is the bold assumptions made about the shareability offered by that third party cloud. I used the example of Google Drive. I have to be logged in as the Google user which I targeted for that file to be shared with (or as the owner of the file) or I have to be comfortable with the file being visible to the internet as “hidden” link (which is not hidden from anyone - just hard to guess). The second issue is that this whole house of cards falls down with login prompts, apps launching, file sharing rights, it’s a nightmare. The usability and scalability of using third party file sharing is poor at best. This doesn’t even begin to touch on the additional problem of searchability.
Seems to me that at a minimum, Supernotes either needs to build a whole cadre of plugins or connectors so that these links you encourage, pointing to third party file hosting providers - can at least be launched from within Supernotes to smooth out usability ‘bumps’. More preferably, I would encourage Supernotes to ‘bite the bullet’ and develop support for embedding files within notes/cards natively and monetize that as an add on feature. This is the opportunity for Supernotes.