Feedback, settled.

Pin feedback to any part of your prototype. Review it, resolve it and hand it to developers, all in one place, with nothing added to your code.

Start free Already have an account? Sign in Open your hub
See how it works

From first comment to build.

Feedback in Hobnob goes somewhere. Every comment is pinned to a component, reviewed in a round, settled, and handed to the developers building it.

  1. 01 · Feedback

    Pin it to the part you mean.

    Reviewers click the component they’re talking about and comment right there. Nobody has to describe where they mean, and the comment stays with the component when the layout moves.

  2. 02 · Review

    Everyone in one round.

    Send one link. Your client, your team and stakeholders leave feedback under their own name, with no account, and reply to each other in place.

  3. 03 · Resolve

    Settle it, then sign it off.

    Resolve what’s done and carry the rest into the next round. Your client signs the round off, and every decision goes on the record.

  4. 04 · Build

    Hand it to developers.

    Add design notes to the components that need explaining. One command writes the handover: every note, with a picture of the component it describes.

Nothing goes into your prototype.

Hobnob sits in front of your preview and adds its layer as the page loads. Your code, your repository and your build stay exactly as they are.

The usual way

<!-- add before </body>, redeploy, remember to remove -->
<script src="https://feedback-tool.example/widget.js"></script>
  • Paste a script tag into your code
  • Redeploy every prototype you want reviewed
  • Remember to take it out before launch

With Hobnob

/r/fieldbook/round-3
  • Paste your preview address into the hub
  • Send the review link to anyone
  • Your code never changes

Reviewers never need an account.

They open your link and type their name. No sign-up, no install, no browser extension. That’s how you get feedback from people who’d never make an account.

ClientsComment straight from the link in your email.
StakeholdersSee each other’s comments and reply in place.
Your teamInvite them to resolve comments alongside you.

One focused question at a time.

A review round asks for feedback on one thing, from the people you choose. Open it, collect comments, close it, and carry anything unfinished into the next one.

A brief for each round

Tell reviewers what you need from them, and which pages to look at.

Internal or external

Keep the team’s first pass separate from what the client sees.

Nothing lost between rounds

Unresolved comments carry over, marked with the round they came from.

From first comment to handover.

Hobnob’s design notes sit in the same layer as the comments. When the design is settled, one command writes it up for the developers building it.

Design notesAnnotate components for developers, styled like annotations so nobody mistakes them for the product.
A handover documentEvery note, with a screenshot of the component it describes.
A line in gitThe prototype’s history is tagged at the handover, so everyone knows which build was agreed.
~/fieldbook $ hobnob cut
Run from the Hobnob command-line tool.
Design note · Search button

Run your next review in Hobnob.