{"id":56,"date":"2020-01-24T08:50:40","date_gmt":"2020-01-24T07:50:40","guid":{"rendered":"https:\/\/sketch2react.wordpress.com\/2020\/01\/24\/the-rise-of-lowcode-nocode\/"},"modified":"2020-06-18T07:42:33","modified_gmt":"2020-06-18T07:42:33","slug":"the-rise-of-lowcode-nocode","status":"publish","type":"post","link":"https:\/\/sketch2react.io\/blog\/the-rise-of-lowcode-nocode\/","title":{"rendered":"The rise of #lowcode & #nocode"},"content":{"rendered":"

Thoughts from being right in the middle of\u00a0things<\/h4>\n
\n


\n<\/figure>\n

F<\/span>or 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<\/em>. The hashtag being used is, surprise surprise: #nocode<\/strong>. Right about the same time I saw another tag being used #lowcode<\/strong>.<\/p>\n

What these fine makers are most likely really saying is \u201dwe do most of the heavy lifting & and you do less<\/em>\u201d.<\/p>\n

Thing is, I didn\u2019t realize that we, as Team Sketch2React<\/a>, also are part of this movement, trend\/era or whatever it is. I\u2019m a slow learner, so please forgive me. ?<\/p>\n

So actually I\u2019ve written tons and tons of articles about it without even realising it. Go figure hah!<\/p>\n

How is Sketch2React #nocode?<\/h3>\n

Actually about the whole workflow<\/strong> from a static design file to a real code prototype is without you touching a single line of code<\/strong>.<\/p>\n

Everything is done inside Sketch using our\u00a0markup.<\/p><\/blockquote>\n

Learning it is easy,<\/strong> you are in safe hands, we have a ridiculous huge amount of both written<\/a> & recorded tutorials<\/a>.<\/p>\n

The only time you step outside this \u201dcomfort zone\u201d is when you have exported to React or HTML5. Then it\u2019s a matter of following a few easy steps available in our Docs portal<\/a>.<\/p>\n

Actually now that we are very soon releasing Sketch2React 1.6+ for free, we think we\u2019ll see a new rise of users, trying out prototyping for React & HTML5 for the very first time. Excited? As are we! ??\u2705<\/p>\n

I\u2019m planning to record at least one tutorial aimed at getting your over-complicated design files (trust me they are<\/em>) into real code React prototypes. We\u2019re going to cheat of course, that\u2019s the whole philosophy behind a prototype ?\u2705<\/p>\n

How is Stratos\u00a0#nocode?<\/h3>\n

For example, you just add the syntax & markup {H1}<\/strong> to a styled text layer in Sketch<\/strong> and we give you a couple of things automagically:<\/p>\n

    \n
  1. We create a Styled Component that\u2019s production-ready<\/strong>\n<\/li>\n
  2. We create a NPM project<\/strong> in the background<\/li>\n
  3. We create a React web app<\/strong> in the background<\/li>\n
  4. We create a HTML5 web app in the background<\/li>\n<\/ol>\n

    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\u2019s 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.<\/p>\n

    The differences between Sketch2React &\u00a0Stratos?<\/h3>\n

    So<\/span> by now you may be wondering what\u2019s the main difference between Sketch2React & Stratos?<\/p>\n

    There are a few philosophical differences & technical ones. People love bullet points so here we go:<\/p>\n