AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() If such a high degree of this information were mere speculation, it would be asking for trouble. Differences like these show why it’s crucial to make user journeys that are highly data driven. Throwing more than one persona into the mix adds complexity and conflicting information. However, it must still be intuitive enough for Paul to painlessly discover the new features of a challenger bank with budgeting features.Īs a result, you’ll need to create two separate user journey maps for these two different personas. It’ll need to have a similar pattern to other highly downloaded banking apps on the market. I, for one, would love to completely ditch using another tool and I think we’d all agree.In each case, you’ll need to cater for both mental models. So yes, conditions, variables, scroll events, detecting state or value change… please let’s move in that direction. I kept thinking that doing even half of what we’re doing in ProtoPie within Figma makes a lot more sense. The notion (and reality) of managing two sets of assets in an iterative process is just wrong (not to mention lack of parity of features upon import). ![]() Before that I tried UXPin, Justinmind, Protoio, and Framer (that one’s over-reliant on React but if you’re working on a product team with your devs and a React code base then maybe that makes sense).īUT, I’ve been thinking that it is just bonkers to need two tools to accomplish this kind of output. Although its interaction model is great, it definitely needs work. I’ve been using ProtoPie for the past two years for advanced prototyping, and with its formulas, variables, conditional logic, functions, etc, we can build almost anything. Coming from Sketch a few years ago (and having used XD for one project because I had to), while obviously not perfect Figma is just smarter and imho better with its conventions and methods and I think justified in why it is the conversation in product design tools. But, you don’t really see a lot of folks talking about UXPin or Axure as their primary design tool. I came here to make a post about expanding Figma into the advanced prototyping territory and found this one.ĭesign apps are very product design forward which I like, and also afford some prototyping, and prototyping apps continue to add features to afford straight-up design processes as well. I recently have been thinking about the logistics of advanced prototyping, and the unfortunate divide between design apps and prototyping apps. ![]() Just a simple list of global access variable declarations that can be used in flow logic alongside the usual event settings. This would tremendously improve prototypes without requiring a ton of additional feature work. I would choose from those drop downs and make this: In the interaction panel, I want to see a section where I can choose a variable=value selection to act as a condition check, allowing me to send the flow to different frames, like this: Example: variable name: “password” with value: “hello”. In that connector, I want to highlight it, then see a “global variables” section in the property panel where I can add a custom global variable and give it a value. I’d like to be able to utilize a list of global variables that I can access in this panel, in order to create logic based events. When prototyping, we have the interaction panel to add input events. ![]()
0 Comments
Read More
Leave a Reply. |