I think that the entire breakpoint system in @webflow should be re-thought. It is currently based on arbitrary breakpoints, which is the incorrect conceptual model for this feature, in my opinion. The breakpoints are not completely arbitrary, as they try to represent an average size for different device types, but even this averaging concept is now too limiting for modern web design, as the number of device types and sizes has exploded in recent years.
I do like the stretching feature in the device pane that shows me different device names at different sizes, but i can only see how the design will behave, not add breakpoints and make changes when needed.
I think adobe muse has a better conceptual model, which is to allow the user to add breakpoints when the design breaks, as this represents the best way to mitigate the endless sea of devices that exist in the world. If we focus on the design breaking we then have to worry less about the type of device, as our focus is on what the design needs at any given point in time. Adobe implements their solution by having what is essentially a mirrored pixel count strip on top, which the user can click on add a breakpoint when the design breaks, which seems to be a very elegant and versatile implementation of the concept.
The current breakpoint implementation in @webflow is starting to become more and more difficult to work with as my designs get more intricate and exacting. I would love to be able to add breakpoints anywhere, as I can with code, without limitations, and can serve a wider array of devices with a simpler conceptual model.
This, of course, is mirroring the opinions of fine folks like Rachel Andrew, Jen Simmons, Brad Frost, Ethan Marcotte, etc, on the subject. Nothing new from me
CC @PixelGeek, @thesergie, @callmevlad… thoughts?