|
|
|
|
|
|
by jonshariat
2509 days ago
|
|
|
I think the main differentiator for webflow is the user experience of their tool. Its very well done, intuitive, easy to use but doesn't oversimplify. If designing app front ends was this easy it would be awesome. In my mind the hook into their hosting service is keeping them from their potential. If they had a stand alone tool I could use or a corp lvl tool, it could be big. That being said, maybe there is more money in it for them to do it this way. But as a designer I see so much missed opportunity to unit design and code for front end work. (And eventually basic app functionalities) |
|
|
It does have serious limitations though. Many times I have needed to tell clients: "you can't do that because it's not (yet?) supported in Webflow". For example, you can't have "lists of lists" (i.e. nested maps or loops in JavaScript), which makes a huge number of designs virtually impossible. There are also random CSS properties, like vertical text alignment, missing from the Webflow interface, requiring custom coding, and they have arbitrary maximum file sizes for a number of assets. With Webflow, you either stay within their limitations, or you have to do a lot of things in custom code embeds.
Despite this, I've found that, even with Webflow's brutal price structures, working around those limitations in order to stay on Webflow's infrastructure has generally been worth the pain compared to spending a whole lot more time/money on doing things by hand, especially because my clients have a tendency to completely change their mind several times during the process. I'm not yet aware of anything with a shorter iteration time — there's CodePen, but its hosting features are even more limited than Webflow's...