10 ms·
congrats on launching! i confess i struggled to get the value proposition at first. i tend to look for as simple as possible positioning. people can get behind
by swyx 6y ago
congrats on launching!
i confess i struggled to get the value proposition at first. i tend to look for as simple as possible positioning. people can get behind "no code", people can get behind Jamstack/"empowering developers", but pitching the messy middle is very tricky in my mind.
i think where i was swayed is less in the custom components part, but more the integrations with airtable/other APIs. you might have a decent shot of doing that better than wordpress and webflow can (although both are formidable already). as a marketer with some dev time i might find that very useful.
with the custom components piece, i'd lean into more of a marketplace approach so that people can reuse components made by others/pick them off the shelf, and people who maintain components might even be able to make money from the weweb users who are using them!
as for embedding React in Vue - what are the constraints to simply mounting the React component on a DOM node rendered by Vue? are you solving for SSR or something? its not clear from your description what exactly you are struggling with.
- raphael-gold 6y agoYes, back-end integrations seem to be one of the main reasons why users decide to adopt us. Being able to add their own components is also one of the big reasons. Also, being able to customize the front-end without limits also reassures developers who were mainly interested in using back-end integrations. I really like your point of vue on the marketplace approach and tend to agree. Most users will want off the shelf elements that they can customize easily (especially marketers). We will start working on the marketplace this Spring. As for react in vue, our problem really lies into the pre-rendering -> the main problem is that we have react in a vue.js environment which can create performance problems and conflicts between the two frameworks.