Skip to main content
Nazim_Can_Tunc
January 31, 2021

Multiple Flows Should Have Different Device Frames

  • January 31, 2021
  • 207 replies
  • 35422 views

It would be great if we could select different device frames for each flow. This would give huge benefits to those who design responsive websites side by side.

207 replies

Simon_Loizeau
March 22, 2024

Definitely agree. All my frames sizes / breakpoints are defined in variables. So it should be possible to set the device model in variables too?
In my prototype, if I click on “iOS user” or “Android user”, it should display the right device model for the same layout.

Marijn
New Member
March 22, 2024

Same here!

March 28, 2024

Sill an isue 3 years laters : we still can’t use the flows for deaktop/mobile presentation and need to send 2 diffent URL for clients / présentations

MoniqueD
April 11, 2024

Jij hier 😉 - and yes, agreed. still struggling with this.

Jeroen_Vos
April 12, 2024

🙌 Small world!

Rajeswara_Rajan
New Member
April 22, 2024

It would be better if we were able to set device for each and every flows we create since the device setting becomes common for the whole file we were unable to have separate devices set for mobile and desktop in same device

Annika_Wiedel
New Member
April 23, 2024

Would love to see this feature as well.

April 29, 2024

I’m working on a responsive website and this feature would help me work faster by allowing me to check all breakpoints side by side.

April 30, 2024
Neil_Johnson
New Participant
May 3, 2024

I wish someone from Figma would respond. This shouldn’t take 4 years to develop. They’ve intentionally ignored it in light of other changes for some reason yet it’s a fundamentally essential part of client review for responsive design. Are they saying this functionality is not important?

Having to develop designs side by side in a sandbox page and then move them to other pages just to review the flow accurately is a terrible process. Frames have to be constantly copy and pasted back and forth possibly introducing error.