WIPP field notes / Developers

Show a prototype and ask what people understand

Make a prototype understandable through a safe screenshot or recording, without asking a viewer to inspect your entire codebase.

Choose another craft
Illustrative interaction sketch: connect a control to the behavior it changes.

Start withOne safe capture. One interaction to understand.

  1. Share contextStage, goal, constraint
  2. Ask one questionObservation before verdict
  3. Test one changeKeep the original; compare

An indie dev prototype does not need a launch announcement to be worth sharing. A screenshot can expose a confusing control; a short recording can show an interaction that is hard to describe. Creative coding experiments can invite discussion about motion, composition or how a viewer understands the result.

On WIPP, share visual progress as an image or video project with a description of the current behavior. WIPP is not Git code hosting, a build service or a deployment platform. A visual critique also cannot establish that the code is secure, performant or correct.

Choose between a still image and a behavior recording

Use a screenshot when the question is about labels, visual hierarchy or a state that can be understood at a glance. Use a short video when timing, a transition or a sequence of actions is the issue. Start from a known state and show one task rather than a tour of every feature.

For a generative sketch, capture a representative output and describe which inputs change it. If the interesting behavior happens only sometimes, say so. A carefully chosen recording is evidence of one run, not evidence that every possible input works.

  • Show the initial state and the action the person is attempting.
  • Explain what is implemented and what is mocked or manually triggered.
  • Name the device or viewing context if it changes the interaction.

Remove secrets and real user data before capture

Use dummy data and inspect the whole frame, including tabs, notifications, terminal output and browser address bars. Hide API keys, tokens, email addresses and confidential repository names. Crop unnecessary surroundings rather than relying on a viewer not to notice them.

Only share work and assets you are allowed to show. If a prototype belongs to an employer or client, obtain permission or make a separate practice example. Never include credentials so someone else can try it, and do not ask commenters to paste secrets or production logs into a public thread.

Ask a person to predict the interface

Before explaining a control, ask what a viewer expects it to do. In a recording, pause at a decision point and ask what seems possible next. Their prediction can identify a misleading label or missing state more directly than “Would you use this app?”

For creative coding, separate the visual result from the interaction model. Someone may enjoy the pattern but not understand that dragging changes its density. Ask about those two things independently. State any limitations: a mock confirmation screen should not be presented as a working transaction.

Turn one observation into a small prototype test

Write down the observed confusion, the change you want to try and how you will tell whether it helped. For example, if a filter looks like a navigation tab, change its label or grouping and ask a new viewer what they think it does. Keep the test small enough to compare meaningfully.

When sharing an update, describe the change and any remaining limitations rather than claiming the prototype is finished. Run your own functional, accessibility and security checks outside WIPP. Community screenshot feedback can complement those checks, not replace them; replies and favorable outcomes are never guaranteed.

Illustrative practice brief / Not a member project

Example description: a creative coding control

This recording shows a local particle sketch with dummy controls. Dragging changes the density; the Save button is a visual placeholder and does not store anything yet. Before reading that explanation, what would you expect the slider to change? I am looking for feedback on the interaction cues, not a code review.
Stage
Local particle sketch recording with dummy controls.
Goal
Understand whether the interaction cues communicate density changes.
Ask
Before the explanation, what would you expect the slider to change?
Boundary
Interaction cues, not code review. Save is a placeholder and stores nothing.

This illustrative prototype description makes the unfinished behavior explicit. A viewer can critique what is shown without mistaking a mocked control for a live feature.

Feedback prompts to adapt

Choose one question that fits the stage of your work. You do not need to ask all of them.

  • What would you expect this control to change?

  • Which state makes it clear that the action completed?

  • Where in this sequence would you hesitate before continuing?

  • Does this motion help explain the interaction or distract from it?

Put it into practice

A small next step on WIPP

Capture one safe prototype task, note its limitations and ask what a viewer expects. Keep implementation details and sensitive debugging material out of the public post.

Posting requires signing in. Feedback is optional.