Hey Sadok, you're right - the web has the incredibly hard property of having to respond to a wide range of screens / resolutions / capabilities. That makes creating for this medium much harder (hence why we have to write code now to deal with all the browser differences), but to me that means it's even more important to create good visual tools around it.
Browser are becoming much more standardized than in the first 20 years of the web (see things like Acid3 compliance), and internally at Webflow we've gone from seeing 10%+ of support requests say things like "this looks different in Browser X" in 2013 to < 1% today. Part of that is because Webflow itself normalizes cross-browser behavior in many cases. For example, one user can report a browser inconsistency, which we fix or polyfill centrally, and everyone else benefits from never having to run into that issue again. Whereas if you were writing code by hand, you would have to know how to research and fix each and every one of those issues yourself.
Also, websites don't need to look the same on every browser, and I think the concept of progressive enhancement is a powerful one. I think it's wonderful that websites built 25 years ago can still be rendered on today's browsers, and many sites built today can be read by 10+ year old browsers (even if they don't look exactly like the designer intended). That's a powerful advantage of the web that other distribution platforms (e.g. mobile apps) can't quite match.
But again, you're right - the web has a ton of challenges that still need to be abstracted and solved. But that doesn't mean we should give up and stop trying :)
Hey Sadok, you're right - the web has the incredibly hard property of having to respond to a wide range of screens / resolutions / capabilities. That makes creating for this medium much harder (hence why we have to write code now to deal with all the browser differences), but to me that means it's even more important to create good visual tools around it.
Browser are becoming much more standardized than in the first 20 years of the web (see things like Acid3 compliance), and internally at Webflow we've gone from seeing 10%+ of support requests say things like "this looks different in Browser X" in 2013 to < 1% today. Part of that is because Webflow itself normalizes cross-browser behavior in many cases. For example, one user can report a browser inconsistency, which we fix or polyfill centrally, and everyone else benefits from never having to run into that issue again. Whereas if you were writing code by hand, you would have to know how to research and fix each and every one of those issues yourself.
Also, websites don't need to look the same on every browser, and I think the concept of progressive enhancement is a powerful one. I think it's wonderful that websites built 25 years ago can still be rendered on today's browsers, and many sites built today can be read by 10+ year old browsers (even if they don't look exactly like the designer intended). That's a powerful advantage of the web that other distribution platforms (e.g. mobile apps) can't quite match.
But again, you're right - the web has a ton of challenges that still need to be abstracted and solved. But that doesn't mean we should give up and stop trying :)