Axure RP: Prototypes With Complex Logic, No Code Required

What is Axure RP, and how is it different from other tools?

Axure RP is a desktop tool built for high-fidelity prototypes with behavior. Balsamiq centers on sketching and Figma on interface design; Figma also supports variables and conditionals in its prototypes (per its help center, on Professional plans and above). Axure takes the idea further: it describes what happens when the user acts, with conditional cases, global and local variables, dynamic panels, and tables that sort and filter, all without code.

The current version is Axure RP 11. Its release history lists build 11.0.0.4150, dated September 24, 2026, which added Axure RP MCP, a local server in alpha and described as experimental that gives AI tools access to the file’s contents (pages, widgets, interactions, and notes). Installation is documented for Windows and macOS; there is no Linux version.

Why does this matter for a junior designer?

Because there comes a point in every project where the drawn screen stops answering the question. If you want to test whether a loan application flow works when the user changes three answers, a static mockup is not enough. Knowing that a tool exists for this, and when to use it, lets you propose more realistic tests without depending on a developer.

Axure also forces you to think in states. Designing a prototype’s logic is, in practice, designing every case of the flow, and that helps you find gaps before you build anything.

How does logic work in Axure?

Axure organizes behavior into three pieces, according to its current documentation:

• Event, case, and action. Events are triggers (for example, a click), cases are ordered lists of actions that run when the event fires, and actions are the resulting changes. With conditional logic, Axure picks the case based on criteria you define.
• Variables. Global variables are accessible from every page in the project and pass information between pages; local variables live inside a single action or condition field. They store answers, totals, or states. Axure RP 11 added a Variable Changed event that triggers actions when a variable’s value updates.
• Expressions. They are used wherever the fx icon appears, for example to do math on a number or capitalize text before it is evaluated.

Other useful pieces, according to the product page: multi-state dynamic panels (from popups to scrollable mobile screens), the repeater widget for tables and grids that sort and filter, and adaptive views for desktop, tablet, and phone on a single page.

How do you use it for a prototype with logic?

1. Define the flow and its variables. Before touching the screen, write down what data the flow stores and what changes based on it.
2. Build the screens statically. Use dynamic panels for the states that change, instead of duplicating screens.
3. Add events per component. For example, when a field changes, a total updates.
4. Order the cases carefully. The documentation warns that case order matters when you use conditional logic, and the actions in a case run from top to bottom.
5. Test the paths, not only the happy one. Walk the flow with empty data, with errors, and with unexpected answers.

One maintenance detail: per the documentation, deleting an event also deletes all its cases and actions. Make copies before cleaning up a large file.

What licenses does it offer today?

According to the pricing page, checked on November 12, 2026, Axure RP has per-user plans:

• Pro: 29 USD per user per month. Includes unlimited prototypes, reviewers, and Axure Cloud projects.
• Team: 49 USD per user per month. Everything in Pro, plus co-authoring, revision history, and team project hosting in the cloud.
• Enterprise: price on request; adds user management, single sign-on, and private or on-premises security options.

Axure no longer offers perpetual licenses (existing ones are not affected). Every subscription includes unlimited publishing and hosting on Axure Cloud. The product page offers a free, fully functional 30-day trial for PC or Mac. There is a 60% discount for nonprofits and educational institutions and 25% for government agencies, and qualified students and educators at accredited schools can use the Team edition free of charge. The pricing page does not detail the billing period behind the 29 and 49 USD figures; confirm it before budgeting.

When is Axure NOT the right choice?

• If the prototype is linear and visual. If there are only screens linked together with no logic, the complexity does not pay off, and Figma or Balsamiq are faster.
• If the logic is moderate. Figma supports variables, expressions, and conditional actions in prototypes, and if your team already designs there, you may not need another tool.
• If there is no Windows or Mac. Axure is a desktop application with no Linux version.
• If several people must edit at once and the budget is tight. Co-authoring is only on Team, at 49 USD per user.
• If the budget does not allow per-user subscriptions. There is no perpetual license anymore.

To compare with prototyping in Figma, also look at ProtoPie, which focuses on interactions with gestures and sensors.

Example

Illustrative example: a loan application form with three paths depending on declared income.

• Problem: the flow has duplicate screens for each customer type, and it is hard to see whether the “insufficient income” path has a useful exit.
• With Axure: a variable stores the customer type, and a dynamic panel shows one of three states. A conditional case decides whether the application goes to review or is declined with an alternative.
• Test: the team walks through all three paths with realistic sample data and finds that the decline offers no useful next step.

The prototype does not decide the product, but it shows what is missing. That is its value.

If you want to explore how AI fits into prototyping, the article on prototyping with AI covers what can be generated and what should be reviewed by hand. For the artifact itself, the article on prototypes gives the general framework.

Common mistakes

• Using Axure for linear screens that Figma would handle in a third of the time.
• Forgetting case order and breaking the logic without noticing.
• Deleting an event without reviewing its cases and actions.
• Testing only the happy path.
• Duplicating screens instead of using dynamic panels.
• Budgeting without confirming the billing period and what each plan includes.

Sources

• Axure, Axure RP (checked November 12, 2026)
• Axure, Pricing (checked November 12, 2026)
• Axure, RP 11 release history
• Axure, Introducing Axure RP 11
• Axure Docs, Events, cases and actions
• Axure Docs, Variables
• Figma, Use expressions in prototypes