What's coming, what's being thought about, and what isn't.

What is being built now

Decided, in development. Coming in upcoming versions.

• OCR support for scanned PDFs. Today text anchoring only works on PDFs with a text layer. For scanned documents (no selectable text) an OCR layer running in the browser is on the way.
• Saved templates. Right now signature position and configuration are set every session. The next version will let you save named templates ("Payslips", "Client certificates") to reuse in one click.
• Batch report. After signing a batch, you'll be able to download a CSV with which file was signed, when, and where the signature landed. Useful for internal audit trails.

What is being thought about

No commitment. Pending decision on whether it fits the project.

• Desktop version. An Electron or Tauri app for fully offline processing. Pending decision on whether it adds enough value over the current web version, which is already local.
• Drive integrations. Read PDFs directly from Google Drive, Dropbox or OneDrive without downloading them first. The challenge: keeping the principle that files don't leave the browser. Drives would only serve as direct input — nothing would be uploaded to a Fdo. server.
• Better mobile UX. Precise placement with a finger is the weak point on mobile. Possible paths: a zoom tooltip, magnetic snapping to the detected box, or a simplified small-screen view.
• Multi-signer combinations. Some documents need two signatures (responsible + reviewer). Today you have to run the batch twice. A simultaneous double-signing version is under consideration.

What is not coming

So you know what to expect.

• A server that processes your files. That would break the principle that defines Fdo. If a SaaS version ever exists, it would be a separate product, not this same tool.
• User accounts and login. The flow doesn't need them. Your signature is stored in the browser if you choose; that's enough.
• Qualified electronic signature with a digital certificate. That's what national e-signature tools do, and they do it well. Fdo. covers simple signature in batches, not qualified signature.
• Newsletter, cookie banner, email popup, affiliate programme. None of these fit a tool offered as a tool. The only way to follow new releases is the RSS feed.
• Tracking, analytics, telemetry. We don't want to know what you sign. That's a big part of the value of the tool.

Missing something?

This list is partly built from feedback from people using Fdo. day to day. If you have a concrete need — a real use case, not a generic idea — write to hola@fdo.app.