nip

> If the market is filled with cheap products and a clone of your product can be easily made, then the survival of the business is in positioning, marketing, packaging the product, distribution, sales...

Most people stop after having gotten their dopamine hit. It was the case before, it's still the case now with AI.

Try any newly released software, and you'll notice a trove of issues, whether it's UX, UI, features not working properly. Errors, etc. All of the unsexy work that is needed to go from "it works" to "thousands / millions of people can rely on it daily".

Playing the long game has always worked, and will always work.

There are two ways forward for any company (whether big or small):

- Expand the pie: push AI to its limits while keeping your employees, new markets, new offerings

- Keep the same pie, and increase the size of the slices among the shareholders (employees or not)

Multiple ways:

- Cold outreach (rapidly becoming impossible with the amount of unhinged automation pouring over LinkedIn)

- Engaging on the posts with my "takes", not selling anything, just genuinely helping / contributing

- Warm connections that I've made, for me it's attending work fairs / conferences then connecting on LinkedIn

- Posting as myself (the founder): AI-assisted engineering, industry takes, etc

For some of us (founders, sales, GTM engineers), LinkedIn is "the place to be" if you want to find and engage with prospects.

My customers are in healthcare, and they don't hang out on X for example (which is where I get most of my tech news alongside HN).

Most people randomly accept invitations on LinkedIn: "We're both humans, so I felt we should connect!".

But if you actively prune / curate WHO you add to your LinkedIn, you end up with a feed that is genuinely useful.

What you do need to know is WHY you want to use LinkedIn. It could be to find your next job, finding potential customers, or just keeping up to date with <INDUSTRY>.

> like that, but (and I might be ignorant) can't you just change it's all in browser to something else and the users would be oblivious?

Excellent question! The answer is simple: we're known on the market, and trusted by our customer for this secure handling of PDFs. Should we decide to change that (unbeknownst to them), we would effectively kill our reputation and the company by extension.

> Is it possible to download as an app and disable internet (not sure if it's a feature of any browsers).

Back in the days, SimplePDF used to work offline. However maintaining that in conjunction with our paid customers features (where the online connectivity is mandatory) was too big of a maintenance burden. We decided a year ago to drop this support (silently), and no one has complained since then, confirming our hunch that it is not a high-demand feature.

Thanks! We have plans to improve it further (file support), possibly also voice, but for now in the backlog!

And if you’re French, don’t worry, you didn’t miss it.

It’s the 31st of May

Thanks! You caught a real bug: the form labels fed to the LLM were mangled. Now fixed: values land in the correct field.

On "what are we trying to solve":

Forms (PDFs, scanned paper) are still everywhere and aren't going away. SimplePDF Copilot exists to make the transition less painful. A few concrete use cases:

- Pre-filling repetitive forms from existing data sources (CRM, EHR, etc. via MCP/RAG). In most industries, employees fill forms by copy-pasting or retyping. With AI + tool calling, most of the form arrives pre-filled and the employee just corrects or adds the missing bits.

- Filling foreign-language forms. If you've moved to a new country, or know someone who has, you've had to fill out forms in a language you don't master.

- Understanding a contract before signing it. "Can I actually trust all the clauses here?" Reading proficiency changed the world by giving people a way to understand what they were signing. This extends it to legalese and odd clauses.

On Claude Cowork:

Different shape, and a different privacy model. Cowork drives a sandboxed virtual desktop: you can't see exactly what it's doing while it fills, and correcting a wrong value means another back-and-forth with the LLM.

Copilot works inside your editor: every change is visible as it happens, you can amend any field with one click, and the document never leaves your browser + it's LLM agnostic: bring your own (local or hosted).

Absolutely not insulting! In fact an excellent question!

Preview was an inspiration when I started SimplePDF, my goal was to make the "Preview" of the web, so that people without a Mac would benefit from a software matching Preview in ease of use and overall polish.

Adobe Acrobat: SimplePDF has "Simple" in the name as the philosophy is to keep it simple (both in ease of use, and features): I don't intend to support everything that Adobe Acrobat does. There's a lot of features that I could build that I intentionally do not, as they would bloat the UI and hard the overall usability. Most people have very simple needs and don't need advanced features (like scripting, etc).

It already does! More specifically, SimplePDF supports "WebMCP": the tools that the LLM is using are exposed as WebMCP tools

We offer both:

- A privacy-focused PDF editor, free for individuals, used by 200k users monthly: https://simplepdf.com/editor

- The same editor, embeddable into one’s app for companies, with the same privacy guarantees (everything happens in the browser) + the resulting PDF is stored in their own storage (« bring your own storage »).

The majority of our paid customers are in healthcare where privacy is non-negotiable. Co-pilot extends that to the AI world (« bring your own AI »)

What are you using the PDF editor for?

I was not able to reproduce it, so I made a small video, hopefully I better understand your problem once you've seen it: https://cdn.simplepdf.com/simple-pdf/assets/hn-reply-tyingq....

In the video I let the chat fill my name, then have it skip the second field (business), then fill LLC, it makes a mistake and I correct it

Have you tried telling the LLM to just skip the field and move to the next one?

I tried with various: "Skip it", "None, leave blank", "Skip this field" and all worked for me, but if may very well be missing something very obvious?

Hey Kiney!

It supports AcroForms (like in the example) but not XFA.

Why are you asking? gov forms support?

Thanks!

Anything you see missing in Copilot to achieve that?

Not sure if you noticed, but there's an arch-diagram in the info popup [1].

[1] https://copilot.simplepdf.com/?share=a7d00ad073c75a75d493228...

I tried to make it clear with the popup message that appears when you start chatting: "Public demo. Use sample data only. Messages are processed by the selected AI provider."

But you're right that it's not as evident as I wanted to, I'm making a small copy update to make it clearer: "Public demo. Your chat messages leave your device and are sent to the selected AI provider. Use sample data only."

(Since there's support for local models, the popup is only displayed when NOT using your own model)

Thanks!

EDIT: the copy update is live, thanks again!

Just to be clear, this is a technical demo showing what's possible with client-side tool calling + local models: LLM-assisted form filling where no document data has to leave the user's machine.

Use cases range from:

- Filling foreign-language forms

- Navigating a contract before signing: "can I trust ALL the clauses here?"

- Pre-filling repetitive forms from existing data sources (CRM, EHR, etc. via MCP/RAG)

Copilot is designed to be embedded; our customers ship it white-labeled inside their own products.

Just to be clear, this is a technical demo showing what's possible with client-side tool calling + local models: LLM-assisted form filling where no document data has to leave the user's machine.

Use cases range from:

- Filling foreign-language forms

- Navigating a contract before signing: "can I trust ALL the clauses here?"

- Pre-filling repetitive forms from existing data sources (CRM, EHR, etc. via MCP/RAG)

Copilot is designed to be embedded; our customers ship it white-labeled inside their own products.

Very likely, but you don’t need to be so aggressive and dismissive.

Anyone who has achieved “distribution” knows. Anyone else is just lacking experience.

Answering like you did is akin to gatekeeping. The world is better with more builders. We should encourage anyone who wants to give it a shot

I was approached twice to add « a search and tracking script » to my 35k+ user-based extension.

Now I know what would have happened if I had accepted.

Agree on Smart-ID but the answer is to fix those flaws, not to replace the entire approach with one that depends on Google Play Integrity verdicts that even the German architects admit they can’t fully trust.

SIM-based solutions on their way out is a non-issue. For eSIM to support that use case, political will only is needed: the EU got Apple to abandon the lightning cable, this is not any different.

It is, mandated by the EU commission.

Instead they could have mandated the use of eIDAS 1 to all countries + extend it with attribute/credential support, and let countries choose their implementation (cards, SIM, server-side).

Instead we’re back to the drawing board with the big shortcomings highlighted in this thread.

I’m sorry to lash out at you but I keep getting disappointed in European countries (more precisely the ever disappointing EU commission) all suffering of the NIH syndrome instead of collaborating and learning from each other

In light of all of these shortcomings with platform attestation, why go with the eIDAS 2 wallet approach at all? eIDAS 1 already solved this with Mobile-ID (SIM-based, no Google/Apple dependency) and Smart-ID (server-side key management with minimal platform reliance). What does the wallet model give you that justifies this level of dependency on two American corporations’ proprietary backends?

Especially considering that mobile-ID has been around since 2007.

The web was initially meant to be browsed by desktop computers.

Then came mobile phones with their small screens and touch control which forced the web to adapt: responsive design.

Now it’s the turn of agents that need to see and interact with websites.

Sure you could keep on feeding them html/js and have them write logic to interact with the page, just like you can open a website in desktop mode and still navigate it: but it’s clunky.

Don’t stop at the name “MCP” that is debased: it’s much bigger than that

The reason is simple: the TUI is the fastest way to provide any form of UI over the file system.

Want to do that with web technologies? You’ll need a browser AND a server or build an app using electron or tauri.