Skip to content
  • Protopie and Figma
  • Protopie Tips
  • Experience Prototyping
  • Protopie and Figma
  • Protopie Tips
  • Experience Prototyping

PROTOPIE

This video illustrates one of Protopie’s strengths, which is the ability to create closer to real experiences. It shows two instances of the same prototype, each running on its own device, but able to talk to each other. The intention was to mimic the kind of behaviour that might occur in a clinical setting with multiple receptionists managing patients arriving for and making new appointments – but this uses a quiz format, where the players can choose their question types (as available from  the 4000+ questions on the OpenTrivia Database ).

A question can only be answered by one of the two players and scores are penalised for incorrect answers. There is no need to answer every question. When a player has done their best they can see their own score, but when both are done, they see each others’ scores and can review the correct answers.

I think it is reasonable challenge to the other prototyping platforms to be able to create something like this – yet many many real world experiences (in healthcare especially, but elsewhere too) have exactly this kind of multi-person requirement.

This prototype is available to view (as a one player game) on cloud.protopie.io , but if you have access to Protopie Connect then you can download and run it as a two person game

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.
more ...

Working with Components

more ...

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.
more ...

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.
more ...

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.
more ...

Viewing variables within Components

The variable debugger doesn't work when the variable that needs to be viewed is inside a component. There are two relatively easy ways to deal with this.
more ...
Origami Studio, Figma and others
How do these other popular platforms compare?
more ...
Good Prototyping Practice
IDEO's 3R prototyping principles from the late 1990s still apply - "Right, Rough, Rapid" but in the UX and UI space they are easily misunderstood.
more ...
Why use Protopie?
There are many prototyping tools out there, so what makes Protopie special – how is it different?
more ...

© 2023: David J Gilmore