Take a banking application for example, you would write up a test doc to test something like the following If you are showing a user a product and saying "go ahead and use it" you are wasting their time, and your own time.Ī user test should be specifically testing a number of user flows. The vast majority of the time your user tests should be flow specific, you don't need a fully functional application with 400 wireframes and state changes, table changes etc, its pointless. So all you (the designer) has to do is drag and drop everything in a few artboards, write up some dev instructions with flows and hand it off.Ī dev then has their component library and can whip up a few pages in your testing server to deploy for testing. Velocity for a POC will always be better if a dev team is handling a prototype (working from a design).Įverything should be componentised. A designer should never be creating POCs, that's the dev job. The argument for something like Axure is powerful prototyping capability, for a designer. I don't want to have to rely on some random developer to make and support a plugin that is vital to our work.įigma doesn't need elaborate prototyping. I've been burned by plugins before, and I won't load anything that is more than a convenience feature. I'm not going to wait around for a plugin to do this, it has to be a core function of Figma. What I've seen a coworker make in Axure, Figma is nowhere near what they are capable of right now. ![]() Especially Sketch, Invision and XD as well as Figma. Try making a prototype of a desktop or enterprise application and that's where most of these applications fall short. Also, the fact that there are so many applications that can handle that work. I think the mistake Sketch and a lot of tools are making is NOT acknowledging the fact that it's easy to make something to build mobile apps. I've been looking at Protopie for that kind of functionality. I would love it if they did, but I see no evidence of it yet. Until they incorporate variables that can be stored and recalled to drive element properties, there's no indication to me that they're heading in that direction at all. For those designers who need to prototype complex form-driven UIs for user testing, designers need a different class of tool like Axure RP (and more direct competitors like ProtoPie) or the ability to write code. In those cases, Figma will likely be enough. I could see Figma going down the route of Framer and allowing custom HTML elements to fill in the prototyping gap, but that still requires the designer to know how to write code.Īt the end of the day, many designers either create basic pages with limited interactivity or don't need the ability to allow their users to directly interact with complex form elements during testing. ![]() Because of the way Axure is designed it would be easier for them to improve their sharing tools and add autolayout than for Figma to fundamentally change the way they do prototyping and add HTML elements and advanced JavaScript logic. However, as Axure creates HTML and could easily implement a Flexbox approach I would be surprised if they don't implement it soon. If you are creating complex enterprise software and want to allow users to interact with a prototype form and fill it out while triggering validation along the way, Axure is clearly superior to Figma.Īxure is far behind in terms of sharing and collaboration with its SVN approach, and surprisingly still lacks the equivalent of autolayout (with a very basic implementation in repeaters). As a result, for a design with 5 dynamic elements with 10 results each, Axure can handle everything in one page, while Figma would take 50 frames to handle every combination, to say nothing of a component that allows free text. Axure also focuses on individual dynamic panels with states on the same page. Axure RP actually generates HTML prototypes with HTML form elements and a healthy amount of JavaScript logic. ![]() Figma is more similar to Sketch and InVision prototyping in that it still fundamentally moves through a series of art boards, with some animated effects available. The comparison with Axure RP is a bit less clear cut because the prototyping on Figma is fundamentally different. Considering those issues, it's not surprising that Figma has overtaken Sketch. I have used Axure RP on and off for over 15 years, and used Figma as my primary design tool for more than two years, with Sketch and InVision before that.įigma has nearly 100% overlap with Sketch, as well as being browser-based so it works cross-platform vs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |