Put code inside components

Receive and Assign hazard

Receiving a message, and then assigning a value and then writing a conditional based on that value is that something that is quite a normal, conceptual pattern – but in Protopie it will often not work as expected. This is because responses to Protopie triggers all happen simultaneously and not in the order written.

Using the wrong mental model for Protopie

Most prototyping tools for designers use the frame-by-frame, or multiple dartboards model. But Protopie is much closer to a developer's object-oriented model of an application UI.

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.

Moving between Figma and Protopie

Why use Protopie?

There are many prototyping tools out there, so what makes Protopie special – how is it different?

Use Variables

Variables are very powerful simplifying tool and they do not seem to have any impact on Protopie's performance.

Origami Studio, Figma and others

How do these other popular platforms compare?

Check if your other pie is present

When building a connected system it can be valuable to know if the other pies are loaded into Connect or not – for examples so you don't get stuck waiting for a message that will never be sent.

The wrong variable type

Put code inside components

Sending a message to another scene

Receive and Assign hazard

Origami Studio, Figma and others

Arrays and multiple parameters