Build a Product
Build a booking form that can explain what just happened
A first prototype should distinguish a requested time from a confirmed appointment.
You pick 2 p.m., press a button, and see “Success!” Did you book an appointment or ask someone to check a calendar? A first-time builder can learn more by fixing that one ambiguity than by adding a calendar integration.
Build a local prototype for a repair shop. Give the customer three fields: preferred day, preferred time, and email. Label the button “Request this time.” After a valid submission, show the chosen time, the destination for the reply, and the words “Request received. The shop will confirm availability.” A fake database or an in-memory list is enough for this exercise.
Build the awkward states first
Leave the email blank. The form should identify the field, explain what to enter, and keep the date the person already picked. Now double-click Submit. Your prototype should make one request and show one receipt. Finally, make the time unavailable between selection and submission. Preserve the contact details and offer another time. MDN’s guide explains native form validation and why a real service also checks submitted data on the server. MDN • Client-side form validation
Chrome’s WebMCP guidance adds a second design question: how could a browser agent identify the action and its inputs? Precise labels help you answer it. “Request an appointment” describes what this form can actually do. Chrome for Developers • Agentic forms
Invite someone to complete the prototype. Before they close the confirmation, ask, “Would you go to the shop at two?” If they say yes, revise the receipt and test it again. Your build has a clear finish line: the customer takes the right next step.