- Inevitably in any real-world project, various parts of the UI need to be changed/overridden from code. But you cannot iterate on the design once ejected, which is a significant limitation for any product that requires iteration.
For building prototypes, it works great, and it makes user-testing a "happy path" nice and breezy.
That said, would love to see/hear more about the projects you've shipped to production!
We are in a very fortunate position financially (multiple years of runway), and I am YZ. :) We also have companies big and small relying on Plasmic in production. Lastly, you fully own the code that you generate, and can always eject with clean React.
- There's nothing stopping you from using it in production, but it isn't designed for this. What you create does not even use real layout, does not use normal HTML elements, etc.: see https://www.framer.com/support/using-framer/creating-real-ap....
- Inevitably in any real-world project, various parts of the UI need to be changed/overridden from code. But you cannot iterate on the design once ejected, which is a significant limitation for any product that requires iteration.
For building prototypes, it works great, and it makes user-testing a "happy path" nice and breezy.
That said, would love to see/hear more about the projects you've shipped to production!
(Disclaimer: I work on https://www.plasmic.app.)