Learn by Example
There's something so satisfying about a fun and playful one-page website. And these days, the feelings of playfulness and engagement produced by a good one-pager are often enhanced using scroll effects—special movement or visibility behaviors that happen as a reaction to you, the visitor, scrolling down the page. Scroll effects are easy to achieve in Axure RP using the conditional logic feature.
Did you know that Axure RP makes it easy to store user-entered data and then reuse it across widgets and pages in your prototype? There are actually several good ways to do this, but one sure-fire technique is to use a variable.
I've never been much of a draftsperson. Precise linework isn't really my area of expertise. More of a tracing guy, really. All of which is why I love shape transforms, which were introduced in Axure RP 8 but continue to be a lesser-known feature.
For this installment of our Easy Conditions blog series, I want to look at how conditions work together with masters. I've put together a pretty standard three-page prototype in order to demonstrate what I'll be discussing, as shown in the animation below. And I've built it two different ways: one example uses conditions, and the other does not.
With Axure RP, our goal has long been to create a tool that can go as low- or as high-fidelity as your project calls for. At the top of that spectrum—the highest of the high-fi—we've got the repeater widget.
For as long as Axure RP has had the conditions feature, it's been included in the "advanced" section of our training guide—here's our current documentation on conditions—and it's true that conditions are usually a must-have feature if you're building a prototype with a high degree of interactive fidelity. But the conditions feature itself isn't inherently complex.