Thoughts from being right in the middle of things
For the last couple of years I have seen a hashtag being used more and more. Specially amongst users and makers of so called no code tools. The hashtag being used is, surprise surprise: #nocode. Right about the same time I saw another tag being used #lowcode.
What these fine makers are most likely really saying is ”we do most of the heavy lifting & and you do less”.
Thing is, I didn’t realize that we, as Team Sketch2React, also are part of this movement, trend/era or whatever it is. I’m a slow learner, so please forgive me. ?
So actually I’ve written tons and tons of articles about it without even realising it. Go figure hah!
How is Sketch2React #nocode?
Actually about the whole workflow from a static design file to a real code prototype is without you touching a single line of code.
Everything is done inside Sketch using our markup.
Learning it is easy, you are in safe hands, we have a ridiculous huge amount of both written & recorded tutorials.
The only time you step outside this ”comfort zone” is when you have exported to React or HTML5. Then it’s a matter of following a few easy steps available in our Docs portal.
Actually now that we are very soon releasing Sketch2React 1.6+ for free, we think we’ll see a new rise of users, trying out prototyping for React & HTML5 for the very first time. Excited? As are we! ??✅
I’m planning to record at least one tutorial aimed at getting your over-complicated design files (trust me they are) into real code React prototypes. We’re going to cheat of course, that’s the whole philosophy behind a prototype ?✅
How is Stratos #nocode?
For example, you just add the syntax & markup {H1} to a styled text layer in Sketch and we give you a couple of things automagically:
- We create a Styled Component that’s production-ready
- We create a NPM project in the background
- We create a React web app in the background
- We create a HTML5 web app in the background
See? All of these amazing things are created by us the very same second that you add our markup inside of Sketch. That is #nocode, at least for me. But it’s a devious hashtag that also can be interpreted that you, as a user, need to do very little to achieve great things. We all know that is never, ever true.
The differences between Sketch2React & Stratos?
So by now you may be wondering what’s the main difference between Sketch2React & Stratos?
There are a few philosophical differences & technical ones. People love bullet points so here we go:
- Sketch2React is perfect for simple real code prototypes
- Stratos is perfect for complex prototypes & production-ready React components
We haven’t yet decided if Stratos is going to replace Sketch2React or if they will co-exist. They serve different masters and tasks. We’ll let the users decide about that, we’ll use one of my fav quotes:
“When in doubt, do nothing”
Don’t even know who said that but I really like it.
Our Youtube with lots of tutorials
https://www.youtube.com/channel/UCFyKi5oCfeTLR1wcCRk89_g/featured
Our Docs portals
Sketch2React for Sketch
https://www.youtube.com/channel/UCFyKi5oCfeTLR1wcCRk89_g/featured
Stratos for Sketch
https://www.youtube.com/channel/UCFyKi5oCfeTLR1wcCRk89_g/featured
Btw our Stratos docs are not 100% finished yet since we are continuously transferring/translating components from Sketch2React V1 into Stratos.
All the best
Juan, Team Sketch2React