Hi Michael, and welcome to the community!
Just sayin’ … if you name this feature “Attachment Annotations” and promote it for “any type of visual asset” but then only deliver this capability for certain types of attachments, it may come as a surprise to users, and above all, software teams need to mitigate surprises because users don’t like to be surprised unless it’s a magically smart surprise. This is the opposite of a magically smart surprise.
I understand why it’s not as easy to annotate PDF documents, but this is [yet again] one of those instances where Airtable has half-baked a feature. Is a PDF document not a “visual asset”? And it’s not just the lack of PDF support; consider the annotations themselves; no access via the API, and lacking this, we can’t even add PDF annotation support separately.
Oddly, there is a well-defined specification for adding annotations to PDF documents (without changing the document itself) and a vast collection of open-source libraries to choose from. While images do sometimes flow through workflows and approval processes, I have a hunch that PDFs are just as important in the conversations and workflows for business content.
Surely, we can all agree that there are fringe attachment cases. Would we expect it to work for JSON documents? Probably not. But for PDFs? Hmmm, there are about 2.5 trillion of them. Do they matter? More importantly, do conversations about PDF documents matter greatly? I think so. Airtable opened Pandora’s box with attachments. Now it must be prepared to fully bake the idea.
There is no world in which PDF annotations should not be in your immediate plans and should have been in this plan.