Interactive demo recording
Use any web app while Replayink records, press stop, and the share link is already on your clipboard. Whoever opens it watches it play like a video — then presses the buttons themselves. Nothing to install on their end.
That is the whole handoff. Whoever opens the link lands here with the recording
playing; once it is theirs, the link points at the step they are on — the same
#s= a real share link takes.
Not a slideshow of screenshots
Each screen is the real page — its HTML, its CSS, its fonts — without its JavaScript. What the app did after each press is recorded as it happened and played back at the same pace.
The honest limit: a replica runs none of the app's code, so what works is what was recorded. A button nobody pressed does nothing — and the player says so instead of pretending.
It started as an annotator
Nothing below is a mockup. Each panel is the feature running.
Drag across a sentence to highlight it, then drop a comment pin on it and start a thread. Replies stack under the mark they belong to, so the argument stays next to the claim instead of in a separate document.
Keys: H highlight · C comment
Every serious piece of software is used by someone who is about to be interrupted. The meeting starts in four minutes, the child needs collecting, the deploy is still red.
What matters far more than speed is whether a thing can be put down and picked back up without having to reconstruct where you were. That takes a marker: a way to point at one sentence and say this one, the claim I do not believe.
Anchoring to a pixel position fails on the first reflow. Anchoring to an element fails the first time the framework re-renders. Anchoring to the text itself survives nearly everything short of the sentence being rewritten.
The measure of an interface is not how quickly a rested person can use it. It is how much of the work survives when they stop paying attention halfway through.
Given a way to mark things, people immediately want to sort what they marked. Colour costs nothing: you reach for the yellow one because it is the yellow one, and the meaning follows the habit.
Sticky notes go wherever you drop them — in the margin, over a figure, next to the paragraph you want rewritten. They are written in place, they stay where you put them, and they come back when you reload the page.
Keys: N note · T text label
Every serious piece of software is used by someone who is about to be interrupted. The meeting starts in four minutes, the child needs collecting, the deploy is still red.
What matters far more than speed is whether a thing can be put down and picked back up without having to reconstruct where you were. That takes a marker: a way to point at one sentence and say this one, the claim I do not believe.
Anchoring to a pixel position fails on the first reflow. Anchoring to an element fails the first time the framework re-renders. Anchoring to the text itself survives nearly everything short of the sentence being rewritten.
The measure of an interface is not how quickly a rested person can use it. It is how much of the work survives when they stop paying attention halfway through.
Given a way to mark things, people immediately want to sort what they marked. Colour costs nothing: you reach for the yellow one because it is the yellow one, and the meaning follows the habit.
Copy a share link and your highlights, notes and comment threads travel inside the link itself — nothing is uploaded to make one. Whoever opens it is asked first, then the same marks appear on their copy of the same page.
Keys: Alt⇧S copy share link
Marks are saved against the page's address and ride Chrome's own profile sync, so the highlights you left on your laptop are on the same page on your desktop. Sync goes through your browser account — never through us.
Settings → Sync & data, with a per-page list and JSON export
Presenter mode gives you a laser pointer, ink that fades on its own, and a spotlight that dims everything but the part you are talking about. The page underneath stays fully usable, so you can keep driving while you point.
Keys: ⇧P presenter · ⇧L laser · ⇧D ink · ⇧S spotlight
Every serious piece of software is used by someone who is about to be interrupted. The meeting starts in four minutes, the child needs collecting, the deploy is still red.
What matters far more than speed is whether a thing can be put down and picked back up without having to reconstruct where you were. That takes a marker: a way to point at one sentence and say this one, the claim I do not believe.
Anchoring to a pixel position fails on the first reflow. Anchoring to an element fails the first time the framework re-renders. Anchoring to the text itself survives nearly everything short of the sentence being rewritten.
The measure of an interface is not how quickly a rested person can use it. It is how much of the work survives when they stop paying attention halfway through.
Given a way to mark things, people immediately want to sort what they marked. Colour costs nothing: you reach for the yellow one because it is the yellow one, and the meaning follows the habit.
Tools, colours, categories, the notes panel, screenshots, presenter and recording all sit on single keys. Remap any of them in Settings with a field that records the keys you press and warns you when two actions collide.
Every serious piece of software is used by someone who is about to be interrupted. The meeting starts in four minutes, the child needs collecting, the deploy is still red.
What matters far more than speed is whether a thing can be put down and picked back up without having to reconstruct where you were. That takes a marker: a way to point at one sentence and say this one, the claim I do not believe.
Anchoring to a pixel position fails on the first reflow. Anchoring to an element fails the first time the framework re-renders. Anchoring to the text itself survives nearly everything short of the sentence being rewritten.
The measure of an interface is not how quickly a rested person can use it. It is how much of the work survives when they stop paying attention halfway through.
Given a way to mark things, people immediately want to sort what they marked. Colour costs nothing: you reach for the yellow one because it is the yellow one, and the meaning follows the habit.
A PDF link opens in a viewer with the whole toolbar available, including real text
highlighting rather than a rectangle drawn over the words. It is recognised by what the
server says it is, so a link with no .pdf in it still opens here. Downloads
still download.
The notes panel shows every highlight, note and comment on the page, with a live count per category and a search box. Filter to your open questions and read only those, then copy the lot as Markdown grouped by category.
Comment threads that other people can answer, names on every reply, and an @mention that puts a question in front of the person who can settle it — on any page on the internet, not in a copy of it.
This is what is being built next. It is not in the extension yet: today a comment thread is yours alone, and the way to get it to someone else is the share link above.
Every serious piece of software is used by someone who is about to be interrupted. The meeting starts in four minutes, the child needs collecting, the deploy is still red.
What matters far more than speed is whether a thing can be put down and picked back up without having to reconstruct where you were. That takes a marker: a way to point at one sentence and say this one, the claim I do not believe.
Anchoring to a pixel position fails on the first reflow. Anchoring to an element fails the first time the framework re-renders. Anchoring to the text itself survives nearly everything short of the sentence being rewritten.
The measure of an interface is not how quickly a rested person can use it. It is how much of the work survives when they stop paying attention halfway through.
Given a way to mark things, people immediately want to sort what they marked. Colour costs nothing: you reach for the yellow one because it is the yellow one, and the meaning follows the habit.
A highlight is anchored to the text it covers, not to a spot on the screen. Reload the page, resize the window, let the layout rearrange itself — the mark stays on its sentence.
Drag the handle across the panel.
Annotating, PDFs, presenter mode, screenshots and recording all run entirely on your computer. No telemetry, no usage counter, no advertising SDK. We do not know which pages you visit, because nothing tells us.
The one thing that is ever uploaded is a recording you share by link. Before you do that on a site you are signed in to, read this first.
Replayink