But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)?
Naming is fun.
But this tool is related to that ui/ux version of Sketch (but with/for React), and not the mis-named Sketch (that was for React)?
Naming is fun.
- react-dom
- react-native
- react-vr
- react-hardware
- react-blessed
- react-three
- react-aframe
etc
it felt like the right thing to do was a descriptive "this is what it is" name rather than a "marketing name" that would be more confusing.
Yeah, about that.
Are you saying that the "React Sketch.app" in the title is/should/will be "React Snack.app?"
Sketch.app - Description: Most popular native mac app for designing UIs - Built by: Bohemian Coding
react-sketchapp - Description: Convert a UI written in react-primitives to sketch. react-primitives is a subset of react-native. - Built by: Airbnb
I want to say Snack has nothing to do with react-sketchapp, but unfortunately they do share a couple of things. The developer/user of both tools will write code that is largely compatible with each other, basically a shared subset of react-native. Then, there's the whole confusion with the name Sketch. Snack used to be called Sketch. react-sketchapp uses "Sketch.app" as a rendering engine and editing interface. "Sketch.app" is basically the next program in the workflow for the user of react-sketchapp.