Only record certain steps in Interaction recordings (Handoff)
planned
Alan EDodds
Very much needed to make the hand-off more sensible and robust.
Ryan Cuppernull
Adding support for this and the ability to hide layers in the list. So many extra layers, triggers, etc needed to make the prototypes that are not needed for handoff. These just add noise to the list and make it really confusing for partners.
Ryan Cuppernull
Also adding a note that being able to rename the layers/actions would be really helpful as part of this. Or even if they used the names from the ProtoPie file, noticing they do not match the updated names I use in my files action list.
songz meng
also need a hook for dev to navigate to the certain layer and properties
Patricia (ProtoPie Team)
planned
Amin Shazrin
Patricia (ProtoPie Team): Yes! Finally! Very useful feature for rapid development process!
Patricia (ProtoPie Team)
Merged in a post:
"Interaction Recipes" urgently needs additional clip functions!
Deisgn MICC
Problem:
The Interaction Recipes feature is very unfriendly for recording complex interaction effects, than recording the motion of an app scoring popup, I only want to record the motion of the popup popping up and closing down to provide to the R&D staff.
It records all the parameters from the very beginning of the interaction prototype, it records a lot of parameters that the developers don't need to know about, it records all the effects of the app from the click of the download button, the download process, the completion of the download, the installation etc. into this "Interaction Recipes".
This makes it extremely difficult for the developer to find the pop-up window movement in the Interaction Recipes.
The solution:
- click on Recipe to record without resetting the entire interaction prototype after the interaction has been recorded
- edit the Interaction Recipes to provide an AE-like editing function to cut out the parts that the developer needs to know.
- Provide a hidden layer-like function to hide the interaction effects. When designing complex interaction prototypes, there is a lot of sending and receiving involved, but in the Interaction Recipes interface, sending and receiving are only shown as "Receive/Send" characters, which does not provide a quick and effective The Interaction Recipes interface only shows the "Receive/Send" characters and does not quickly provide valid information to visualise what was sent and what was received.
- when a Group name is set for an interaction in a Pie design, display that Group name in the Interaction Recipes
- when a layer of Interaction Recipes is selected, highlight the interaction parameters for that layer, just as it does in the Pie APP!
Other improvements:
It is suggested that the name of the interaction snippet can be changed directly in the sub-page of Interaction Recipes, it is not convenient to have to go back to the main screen to change it each time.
As you know, ProtoPie is a design tool for creating high precision prototypes and the "Interaction Recipes" are the most valuable feature for most designers (T0 level) and the main reason why they are worth purchasing. I hope the Pie team will improve this feature soon, Pleassssssse!
Patricia (ProtoPie Team)
Merged in a post:
Link and share to exact frame of interaction recipe timeline
Han Lee
Interaction recipe is super helpful. But it makes handoff a bit complicated every recording starts from the beginning of interaction. I saw other request about record partially which makes sense.
I also think if we can annotate on the frame on timeline of interaction recipe and share the exact frame as a starting point(maybe ending point as well) - it would be so much easier to specify thing during handoff communication.
Since I have a handful of devs work together, it would be helpful to manage single source of truth and allocate the micro task at the same time.
Patricia (ProtoPie Team)
Merged in a post:
Trim Interaction Recipes
David Lee
I want to be able to trim unnecessary parts like starting and ending with no interactions.
C
Cyan Camel
Agree with both of you. Having a recipe for a full prototype is a bit useless. It needs to be broken down into small pieces. And would love to remove invisible layers.
Han Lee
Plus one. If partial recording is not possible, at least annotate on the Interaction Recipes and generate separate links would be helpful. This is great tool for hand-off purpose, and hand-off needs to be broken down smaller pieces some time.
P
Philipp Nürnberg
Yes, it's a bit uncomfortable to share just small pieces when your prototype covers a lot more.Then it would be possible to share small recipes named e.g. "card interaction" or something no matter where in the user flow it was recorded.
Load More
→