Auto-Animate (like Principle, Flinto and XD)
closed
F
Fredo Tan
closed
Patricia (ProtoPie Team)
complete
It's in ProtoPie 6.1.
Learn more about this: https://www.protopie.io/blog/animated-transitions-with-smart-jumps
Florin Ursu
Patricia (ProtoPie Team): That's so great!!! Thanks!!!
Florian
Patricia (ProtoPie Team): amazing
Yasir Eryilmaz
Patricia (ProtoPie Team): This is great but I wish you didn't take the Figma approach but Principle approach. In Figma, unlike Principle, there's only one control which is screen transition. But in Principle, it smart animates it but you can individually control the animation time and curves for each individual layers.
Don't get me wrong, Protopie is awesome but the scene animations and micro interactions are so hard to achieve in Protopie.
Patricia (ProtoPie Team)
Yasir Eryilmaz: Thank you for the feedback. I believe our product managers wanted to enable users to import their Figma transitions as Jump into ProtoPie, hence the similarities between Smart Animate and Smart Jump. I'll share your comment with them though!
Michael Anthony Raquel
Patricia (ProtoPie Team): Does Auto-animate in Protopie lets you auto-animate components, which is similar in Figma?
Patricia (ProtoPie Team)
Michael Anthony Raquel: yes unless I'm misunderstanding your question 🙂
Michael Anthony Raquel
Patricia (ProtoPie Team): My pain point is that my component in Protopie won't let me jump(response) to another component that I want to auto-animate, it only letting me to jump to another scene. It would be nice if I can auto-animate components to components in Protopie.
Patricia (ProtoPie Team)
Michael Anthony Raquel: Ok I understand better now. That's indeed not supported yet, you can only smart jump between scenes currently!
ayush tiwari
Patricia (ProtoPie Team): Amazing !!!!!
Patricia (ProtoPie Team)
in progress
M
Mitchell Hart
Patricia (ProtoPie Team): 🤯
Greg Sargent
I'm not sure this would be an upgrade/improvement. One of the things that is so great about protopie is not creating a dedicated screen for every interaction. With auto-animate features found in other apps, one would need to create dozens of screens for each interaction.
In protopie you only create one screen and build the interactions into the component level instead of linking two screens together.
This is the key benefit/feature of protopie over another solution like Principle, Flinto, etc.
Mitchell Hart
Greg Sargent: This feature request isn't suggesting a move to the two screen model. Here the states are all contained in a Response. Check out the screens linked below.
L
Luke Han
under review
F
Florin Ursu
Luke Han: 😱 OMG, make it happen ❤️
Florian Grau
Luke Han: Most important feature!
Mitchell Hart
Florian Grau: Yes! And your work on this feature is just about perfect as to how it should work.
F
Florin Ursu
Any updates on this? Pretty please 🥺, we really need it :(
Jose Antonio Orellana
Auto Animate feature from Principle is terrible because it forces you to go through each single layer's name to make sure that there's no duplicates causing "flying objects".
If auto animation is implemented I hope at least there's a way to switch it off, because the auto animation from Principle was driving me crazy.
M
Mitchell Hart
Jose Antonio Orellana: ProtoPie doesn’t work by transitioning between frames ( or art boards) so it likely wouldn’t work that way. A more controlled approach would be a state toggle button that allows you to move, scale and rotate any layer until deactivating the state button. Doing so would add those transitions wrapped in a trigger function. That’s how I imagined it working at least.
Imagination Digital Team
This is maybe the number one thing that needs to happen! Doing even simple interactions in ProtoPie can take hours instead of minutes!
F
Florin Ursu
I would really want to underline the importance of Auto-animate. I had 6 screens for whichI wanted to add interactions to in Protopie. It took me 30 mins to do it, when I decided to return to XD and just do it there in 15 seconds.
I love Protopie for its ease of use in complex interactions, but sometimes is just overkill doing simple interaction.
It's known that buttons have 3 main states, why do I have to define 6 interactions for that?
ProtoPie
Merged in a post:
Add a morph transition
j
josef pa
Just simply take the PowerPoint morph idea and import it to ProtoPie.
Load More
→