Our Products

iDoc

A manual builder that retouches screenshots in the app, pins numbered steps onto them, and publishes something that reads on the web and prints correctly.

The situation

Everyone agrees a manual is needed, and the manual is the first thing to rot. Screenshots are retouched in Photoshop before upload, so when one button on the screen changes, fixing it starts with finding the source file — usually on the laptop of someone who has left.

The second failure is a manual that looks right on screen and falls apart on paper: figures cut in half, headings stranded at the foot of a page, and a table of contents whose page numbers stopped being true some time ago.

And when a client asks which version of the manual they are actually holding, there is often no answer, because the file that was sent and the page that was last edited parted ways long ago.

How it works

An uploaded screenshot is kept untouched. Every adjustment — crop, brightness, spotlight, highlight box — is stored as instructions and drawn at render time, so any of it can be changed later. Nothing is ever baked into the pixels.

Several screenshots can be composed into one figure, with numbered pins placed where they belong and a description for each. Positions are stored as proportions rather than pixels, so one stored value is correct as a thumbnail, as a full-width figure, and on a printed sheet.

Publishing freezes the whole manual into an immutable version. A client's link always serves the current one, and each version keeps a permanent address for reference. A manual that should not be open to everyone takes a password — and that password covers the screenshots too, not just the page around them.

What changes

  • Figures stay editable for the life of the manual, with no source file to hunt for
  • What is read on screen and what comes out of the printer are the same pages
  • Which version a client is using is a question with an answer
  • Each client's manual is separately locked; unlocking one opens nothing else

Who it is for

  • Teams delivering systems to corporate clients, manual included
  • Work that must ship both a file and something readable online
  • Products whose screens change faster than the documentation
  • Organisations that must control who can open which manual

What it connects to

  • Reads in any browser, phone or desktop
  • Prints from the browser, with cover and contents generated automatically
  • Exports for assembly into a Word deliverable in the house document format
  • Per-manual passwords, covering the screenshots as well as the pages