23:00 If you move both "Set variables" to above the 'Back' transition, then it will trigger those variables first before changing screens-effectively removing the Figma delay.
Your detailed walkthrough of advanced prototyping is impressive! 😄Throughout your design process, what's the most unexpected or quirky issue you've encountered while creating these interactions, and how did you solve it? 🚀
Some interactions are unnecessarily complex. For example, every interaction always has to be based on a trigger. It would be great to have have triggers based the state of components without having that need to click or tap on something all the time. Also more options to control such as CONTAIN. For example we can validate and activate the CTA when entering and email if it contains the @ symbol. Small things like this.
I'm genuinely impressed by how you explained your design's intricate details and the thoughtfulness you put into creating a seamless user experience. Kudos!
Absolutely! To solve these issues, designers often need to think creatively, collaborate with team members, and iterate on their designs. Prototyping tools and user testing can be valuable in identifying and addressing unexpected issues early in the design process. The key is to remain flexible and open to new ideas, even when faced with quirky challenges, in order to create the best possible user experiences. Great work btw!
It takes time to understand all this 😅 Btw had a query, The element is a horizontal tracking frame with checked, in transition and 'not yet' icons with different widths. How to add the bars/rectangles that maintains the same distance between all the icons having different widths?
In no way does the user want you to clear a phone number field when you navigate back to the previous screen. If you clear the field, there will be uncertainty as to whether the number input was incorrect or if there was a system issue. This is a clear violation of the error recovery heuristic.
It’s a lot simpler in development cause the functionality to build it is a lot simpler. For example, in code you can show or hide an element of a condition is met. But in Figma it is always connected with a tigger which is why it’s extremely complex in Figma
23:00 If you move both "Set variables" to above the 'Back' transition, then it will trigger those variables first before changing screens-effectively removing the Figma delay.
Your detailed walkthrough of advanced prototyping is impressive! 😄Throughout your design process, what's the most unexpected or quirky issue you've encountered while creating these interactions, and how did you solve it? 🚀
Some interactions are unnecessarily complex. For example, every interaction always has to be based on a trigger.
It would be great to have have triggers based the state of components without having that need to click or tap on something all the time.
Also more options to control such as CONTAIN. For example we can validate and activate the CTA when entering and email if it contains the @ symbol. Small things like this.
Your video tutorial is incredibly informative and engaging, making it easy to follow along and learn from. Great job! 👏😄@@DesignPilot
I'm genuinely impressed by how you explained your design's intricate details and the thoughtfulness you put into creating a seamless user experience. Kudos!
Absolutely! To solve these issues, designers often need to think creatively, collaborate with team members, and iterate on their designs. Prototyping tools and user testing can be valuable in identifying and addressing unexpected issues early in the design process. The key is to remain flexible and open to new ideas, even when faced with quirky challenges, in order to create the best possible user experiences. Great work btw!
Your video tutorial is highly informative and engaging, making it straightforward to follow along and learn from. Excellent work!
That's great! Thanks!
I dont know why here us inly 1000 views on this video, these are the tutorial which are extremely excellent
It takes time to understand all this 😅
Btw had a query,
The element is a horizontal tracking frame with checked, in transition and 'not yet' icons with different widths. How to add the bars/rectangles that maintains the same distance between all the icons having different widths?
In no way does the user want you to clear a phone number field when you navigate back to the previous screen. If you clear the field, there will be uncertainty as to whether the number input was incorrect or if there was a system issue. This is a clear violation of the error recovery heuristic.
Definitely. But I was just showing the possibility to clear with Figma
Totally fair 👍🏻
is it complex to implement in native android development as well?
or is it just me, who finds it difficult to build logic for this in figma 😅
It’s a lot simpler in development cause the functionality to build it is a lot simpler. For example, in code you can show or hide an element of a condition is met. But in Figma it is always connected with a tigger which is why it’s extremely complex in Figma
@@DesignPilot I hope this prototyping will get easier to do by time.
It's a blessing for us to have a mentor like you, amazing content as always.