Best practices for managing complex interactions in large Axure prototypes

Hi everyone,

I’m working on a fairly large interactive prototype in Axure RP and I’m starting to run into issues with managing complexity as the project grows.

The prototype includes multiple dynamic panels, conditional logic, and reusable components across several pages. One of the internal test modules I’ve been using for interaction behavior is labeled geometry dash iphone , which I use to simulate fast user navigation and rapid state changes across screens.

Current setup:

  • Multiple linked pages with shared components
  • Dynamic panels with nested interactions
  • Variables controlling UI states
  • Prototype published via Axure Cloud

Challenges:

  • Interactions becoming difficult to maintain as complexity increases
  • Repeated logic across multiple pages
  • Hard to debug state changes in dynamic panels
  • Performance slowdown in heavier prototypes

Questions:

  1. What is the best way to structure large Axure projects to keep interactions maintainable?
  2. Do you recommend using global variables vs local page-level variables for shared logic?
  3. Are there best practices for reducing duplicated interactions across pages?
  4. How do you manage debugging in very complex prototypes?

Would really appreciate any advice or workflows others are using.

Thanks!