3 ms·
We’ve been seeking the “holy grail” being web dev tools our design team can use. What we’re also seeking is a way that limited end-clients could also use the t
by evolve2k 6y ago
We’ve been seeking the “holy grail” being web dev tools our design team can use.
What we’re also seeking is a way that limited end-clients could also use the tool to make minor copy changes (A poor mans CMS if you will).
How might your tool support the three different users.
1. Devs who need it to create handcrafted grade code
2. Designers seeking to drag and drop with flexibility
3. Power users seeking to update copy inside the same platform
Thx
- xyzzyrz 6y agoPlasmic's user base is in fact split about 50/50 designers/developers. And "visual CMS" exactly describes our most common use case—letting non-developers publish changes. 1. Developers can use it as a UI builder, removing the pain of things like CSS layout (for ex., we use Plasmic to build Plasmic; and engineers at companies small and large use it on their flagship websites/apps). 2. Designers versed in tools like Figma and Webflow are probably the segment with the highest "starting proficiency." 3. Currently Plasmic is most comfortable for designers and developers, but we very much want to accommodate the end-client persona (a "copy-only-mode" is on our roadmap). Prioritization is heavily influenced by early users, so would love to hear your feedback on how this works for your team!