Users love simple and intuitive products, but the design process required to get there takes considerable thought and judgement. When you’re starting work on a new software product or a new feature, the prototyping stage is a critical step, as it enables you to test product concepts before investing the effort to build them out.
Prototypes are handy as internal deliverables that communicate your ideas visually and interactively. But if that’s all you’re using them for, you’re missing out on the benefits they can offer in the form of user feedback. Conducting user testing with your prototypes is valuable because you can’t be sure you have a winning design until you have real data to back it up.
Publishing to Axure Share is a handy way to share the HTML output of your Axure RP prototypes with your teammates and stakeholders. You click the "Share" button in Axure RP, hit "Publish", and get back a shareable link to the prototype. Bing, bang, boom!
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.
This guide pulls together a number of accessibility issues worthy of your consideration as you develop your next Axure RP prototype, along with some simple steps you can take in the tool to pilot your project toward an outcome that's more friendly for all types of people to consume.
The Notes feature in Axure RP is an easy way to document and communicate the intent and functionality of your designs. This can be especially useful as the developers are implementing the solution or when QA is writing test scripts based on the design.
Styles in Axure RP are a way to centrally manage the look and feel of pages and widgets across your entire project. Think of it like styles you use in Microsoft Word, or CSS for HTML in code.Using styles can save you a lot of time when updating the visual design of the project.