#Make your webpage scalable axure rp code
#Make your webpage scalable axure rp series

The landscape of UX tools are constantly improving at a rapid pace. Yet, it may be more effort than you’re willing to invest in time and/or money to research, acquire, and learn these plugins and workflows.Īxure RP is the most complete out-of-the-box prototyping tool on the market, notwithstanding it’s deep support, community, and resources. Considering the vast library and resources available for Figma and Sketch, it is possible to account for many of these shortcomings. Sure, I picked on Figma in this article, but similar limitations are present in Sketch, the dominant design platform permeated across many enterprise UX teams. When testing a high-fidelity prototype with actual users, a close parity to the real-world experience ensures your test results won’t be muddied with the limitations of the design tool used or worse - force you to redesign your approach to fit the limitations of the tool.

#Make your webpage scalable axure rp code

This design process with Axure RP is more aligned with designing for code in that you’re building components, states, and logic that behave as you would expect in production. Īxure RP is a true rapid prototyping tool

#Make your webpage scalable axure rp series

the tabbed content or the series of circles below) you can do this no problem by swapping the overlays with the subsequent (‘two’ and ‘three’) circles, and closing the overlays when you click ‘one’. If you have just one series of similarly-sized components (i.e. The only way to do this is to “fake it” with overlays. This means one could navigate through a sub-menu while changing the states of other items below it.

We intended to have a segmented controller for the content in one frame that respects multiple states across other components on the page. Then, we got to the part where we test out interactions during prototyping.Īfter spending thirty minutes or so with my team, our cursors whizzing across frames, flipping in and out of prototype mode, the problem was abundantly clear: Figma doesn’t allow multiple dynamic states for multiple components simultaneously. Then, we got to the part where we test out interactions during prototyping.

Figma was a breeze to collaborate on information architecture and page designs. This was a giant conceptual prototype that included a custom CRM among other enterprise products. My team and I recently collaborated on a project using Figma. Understanding when to employ each is an important decision that can save you time, headaches, and deliver the results needed for the intended outcome. The prototype was designed in Axure RP 8.Īs an Experience Designer for Slalom Consulting, we regularly use Sketch, InVision, Axure RP, and Figma based on the project and client need. In retrospect, it’s no surprise that he thought the demo was in a live test environment considering how responsive the experience was with inputs, logic, dynamic states, non-linear navigation - it seemed like the real thing.

He asked, surprisingly, “wait, this isn’t live?” About halfway through the experience, he paused when my boss mentioned in passing that he was witnessing a prototype. In a previous role I demonstrated a completely overhauled checkout experience for the CEO. However, if you are tasked with creating a complex, non-linear experience with logic or need to create a near-production prototype without code, Axure RP beats Figma all day*. If you have a project that needs mockups or a prototype with simple navigation without multiple states, Figma is arguably the best tool for the job. For starters, its collaboration and intuitive UX is a seamless (and fun) experience. There are many things that Figma does undeniably well. F igma is all the rage in UX design these days with good reason.