Hey Vincent! Lovely to see you — you might not know me but I, like many others, know you from the many topics you’re present on. Thanks for doing such a wonderful job.
I get what you’re saying and my thinking is the same: if it works, it works. The discussion about this or that stack can be just noise, unless we’re talking about a specific super impactful use case (high scale, high impact etc).
That said, I wanted to see if anybody’s gone down this route before and what caveats might be there.
Yep! So the classical scenario you’ll know is
- Design (with any tool: Sketch, XD, Figma etc) built by designer
- Front-end is built by FE dev
- Back-end is built by BE dev
Since Webflow kinda intertwines the FE dev role and the designer role (in my case, it turned me from a designer to a designer+FE person), I was thinking whether the output of a Webflow project can be taken straight to the BE developer, and then to deploying the app.
Of course, that implies super fancy stuff like a library won’t be used (can we…? say chartJS as a random example?), or that we won’t be able to make a single page application… but for a no-code solution it might be just the right tool for the right people who are just starting off.
What do you think @vincent ?