Build a small tool with Sites, Artifacts or Canvas
Choose the workspace based on what you need to publish, share and maintain.
What you’ll finish with A small working prototype and a checklist for sharing it.
AI-generated guide · Content revised · Allow about 25 minutes for the exercise
The walkthrough
Choose one useful interaction
Start with a calculator, checklist or explainer. Write the inputs, expected output and one realistic example. Avoid adding accounts, payments and private data to a first experiment.
Choose the destination
Use Sites when publishing a website is central to the task. Compare Artifacts or Canvas for work you want to develop interactively inside the assistant. Check the available export and sharing options before choosing.
Build and test the same example
Supply the brief and a known example. Check the result on a narrow phone screen and with keyboard navigation. Try empty fields, very long inputs and an obviously invalid value.
Inspect the sharing settings
Preview the actual shared result. Confirm that private source material is not included, links work and you understand any hosting or usage limits. Keep a copy of the brief so future changes are easier.
Text to start with
Replace the bracketed sections with your own details.
Build a small [calculator/checklist/explainer] for [audience]. Inputs: [fields]. Expected result for this example: [example]. Keep the layout usable on a phone and with a keyboard. Explain any assumptions that affect the result. Do not publish until I have checked the preview.
A complete worked example
Build the same simple event-budget calculator in whichever workspace you can access. The expected results below are known arithmetic checks, not a claim that each provider was tested.
Complete build brief
Build a public-data-only event-budget calculator.
Inputs: attendees (whole number, zero or more), cost per attendee (zero or more), fixed room cost (zero or more).
Total = attendees × cost per attendee + fixed room cost.
At 20 attendees, $8 each and a $60 room, show $220.00.
At 0 attendees with a $60 room, show $60.00.
Reject negative values and fractional attendees. Empty fields show a helpful message.
Use visible labels, keyboard controls and a phone-friendly layout.
No accounts, payments, external APIs, storage or publishing until the preview is checked.
Expected results
Swipe or scroll across the table to see every column.
Expected results
Input
Expected output
What it checks
20 people; $8 each; $60 room
$220.00
The intended formula.
0 people; $8 each; $60 room
$60.00
Zero is valid.
2.5 people or a negative cost
Explain invalid input; no total
Whole-person and nonnegative constraints.
An empty field
Explain which field is needed
Missing is not silently zero.
Sharing and maintenance choices
Swipe or scroll across the table to see every column.
Sharing and maintenance choices
Workspace
Useful distinction
Before sharing
ChatGPT Sites
Website publishing with audience and owner controls.
Preview the actual visitor experience; inspect audience and hosting settings.
Claude Artifacts
Interactive outputs with sharing options that vary by artifact and plan.
Ordinary shared artifacts require a Claude account; legacy public chat artifacts have different rules.
Gemini Canvas
Create and edit an app in Gemini, then share through its export controls.
Review app info and whether associated data is shared before creating a public link.
Finish the prototype
Try every known example, then use the keyboard and a narrow screen. Ask for the smallest correction when a check fails. Open the shared result as the intended reader: it must explain its assumptions without your chat history. Keep a copy of the source and brief. The example deliberately avoids persistent data; adding accounts or shared storage changes both the privacy and maintenance work.
When it goes wrong
Empty values are converted to zero or the shared page depends on your private chat.
How to correct it
Require explicit validation and a self-contained explanation, then repeat the failed visitor journey.
Finished when
The calculator passes the known cases, rejects invalid inputs and can be used by the intended audience.
Check the result
Does the known example produce the right result?
Can someone use it without your chat history?
Are sharing, export and usage limits suitable?
Before paying
These features may require an eligible plan. Hosting and visitor usage can have limits beyond the chat allowance.