

So when a browser window is resized, although elements will move around, it should not affect the text size. This is similar to what we do when we set our constraints in Figma. I could be wrong, and would gladly be corrected, but from my understanding real, coded web pages should behave responsively as a browser window is resized, they should not scale up or down proportionally. Not sure if I’ve missed something here, but this is still a problem. However, if I view the prototype and play around with the size of the browser window, it doesn’t act in the same way. In Figma, I can play around with the frame size, and it will act in a responsive way. It’d be great if, when users are viewing the prototype in the browser, the design would behave in align with the responsive design you’ve built. HOWEVER, this means I have to change the size of each frame, and if you’re working with a prototype with lots of frames, this would take forever. This solves half the problem - if a customer asks to see the design in a different desktop size, I can simple resize the frame, and it will change in a responsive way, and there won’t be any fiddling around to do. I always take responsiveness into consideration, but I rarely took the time to properly set my constraints and grids, as I rarely had to demonstrate with my prototypes how the responsiveness would work. Thanks for the response, I’ve somehwat discovered a solution to this as I went down the rabbit hole of grids and responsive design.
