I've been working on SimplePDF to solve a problem I encounter weekly: filling out non-editable PDFs [2] that I'm confident other people have already had to fill themselves [3]
---
# So what does SimplePDF do, that other services don't?
- You get to try the product right away and see for yourself, no signup process, popups, email to give away
- The documents you load, edit, fill never see the light of my server, everything is processed locally – no remote uploading anything. This includes the PDF generation.
- There are no analytics / third party tracking your every move (I do collect usage data, but it's fully anonymous and processed and stored on my server): therefore no annoying cookie banner. You can read more on the Privacy Policy [5]
- If someone before you has filled the same document, upon opening it you'll see fields already set, you can try out with [3] or [4]: load them with simplePDF and you'll see the fields appear.
---
# How does SimplePDF do this field matching thing?
When a document is loaded in your browser, a fingerprint of the document binary is made, and sent to the server. The document table consists of: document_id, fingerprint and created_at.
As soon as you start editing a document, a template is created, containing metadata about the fields (x, y, width, height, type of field, background color...) that is then tied to this document you created. Once you save, this template gets sent to the server. The template table consists of: template_id, document_id, fields (the metadata) as well as created_by_customer_id if you're a customer.
As a result, someone else on the other side of the world opening the same document will see the fields you positioned already there – you just saved them the 5min it probably took you to position them.
---
# What's the tech stack of SimplePDF?
- NextJS on the frontend
- Koa with GraphQL on the backend
- Postgres (Managed Database on Digital Ocean)
- A 10€ droplet on Digital Ocean
---
If you have any questions, comments or feedback, please let me know!
I like to believe that I'm a good product engineer, but I suck big times at marketing and sales:
if you have any feedback on that front, I'll be extremely happy to hear it (and I'm a long time HN user, so I'm "ready" for your feedback)
1 comment
[ 2.3 ms ] story [ 16.5 ms ] threadI've been working on SimplePDF to solve a problem I encounter weekly: filling out non-editable PDFs [2] that I'm confident other people have already had to fill themselves [3]
---
# So what does SimplePDF do, that other services don't?
- You get to try the product right away and see for yourself, no signup process, popups, email to give away
- The documents you load, edit, fill never see the light of my server, everything is processed locally – no remote uploading anything. This includes the PDF generation.
- There are no analytics / third party tracking your every move (I do collect usage data, but it's fully anonymous and processed and stored on my server): therefore no annoying cookie banner. You can read more on the Privacy Policy [5]
- If someone before you has filled the same document, upon opening it you'll see fields already set, you can try out with [3] or [4]: load them with simplePDF and you'll see the fields appear.
---
# How does SimplePDF do this field matching thing?
When a document is loaded in your browser, a fingerprint of the document binary is made, and sent to the server. The document table consists of: document_id, fingerprint and created_at.
As soon as you start editing a document, a template is created, containing metadata about the fields (x, y, width, height, type of field, background color...) that is then tied to this document you created. Once you save, this template gets sent to the server. The template table consists of: template_id, document_id, fields (the metadata) as well as created_by_customer_id if you're a customer.
As a result, someone else on the other side of the world opening the same document will see the fields you positioned already there – you just saved them the 5min it probably took you to position them.
---
# What's the tech stack of SimplePDF?
- NextJS on the frontend
- Koa with GraphQL on the backend
- Postgres (Managed Database on Digital Ocean)
- A 10€ droplet on Digital Ocean
---
If you have any questions, comments or feedback, please let me know!
I like to believe that I'm a good product engineer, but I suck big times at marketing and sales:
if you have any feedback on that front, I'll be extremely happy to hear it (and I'm a long time HN user, so I'm "ready" for your feedback)
---
[1] https://simplePDF.eu
[2] The assignments my estonian teacher gives me are usually scanned documents that do not have any editable fields in them.
[3] The Model Release agreement of Shutterstock (https://ak.picdn.net/assets/cms/2e36c8b30913813b9e424f37ba0a...)
[4] Equifax's Employment Data Freeze Placement Form (https://assets.equifax.com/wfs/theworknumber/assets/twn_Empl...)
[5] https://www.simplepdf.eu/privacy_policy