Product

From “this is broken” to fixed, without a meeting.

A widget your reviewers can use without reading anything, and a dashboard your developers can use without asking anything.

The widget

A guest in your app, not a squatter.

A collapsed tab on the edge of the page. It opens on click, lives in a shadow root and causes zero layout shift. A page that never opens it pays under 3KB.

  • Pins that stay put. Anchored to the element, positioned by ratio, so they survive a resize.
  • Annotate. Arrows, boxes and blur on the screenshot before it is sent.
  • Record. Capture the steps; stopping drops the recording straight into a new Jot.
  • Threads. Reply in place, mention a teammate, see every Jot on the page.
The Jot composer pinned to the delivery line on a checkout page, with label chips and the screenshot attached.The Jot composer pinned to the delivery line on a checkout page, with label chips and the screenshot attached.
Click the broken thing, type one sentence. The screenshot and selector go with it.

The conversation happens on the page.

Reviewers see the replies right on the element they flagged. When the fix ships, they are the ones who approve it.

A Jot thread on the page: the developer replies that the fix is shipped, right on the pin.A Jot thread on the page: the developer replies that the fix is shipped, right on the pin.
The reply lands on the pin the reviewer left.

The dashboard

Dense where it should be. Calm everywhere else.

A board and an inbox over the same queue, live as Jots arrive. Open one and the full repro is on the right, ready to copy as Markdown.

usejot.co · acme-checkout
The Jot board for acme-checkout: Open, In progress, Resolved and Approved columns.The Jot board for acme-checkout: Open, In progress, Resolved and Approved columns.

Board and inbox

Drag across Open, In progress and Resolved. Filter by status, label, page, or just yours.

Approved is the reporter’s

The Approved column belongs to the person who reported it. Not to you, not to an agent.

Live, honestly

“Live” means the realtime connection is confirmed, not hoped for. New Jots just appear.

Session replay

See the thirty seconds before it broke.

Recordings replay the DOM, not a video, with the console and network side by side. Failed requests and errors are flagged on the timeline.

  • Inputs are masked in the browser before anything is uploaded.
  • .jot-block leaves an element out entirely; .jot-mask hides its text.
  • On mobile, crashes and failed requests come with the recording.
A session replay beside its network log: the POST to /api/orders returning 500.A session replay beside its network log: the POST to /api/orders returning 500.
Console, network and the page, on one timeline.

Share links

Send a bug to anyone. They don’t need an account.

Any Jot can be shared as a public link: the note, the context and the replay on one clean page. Drop it in a PR, a ticket or an email.

usejot.co/j/…
A public Jot page with a replay, one console error, the reporter’s note The pay button does nothing, its URL, selector and browser, and a reply: Thanks, reproduced on staging.

Mobile SDKs

The same Jot, in your native app.

React Native, Flutter, iOS and Android. Pins, annotate, record, threads, and crash reports that arrive with what led up to them.

Flutter: annotating a screenshot with a box and arrow; password and secret fields masked. Flutter
React Native: pins from several reviewers on an orders list, with the Jot dock at the bottom. React Native
Flutter: a new Jot composer with label chips, a screenshot attached and fields masked on this device. Flutter

Put it on your staging site today.

Free for one project. Reviewers are always free.