I would love to be able to create one prototype across the pages in a file that resembles an actual website. This would be ideal for bigger projects and would be easier to maintain as well. We can connect the component libraries across all the pages anyways. A way to connect the prototype would be great in my opinion and that will give Figma a big leg up on other platforms.
What do you guys think?
+1 vote, it would greatly help me as I have a LOT of versions for the app we’re doing, it would be great to put them all up to date with an easy interaction without navigating each 20ish pages one by one
This would be huge, and it’s been discussed for 4 years now…
This lack of functionality forces our team to create two separate files—one master and one for the prototype—breaking the best practice of maintaining a single “source of truth.”
I would love to be able to create one prototype across the pages in a file that resembles an actual website. This would be ideal for bigger projects and would be easier to maintain as well. We can connect the component libraries across all the pages anyways. A way to connect the prototype would be great in my opinion and that will give Figma a big leg up on other platforms.
What do you guys think?
For example, creating a seamless navigation experience, as discussed in this https://www.cogniteq.com/blog/navigation-app-development-step-step-guide could benefit greatly from having a unified prototype. It could allow designers to visualize and test the user journey from one screen to another, ensuring that all transitions and interactions are smooth and intuitive, which is crucial for navigation apps.
I’ve worked on a few projects where having a connected prototype across pages would have saved so much time, especially when trying to tweak designs and keep everything aligned across screens. If Figma added a feature that allows you to connect the components and interactions seamlessly across pages, it would really set them apart from other platforms. The flexibility to work on a cohesive, interactive prototype that mirrors an actual website would be so useful! Plus, it would be great to be able to see how components interact from one page to another without having to jump between separate files. This would help avoid those annoying inconsistencies and make collaboration much smoother. I’m definitely on board with the idea!
😵💫 I can’t believe that this hasn’t been addressed yet; 4 years, wow.
I did, however, figure out a pretty simple workaround — at least for navigational/link purposes — that being [Action] > Open Link and linking to the relevant prototype frame. It definitely won’t work for everything, but it works swimmingly for navigating page-to-page in some situations.
@Figma PLEASE help us with this feature!!
Hi, currently trying to optimize a VERY large file, for our company’s SaaS app, and I wish this feature existed so we could separate each main submenu of our webapp into a Page.
We used to prototype for client demonstration so the “open link” workaround isn’t acceptable as the refresh takes you out of the prototype, but the slowness of the file is becoming problematic, and most of it is due to how much content is on the same page (checked with the memory tool).
+1 for that feature
Ridiculous that a simple feature like this hasn’t been implemented for years. I just left Proto for Figma and it was a huge let down to discover I could not set navigation between pages/screens. Simply unacceptable. I mostly design web pages, and there’s absolutely a need to have a way to “click-through” from Page A to Page B in the prototype.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
