Skip to content

UX Prototyping & Protopie

  • Principles
    • Educational
    • Figma Integration
  • Patterns, Pitfalls, Ploys
    • Patterns
    • Pitfalls
    • Ploys
  • More …
    • People-Centered Design
    • Thinking about AI
  • Principles
    • Educational
    • Figma Integration
  • Patterns, Pitfalls, Ploys
    • Patterns
    • Pitfalls
    • Ploys
  • More …
    • People-Centered Design
    • Thinking about AI

Distinctive initial variable values

Often one finds that a variable that should have acquired a certain value has not yet done so. Or a condition depends upon a value that has been erroneously set. 

A useful ploy to help you see these kinds of problems is to use something like -99 as your default value, which is unlikely to occur normally in your pie. Then if you see -99 in your running pie, you can much more quickly see what is going on.

Likewise, especially when getting text from an API, or by string manipulation, having “” as. the default text value for a variable is easily overlooked as a problem. Using “Null” as your default value – which will again not be likely to occur in your pie anywhere else will help you distinguish between something not having been done and having been done with an empty string.

Keep trigger and response names visible

It is very important to annotate your code with what it is actually doing, but keeping the trigger and response names helps someone new to the project (or you in three month's time.

Origami Studio, Figma and others

How do these other popular platforms compare?

The wrong variable type

This pitfall is not a big deal, but it can waste you time as you try to track down why your variable seems to have the wrong value (or no value). It can also bite you in a formula where your variable is of the wrong type for the formula.

Use Components

It will often seem as though it will be faster to use individual elements than to use components, but in the end the time saving almost always goes the other way.

How to inspect variables inside a component

Even all-Scenes variables are not accessible inside a component. And this can lead to hard to find errors when a variable with the same name is used in a component, but its value is not sync'd with the scenes.

Check if Protopie Connect is present

If you are building a prototype that depends upon Protopie Connect then it is a good idea to start by checking if Connect is actually present.

Rough, Rapid, Right

Playing with time

A message sent to the current scene will be received by the object that sent it. But a message sent to Protopie Studio (Connect) will not be received by the pie that sent it. B ut what if there is nothing out there to respond to it?

Keep trigger and response names visible

Use overridable variables in components

Use Components

Check if Protopie Connect is present

parseJson gives no error message

How to inspect variables inside a component

  • Welcome
  • What’s New?
  • About
  • Welcome
  • What’s New?
  • About

info@peoplecentereddesign.org

© 2026 David Gilmore