Technical explainers on capture architecture, self-hosting and software training. Written to be useful whichever product you end up buying. There is enough marketing about this category already.
Step by step for browser-based apps and Windows programs: one task per demo, tooltips for new hires, and updating only what changed.
Two architectures, and what each one actually produces for selectable text, scaling, ageing and maintenance cost.
Why a browser app can be captured as markup and a Windows app cannot, and everything that follows from that.
Pacing, maintenance, searchable text and embedding, plus the cases where a video is simply the better tool.
Four things vendors call self-hosting, only one of which survives cancelling the contract. With the questions to ask.
A working method for training people on a system you cannot give them access to.
The path a capture takes through your own browser session and a local editor, and exactly what leaves the machine.
Announcement: a Navattic alternative that exports each demo as one self-contained HTML file for your own intranet, LMS or web server.
Capture a workflow from an application you actually use and see what comes out the other end.
Request trial