Figma is a UI visual design tool that enables you to demonstrate your output as a prototype, whereas Protopie is a prototyping (programming) tool that can make things that look very real.

Whereas Figma requires the user to draw out all versions of the UI in tight detail before the prototype can be put together, Protopie lets you (expects you to) start with programming the behaviours in the UI.

When you import Figma elements into Protopie it is great to get all the rich visual detail that Figma encourages. but it also means (in most cases) that you have imported vastly more than is actually needed. In Protopie you don’t need to draw every version of a component … instead you just need to ensure that you have all the required elements whose size, shape, colour, visibility, etc can then all be programmed as needed to produce all your Figma variants.

Likewise whereas in Figma you need a different frame for every screen that is visually different (and all frames must be drawn out), in Protopie a scene is often best used for a single coherent piece of functionality. A single scene in ProtoPie might include numerous scenes in Figma.

Furthermore, autolayout in Figma means that graphical elements that may not be functionally related are often clustered into one container (component) in order to take advantage of auto layout.  But in Protopie you want to group together things that are functionally related.