top | item 33888069

(no title)

yaaang | 3 years ago

It depends on how extensive the edits/created components are that you want to allow the non-developer to make.

https://plasmic.app experimented with bringing together design+code in this way, but we found it didn't take hold outside of small visual tweaks. We ended up taking a different approach to this specific problem - letting you build screens out of React components from your codebase (and have the screens rendered back into your app). This has worked out much better for us, as the surface area for coordination between the developer and non-developer is much narrower and less brittle as a workflow (and at the same time doesn't put an IDE in front of the non-developer).

discuss

order

No comments yet.