<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Rootcode - Medium]]></title>
        <description><![CDATA[Official blog of rootcode - Medium]]></description>
        <link>https://medium.com/rootcodelabs?source=rss----1e3cfe39ccfd---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Rootcode - Medium</title>
            <link>https://medium.com/rootcodelabs?source=rss----1e3cfe39ccfd---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:22:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/rootcodelabs" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[React Native Tips and Tricks (Part 1/2)]]></title>
            <link>https://medium.com/rootcodelabs/react-native-tips-and-tricks-part-1-2-34265bb39b65?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/34265bb39b65</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[reactive-programming]]></category>
            <dc:creator><![CDATA[Pabashani Herath]]></dc:creator>
            <pubDate>Fri, 08 Jul 2022 09:17:16 GMT</pubDate>
            <atom:updated>2022-07-08T09:17:15.980Z</atom:updated>
            <content:encoded><![CDATA[<h4>A beginners guide to the best practices to follow when coding</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Jr4ptCx2n9WutTcm.png" /></figure><p>The goal of this article is to present you with React Native programming tips that you and your team may use. Some of these suggestions are exclusive to React Native, while others are more generally associated with mobile application development or any development. So, let’s get this party started right away!</p><h4><strong>01. Expo or No Expo?</strong></h4><p>Are you planning to create cross-platform apps with React Native? When you start building apps with React Native, you’ll encounter the decision of whether or not to use Expo.</p><p>Let’s see the advantages and disadvantages of using Expo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IHVswP1yyW3nifUi.png" /></figure><h4><strong>Advantages</strong></h4><ul><li><em>Easy to use</em></li><li><em>Immediate results</em></li><li><em>Everything is covered by Expo</em></li><li><em>Nice documentation from Getting started to all API Docs</em></li><li><em>Live reload while in development</em></li><li><em>Library linking (react-native link) is not necessary</em></li><li><em>Test directly on the device both for iOS and Android (through the Expo container app)</em></li><li><em>Develop from Windows/macOS or whatever (you only need nodejs and an internet connection)</em></li></ul><h4><strong>Disadvantages</strong></h4><ul><li><em>The build is done by Expo, in their cloud</em></li><li><em>Native modules not supported</em></li><li><em>Expo apps don’t support background code execution (source docs.expo.io)</em></li><li><em>Javascript source is hosted in their cloud</em></li><li><em>The app size can be large (around 30MB)</em></li></ul><p>So the summary of this is, make sure not to use the Expo for complex or long-term projects. It is the best tool for newcomers to React Native technology and people who are doing simple projects.</p><p>As an example, if you are preferred to do a project using Expo, first thing is to make sure every requirement that you are supposed to use within your project is available in Expo libraries. Otherwise, there is no point in using it.</p><h4>02. <strong>Folder structuring</strong></h4><p>The folder structure in any project is very important for every developer. Because a good folder structure will give a clear and clean idea about your project and organizing within components and everything inside it.</p><p>As an example;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*SYRHbFgFuyN1JI-uyB2QwA.png" /></figure><p>As a developer, I preferred to use the Atomic design system for my projects as a folder structuring method.</p><p>So,<br><strong>What is this Atomic Design?</strong></p><p>Brad Frost created the term “atomic design” to describe a way of constructing design systems. About 5 years ago, he introduced the concept of atomic design. It is the methodology that can help you create modular designs faster. Using chemistry as a metaphor, this methodology examines the links between the many pieces of the system and how they interact.</p><p>There are five distinct levels in atomic design:</p><ol><li>Atoms</li><li>Molecules</li><li>Organisms</li><li>Templates</li><li>Pages</li></ol><p><strong>Why is this important?</strong></p><ol><li><strong>Make the process of designing modular designs go faster.</strong></li></ol><p>Now, instead of walking through every single page to alter the layout on every single instance of our card design, we can just go to our atoms and molecules and make changes there, and everything will be updated.</p><p><strong>2. Improved communication and execution</strong></p><p>Furthermore, the atomic design is the means through which we can work together on the same project. Any modifications we make will be reflected in everyone else’s work if we update our libraries with the most recent variants of all these reusable components.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/980/0*7JqeU-4dqPJCNiD7.png" /><figcaption>Atomic design methodology</figcaption></figure><ul><li><strong>Atoms </strong>are UI elements that can’t be broken down any further and serve as the elemental building blocks of an interface.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*75YrcEPns_lGiHtw59q41g.png" /></figure><ul><li><strong>Molecules </strong>are collections of atoms that form relatively simple UI components.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wfNwn1aZSy9_9rGWBTKrvw.png" /></figure><ul><li><strong>Organisms </strong>are relatively complex components that form discrete sections of an interface.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DJPqc292I4gwQ1pMI-ZzrQ.png" /></figure><ul><li><strong>Templates </strong>place components within a layout and demonstrate the design’s underlying content structure.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AzT-wNQj78vxamymz5zL9Q.png" /></figure><ul><li><strong>Pages </strong>apply real content to templates and articulate variations to demonstrate the final UI and test the resilience of the design system.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NfldcFvteYhpIbweJLXlrA.png" /></figure><h4>03. <strong>Use ESLint &amp; Prettier</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zIqgePghovYVujDz.png" /></figure><blockquote>Prettier takes care of your code formatting.<br>ESLint takes care of your code styles.</blockquote><ul><li>First, make sure you have Prettier and ESLint installed. You can install them on a per-project basis or globally.</li><li>Second, install the Prettier and ESLint extension/plugin for your editor/IDE.</li><li>Third, install two more packages that are in charge of combining Prettier and ESLint (Only single quotes are used by Prettier, and the line length is set to the specified amount of characters. ESLint, on the other hand, requires a lot of configuration from you because it isn’t as opinionated as Prettier. Therefore, instead of adding all the ESLint rules ourselves, we can use the most popular <a href="https://github.com/airbnb/javascript/tree/master/packages/eslint-config-airbnb">code style guide for JavaScript published by Airbnb</a>. You can install it with all its dependencies)</li></ul><blockquote>npx install-peerdeps — dev eslint-config-airbnb</blockquote><ul><li>Last but not least, set the Prettier rules in your ESLint configuration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/0*uRXP7tvfNvPnP3Z7" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/0*L111zsijxDUQNcjV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*LKXLbmKQrV_mXXv_.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/0*3_hMnJ38hCNuLRUl" /></figure><h4><strong>04. On using external libraries</strong></h4><p>If there is a library out there that satisfies your needs and isn’t abandoned, it’s better to use it instead of reinventing the wheel. You’ll save your precious development time for something else. However, you do need to do some research on the libraries you plan to use.</p><p>As a rule of thumb, if learning to use an external library is going to take more of your time than making everything yourself, you should stay away from it.</p><p>Sometimes you will want to change something in an external library. <strong>Do not edit it directly in the node_modules/ folder.</strong> That folder is supposed to be ignored by version control anyway, so if you change the code directly, your teammates will not see your changes. In addition, an npm update action will overwrite your modifications. The solution is to either fork the original repository and link your project to your own repository where you made the changes (and even make a PR to the original author if you want to help!), or if the library is very small (one file), you can copy/paste it as a component in your own project and then edit it locally.</p><p>When you are selecting a library, you have to ask the below questions yourself to find out the best library which can fulfill your requirement.</p><ol><li>Is it active and regularly maintained?</li><li>Does it have a good rating?</li><li>Is it well tested?</li><li>Does it have a lot of issues?</li><li>Does it support both iOS and Android?</li></ol><h4>06. <strong>Be Very Careful With Copy/Paste</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/360/0*ul5aYZEeQ2B_Ktfk.jpg" /></figure><p>You might want to copy a component, function, or some other piece of code and modify it. This is where a lot of unexpected errors happen because it can be very hard to notice a single property or value that you forgot to modify. So always be on your toes while doing any type of copy/paste.</p><h4>07. <strong>Avoid using Find/Replace Functionality For Refactoring</strong></h4><p>It might seem like a faster solution if you need to quickly change a bunch of things on your project quickly, but there are way too many pitfalls you can (and trust me, you will) fall into. So just don’t even bother with it, and do things the old-fashioned way, or refactor using the refactoring tools provided by your IDE.</p><h4>08. <strong>Use The Most Comfortable Ide As Your Editor</strong></h4><p>React Native is the latest cross-platform mobile development trend, allowing us to create high-quality, native, and powerful mobile apps with JavaScript. It’s been less than a year since Facebook Inc. introduced the open-source React Native project, and there’s been a lot of progress in terms of development, support, plugins, tools, and integrations.</p><p>There are so many code editors for development that it’s often tough for me to pick the best one for a given programming language. I did some exploring when working with React Native and discovered some great IDE/editors for mobile app development. I’ve included information about the editors, plugins, and packages that are special to React Native.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZY1MH4v3KK-P4WPz.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MHngpjcQJoKL-Rlg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4UYJMa3N8ViAzg5p.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Qlh5Yh5eAaOn58Pl.png" /></figure><h4>09. <strong>DRY (Don’t Repeat Yourself) everywhere</strong></h4><p>If I had to name one programming principle that is a basis for everything else in software development, it would be the <strong>Don’t Repeat Yourself </strong>principle.</p><p><strong><em>Don’t Repeat Yourself: </em></strong>To write your code in a non-repetitive manner. Extracting and expressing shared code between components as a module that can be imported and utilized in other components.</p><p>When you need to update the functionality of a code that is being used in several places. All we have to do now is alter that common code, and the changes will be reflected in all components that require it.</p><h4>10. Extract reusable logic into custom hooks</h4><h4>According to the React docs,</h4><blockquote>Hooks allow us to reuse stateful logic without changing our component hierarchy.</blockquote><p>They’re a superior alternative to the strategies that were previously employed in conjunction with class components. Higher-Order Components or render props may be familiar to you if you’ve been coding for a long.</p><p>It’s a good idea to develop a custom hook if you need to reuse stateful logic that has already been utilized in another functional component. You just invoke the hook as a function inside your components to encapsulate the logic.</p><p>Let’s look at an example where we need to change our UI based on screen size and want to retain track of the current window size when manually resizing the browser window.</p><pre>const ScreenDimensions = () =&gt; {<br>  const [windowSize, setWindowSize] = useState({<br>    width: undefined,<br>    height: undefined,<br>  });<br>  <br>  useEffect(() =&gt; {<br>    function handleResize() {<br>      setWindowSize({<br>        width: window.innerWidth,<br>        height: window.innerHeight,<br>      });<br>    }<br>    window.addEventListener(&#39;resize&#39;, handleResize);<br>    handleResize();<br>    return () =&gt; window.removeEventListener(&#39;resize&#39;, handleResize);<br>  }, []);<br>  <br>  return (<br>  	&lt;&gt;<br>    	&lt;p&gt;Current screen width: {windowSize.width}&lt;/p&gt;<br>        &lt;p&gt;Current screen height: {windowSize.height}&lt;/p&gt;<br>    &lt;/&gt;<br>  )<br>}</pre><p>As you can see, the answer is simple, and there’s nothing wrong with stating it this way.</p><p>Now comes the challenging part. Consider how we might apply the same logic to another component, rendering a distinct UI (one for smartphones and one for desktops) depending on the current screen size.</p><p>Of course, we could simply copy the logic and paste it in. However, as you may know from the DRY principle, this is not a good practice.</p><p>Let’s have a look at our customized hook:</p><pre>const useWindowSize = () =&gt; {<br>  const [windowSize, setWindowSize] = useState({<br>    width: undefined,<br>    height: undefined,<br>  });<br>  <br>  useEffect(() =&gt; {<br>    function handleResize() {<br>      setWindowSize({<br>        width: window.innerWidth,<br>        height: window.innerHeight,<br>      });<br>    }<br>    window.addEventListener(&#39;resize&#39;, handleResize);<br>    handleResize();<br>    return () =&gt; window.removeEventListener(&#39;resize&#39;, handleResize);<br>  }, []);<br>  <br>  return windowSize;<br>}</pre><p>Now let’s call it inside our <strong>Screen Dimensions</strong> component:</p><pre>const ScreenDimensions = () =&gt; {<br>  const windowSize = useWindowSize()<br>  <br>  return (<br>  	&lt;&gt;<br>    	&lt;p&gt;Current screen width: {windowSize.width}&lt;/p&gt;<br>        &lt;p&gt;Current screen height: {windowSize.height}&lt;/p&gt;<br>    &lt;/&gt;<br>  )<br>}</pre><p>This allows us to use any component to call the custom hook and preserve the return value (which is the current window size) in a variable that we can use inside the component.</p><h4>Wrapping up</h4><p>React Native is famous and widely used to create interactive UIs. React-Native comes with everything you need and you most likely wouldn’t need more. Initially, when you start a new project you will notice how easy it is starting from the setting up process: it’s very fast and only takes you one command line to run in the terminal and you will be ready to go. As a frequent user of React Native, the above-mentioned practice tips have helped me become an efficient programmer in terms of front-end development and I hope following them will help you to avoid a lot of problems in a long run. <br>For more tips and tricks, await part 2!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34265bb39b65" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/react-native-tips-and-tricks-part-1-2-34265bb39b65">React Native Tips and Tricks (Part 1/2)</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using React 18’s Suspense to Improve Code Quality of Web Loaders]]></title>
            <link>https://medium.com/rootcodelabs/using-react-18s-suspense-to-improve-code-quality-of-web-loaders-6fbb1dd5ab2a?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/6fbb1dd5ab2a</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Manusha Chethiyawardhana]]></dc:creator>
            <pubDate>Wed, 15 Jun 2022 03:53:49 GMT</pubDate>
            <atom:updated>2022-06-23T13:52:30.627Z</atom:updated>
            <content:encoded><![CDATA[<h4>An informative guide for using Suspense in React 18</h4><figure><img alt="Suspense in React 18" src="https://cdn-images-1.medium.com/max/1024/0*YJguTNgT_I2L1zIb" /><figcaption>Photo by <a href="https://unsplash.com/@lautaroandreani?utm_source=medium&amp;utm_medium=referral">Lautaro Andreani</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The React Suspense component was first launched with React 16.6, and it has been further expanded with the release of React 18. Initially, React Suspense could only be used for code splitting with the React.lazy API. However, the React team has worked to improve Suspense’s capabilities, with the goal of making it work with data fetching in the future as well.</p><p>This shows why it is critical for React developers to understand how to work with React Suspense. This article discusses how to improve the code quality of web loaders by using Suspense in React 18.</p><p>Let’s get started.</p><h3>Understanding React Suspense</h3><p>Let’s start with how the &lt;Suspense&gt; component works with the lazy loading components.</p><p>When using the Suspense component, you must provide a fallback option. It accepts any React components or even a string to render while the lazy component is loading.</p><p>Take a look at the example below, which uses the Suspense wrapper to display a typical loader until the &lt;LazyLoadComponent&gt; is ready.</p><pre>import { lazy, Suspense } from &#39;react&#39;;</pre><pre>const LazyLoadComponent = lazy(() =&gt; import(&#39;./LazyLoadComponent&#39;));<br><br>function MyComponent() {<br>  return (<br>    &lt;Suspense fallback={&lt;Loader /&gt;}&gt;<br>      &lt;div&gt;<br>        &lt;LazyLoadComponent /&gt;<br>      &lt;/div&gt;<br>    &lt;/Suspense&gt;<br>  );<br>}</pre><p>Within a single Suspense component, you can place one or more lazy components. You can also place multiple Suspense wrappers, and the one closest to a lazy component will be used.</p><p>To learn how to utilize this, look at the code piece below.</p><pre>&lt;Suspense fallback={&lt;MainLoader /&gt;}&gt;<br>  &lt;Suspense fallback={&lt;SideContentLoader /&gt;}&gt;<br>    &lt;SideContent /&gt;<br>  &lt;/Suspense&gt;<br>  &lt;MainContent /&gt;<br>  &lt;Suspense fallback={&lt;CommentsLoader /&gt;}&gt;<br>    &lt;Comments /&gt;<br>  &lt;/Suspense&gt;<br>&lt;/Suspense&gt;</pre><p>Suspense wrappers are used separately for the &lt;SideContent/&gt; and &lt;Comments/&gt; components in the example. As a result, if the &lt;MainContent/&gt; component is ready to load, it will do so regardless of whether the other two components have loaded. However, because all three components are children of the &lt;MainContent/&gt; component’s Suspense, the other two components will wait until the &lt;MainContent/&gt; component is loaded.</p><p>You can also look at the <a href="https://codesandbox.io/s/suspense-example-2-oeeitv?file=/index.js">code sandbox implementation</a> of the above example to gain a better understanding of it.</p><p>Now, let’s take a look at the enhancements Suspense received in React 18.</p><h3>Improvements for Suspense in React 18</h3><h4>Server-Side Rendering</h4><p>Suspense is no longer limited to lazy components, thanks to React 18’s new concurrent rendering. You can now use Suspense to wrap any React component in your component tree and specify their loading state declaratively.</p><p>In both of the previous examples, you can replace the lazy components with normal components and Suspense will still function according to the same principles.</p><p>This greatly simplifies the process of adding loaders to your web app.</p><h4>startTransition API</h4><p>Another new feature of React 18 is the startTransition API, and it can be used to improve the use of Suspense.</p><p>When switching between tab views, it would be undesirable if the previously displayed loader was shown to the user again after the user had seen the content. In such cases, useTransition() Hook and the startTransition() function can be used to display the old UI until the new UI is ready to be displayed. The startTransition API can help you avoid unexpected fallbacks by marking non-urgent UI updates as transitions.</p><p>Consider the following example code piece, in which two tab components, Cricket and Football, are wrapped in a Suspense component.</p><pre>const [isPending, startTransition] = useTransition();</pre><pre>function handleClick() {<br>  startTransition(() =&gt; {<br>    setTab(&#39;football&#39;);<br>  });<br>}</pre><pre>&lt;Suspense fallback={&lt;Loader/&gt;}&gt;<br>  &lt;div style={{opacity: isPending ? 0.8 : 1 }}&gt;<br>    {tab === &#39;cricket&#39; ? &lt;Cricket /&gt; : &lt;Football /&gt;}<br>  &lt;/div&gt;<br>&lt;/Suspense&gt;</pre><p>Here, if the useTransition() was not used, then the loader will appear each time the user switches between the tabs. However, when used as shown, the Cricket tab will be displayed until the Football tab is ready. During the transition, the user will be able to interact with the content as usual. The isPending value is used to determine whether the transition is currently occurring or not, and it is used in the example to change the opacity of the component while the transition is occurring.</p><h3>Why use React Suspense</h3><p>Without Suspense, we have to access the state and write a bunch more code to display loaders in React. The code piece below demonstrates how to display loaders without using Suspense.</p><pre>function MyComponent() {<br>  const [isLoading, setIsLoading] = useState(false);<br>  return (<br>      &lt;div&gt;<br>          {isLoading ? (<br>              &lt;Loader /&gt;<br>          ) : (<br>              &lt;AppContent /&gt;<br>          )}<br>      &lt;/div&gt;<br>  );<br>}</pre><p>At first glance, the change from isLoading ? to &lt;Suspense&gt; may not appear to be significant, but in large projects, it will make a significant difference. When React improves Suspense to work with data fetching as well, things will get even better.</p><p>Suspense has been added to React 18 for data fetching in the frameworks Relay, Next.js, Hydrogen, and Remix. Although Suspense allows for ad hoc data fetching, the React team does not recommend it as a general practice just yet.</p><h3>Conclusion</h3><p>This article covered the Suspense component, new improvements to Suspense in React 18, and why you should use Suspense. I hope you now have a clear grasp of the Suspense component. So, start using Suspense and improve the quality of your React code.</p><p>Thank you for reading, and happy coding!</p><figure><img alt="Using React 18’s Suspense to Improve Code Quality of Web Loaders" src="https://cdn-images-1.medium.com/max/1024/1*IzSCjj1nFGpWDsfrolaL-Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fbb1dd5ab2a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/using-react-18s-suspense-to-improve-code-quality-of-web-loaders-6fbb1dd5ab2a">Using React 18’s Suspense to Improve Code Quality of Web Loaders</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gestalt Principles applied on UX designs]]></title>
            <link>https://medium.com/rootcodelabs/gestalt-principles-applied-on-ux-designs-15100f4a7f14?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/15100f4a7f14</guid>
            <category><![CDATA[ui-ux-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[gestalt]]></category>
            <category><![CDATA[design-psychology]]></category>
            <dc:creator><![CDATA[Dewni De Silva]]></dc:creator>
            <pubDate>Fri, 20 May 2022 10:15:33 GMT</pubDate>
            <atom:updated>2022-05-20T10:15:33.509Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-nsVXYIOo02Sg56hYcNMGg.png" /></figure><p>Communication plays a central role in both user interface (UI) and user experience (UX) design and understanding how your users perceive and interpret your work is key. The Gestalt Principles can help you do so.</p><p>Developed by Gestalt psychologists, the Gestalt Principles describe how we interpret and process complex stimuli around us. They state that our minds have a tendency to group and organize elements and do so in predictable ways. The ways in which our mind does so are summarized in the Gestalt Principles.</p><p>Great designers recognize how much impact psychology can have in visual perception. By applying Gestalt principles, a designer can improve the clarity of the product since visual interfaces function based on associations between graphical elements.</p><p>In this guide, we will introduce you to the five Gestalt Principles and how they contribute to user-friendly design.</p><h4>Introduction to the 5 Gestalt principles</h4><p>If you’re here, chances are that you’re working to build a career in tech. Whether you’re an aspiring UX designer or a budding UI professional, the Gestalt Principles can help you to understand how the end user will interpret and navigate your work. Now let’s explore each of these principles in detail. The 5 Gestalt Principles we’ll take a look at are:</p><p><strong>Proximity</strong></p><p><strong>Similarity</strong></p><p><strong>Continuity</strong></p><p><strong>Closure</strong></p><p><strong>Figure/ ground</strong></p><h4><strong>Proximity</strong></h4><p>The principle of proximity states that we tend to perceive elements as a group when they are close to each other. This can be used for grouping similar elements, organizing content, and decluttering layouts. You can find this principle applied in many places such as navigation panels, banners, galleries, body text, and pagination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*WcB42FpF9mmm3SHIp9tLew.png" /></figure><p>In the example above you’ll find that closer that items are they form a relationship. In turn, they are easier to read and associate with each other.</p><p>To better understand this principle further, we can use a check-out form as an example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqSROy9Um3A1nHtJME3LIw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V6Vg_BHiGGwM0PdJvF9UYg.png" /></figure><p>These groups don’t sit inside boxes or have clearly delineated borders around them. Yet we perceive them as separate clusters of content. We do so because the elements in each section sit close to each other.</p><p>If you look a little closer, you’ll notice subgroups in each group. In group 3, each input field and label are perceived as a separate group. In group 4, each list item is perceived as another. This is the principle of proximity in action.</p><h4><strong>Similarity</strong></h4><p>Throw a bag of M&amp;Ms on a table and your mind will immediately start to group them by color. Red will be one group, green another, and yellow a third. We’re inclined to group elements that look like each other in terms of color, shape, or iconography.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JsmtC77sY6YcPd8L8E-avA.png" /></figure><p><a href="https://www.nngroup.com/articles/principles-visual-design/">Visual nomenclature</a> can help identify items that belong to similar or different categories while maintaining a consistent patterns across experiences.</p><h4>Continuity</h4><p>Ever notice how your eyes like to travel along lines, following and flowing with them? Our mind has a tendency to follow paths and group elements that are aligned with each other. The linear arrangement of rows and columns are good examples of continuity. As shown below they can be used in menus and sub-menus, lists, product arrangements, carousels, services, or process/progress displays. This is the principle of continuity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*unSHhNBjtmgxTTVuay3n5w.png" /></figure><p>In the example above it shows that This principle can be augmented by providing small visual clues (e.g. underlines) to indicate that the path of navigation path continues to a next level.</p><h4>Closure</h4><p>Individuals perceive objects such as shapes, letters, pictures, etc., as being whole when they are not complete. Specifically, when parts of a whole picture are missing, our perception fills in the visual gap. Since a whole is easier to process than multiple parts, we’ll fill in the gaps or connect the dots to complete implied shapes or images.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ljmRMlZyG8IkqgzZxG7E_A.png" /></figure><p>Loaders are a common element in user interfaces today. Whenever a product needs a little more time to complete a task, like refreshing or processing a payment, loaders will let us know the product is still working in the background.</p><h4>Figure/ ground</h4><p>The human brain often interprets ambiguous objects in more than one way, by bouncing back and forth between the alternatives seeking certainty. As a result, one view will become more dominant while the other one will get harder to see. Based on what our brain sees as the foreground and background this judgment can differ according to this principle; the figure talks about the focus of any composition, and the ground is the supporting background.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1012/1*wJkBfuNL3hmE5vq4QUXrzg.png" /></figure><p>Hence, This principle refers to our ability to visually separate elements on different planes of focus. There are three ways to effectively execute this, of these through layering, contrast, and information hierarchy.</p><h4>Wrapping up</h4><p>These principles should be a mainstay in your toolbox. If applied correctly, they can provide you with some quick wins out of the box. Sometimes we’re using these principles without even knowing it — and that’s because we’re following what our minds tell us is logical.</p><p>Once you’ve got a solid grasp on them, it is easy to see the Gestalt Principles everywhere you look in UI and UX design. The next time you pop open your favorite app or find yourself enjoying a website, ask yourself: are any of the Gestalt Principles being applied here? Do they work alone or are they being used in combination? To help train your brain, make it a point to analyze every great app you come across, make notes and draw inspiration from it!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15100f4a7f14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/gestalt-principles-applied-on-ux-designs-15100f4a7f14">Gestalt Principles applied on UX designs</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Internship experience as a software engineering intern at Rootcode]]></title>
            <link>https://medium.com/rootcodelabs/internship-experience-as-a-software-engineering-intern-at-rootcode-4f5906bedf5?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/4f5906bedf5</guid>
            <category><![CDATA[internship-experience]]></category>
            <category><![CDATA[tech-startups]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Arosh Segar]]></dc:creator>
            <pubDate>Wed, 23 Mar 2022 06:09:08 GMT</pubDate>
            <atom:updated>2022-04-08T08:54:29.974Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Sharing my exciting journey as a software engineering intern at Rootcode.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BBd0CrGbHLdHa-RZvv1eqg.png" /></figure><p>It all began in the month of June. After a CV screen procedure, Rootcode picked me for an interview, and I was elated! Let me walk you through all the details!</p><p><strong>The interview process at Rootcode Labs</strong></p><p>The whole interview process was divided into three phases. During the first phase of the interview, I was asked some general questions as well as some tech-specific questions. Overall I thought that the interview was very well structured. A few days after, the people and the culture team said that I had passed the first phase of the interview and I’m qualified for the next phase. The next phase of the interview was a practical evaluation where I had to develop a small e-commerce application within the allocated time frame. I was asked to demonstrate what I’ve built, to some of the technical leads and they said that they were rather not looking for the completion of the project but rather the approach that I had taken. After a few days I got a call from the People and Culture team, and they said that I have been selected for the third phase of the interview.</p><p>The third interview was more of a quick chat with with Alagan and Mangala (CEO and the COO of Rootcode), which I found very insightful. Plus, it was a pleasure to see that even the C-level executives get involved with regards to recruiting an intern! Finally, they broke the good news to me saying “welcome to Rootcode”. I was really happy that I got selected for this internship and I’m also grateful that I got the opportunity to start my career at Rootcode with zero experience.</p><p><strong>How I kick-started my internship</strong></p><p>The first few days, I spent my time learning about Rootcode, getting to know my fellow colleagues, and adapting to the way of working at Rootcode. My initial task was to get hands-on experience on a mini-project, which led me to gain an idea of the tech, frameworks the company is using. As a person with no prior hands-on experience, this was a great launching point. Frankly speaking, it was challenging, but I was able to learn so much within a limited time frame thanks to my team leads and mentors. Thanks to the support system and the friendly culture at Rootcode, I was able to reach out to anyone at any time if I came across a difficulty. This contributed to my learning process at Rootcode as an intern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K57NtdXHPgVGUOHq" /></figure><p>The training and development process that I underwent helped me become a better engineer every single day. I was asked to complete the allocated tasks within a given time constraint and then a Senior developer would review the work that I have done and give feedback. I believe this was very effective since I was able to learn simultaneously while I’m working on a project.</p><p>Whenever I have to learn something new, I would seek guidance from Senior developers and Tech leads working on the same project and then refer to the official documentation and other articles, for better understanding. This not only improved my reading habit but also improved my communication skills!</p><p><strong>Learning and development</strong></p><p>I’m so glad for the fact that I got to learn a lot of new things at Rootcode. Even though I had an idea about the project management processes followed at Rootcode, I have never used any project management tools for the projects that I worked on before. The whole project management process was new to me, and with time, I got an in-depth idea about the whole process.</p><p>At the very beginning of my internship, I wasn’t familiar with many of the tools that were used by the team. The only library I was familiar with was React and during the first week, I was asked to learn tailwind CSS for styling and Next.js for server-side rendering. I also worked on animating certain components using React Spring and Keyframes. This was a great experience!</p><p>Whenever I do a university project, the main focus would be led towards the functionalities of the app that I’m developing but here I had to focus on other aspects of the application as well, such as performance, responsiveness, usability, code quality, etc. Since I was involved in different phases of the software development life cycle (SDLC), I understood the different stages that the product goes through and the outcome of each stage through practical encounters.</p><p>Over a few months, I not only learned new frameworks, technology, etc. but also learned the work that other teams perform (QA, UI, Marketing, etc.) and how their work influences the overall success of a project. <br>As a university student who had to juggle studies and work, I also learned how to be better at time management and stay organized.</p><p><strong>Project experience</strong></p><p>After the first week of training, I was assigned to a project called the <a href="https://expertrepublic.com/"><strong>Expert Republic</strong></a><strong>.</strong> Speaking a little bit about Expert Republic, it is a mobile and web application that provides secure, trusted one-to-one, and video consultations between industry experts and customers. The application provides a platform for businesses/individual professionals to make their services available online so that customers can obtain the service from their homes or from wherever they are. One month later I was assigned to a project of revamping the Rootcode website, which was also an interesting one. You can check out the brand new look of the Rootcode website right <a href="https://rootcodelabs.com/"><strong>here</strong></a><strong>.</strong></p><p><strong>Rounding up</strong></p><p>Simply putting in, every day I’m given a task to complete, and that task might carry a lot of problems. I like how I end up exploring and learning new things in the process of finding a solution. The learning and development curve that I underwent is enormous concurrently exciting as well. Thanks to the well-structured processes and the guidance received from the seniors, I’ve gathered so much knowledge and experience during the past few months working at Rootcode.</p><p>One of the best things that I like about Rootcode is the freedom that you have to talk to anyone, even with the CEO or COO at any time with no restrictions. All team members are always willing to help and sometimes they even leave aside their work and try to help me find a solution to the problem. It really did feel like I’m working with a bunch of great friends. Genuinely, this is a work community that feels like family!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f5906bedf5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/internship-experience-as-a-software-engineering-intern-at-rootcode-4f5906bedf5">Internship experience as a software engineering intern at Rootcode</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The rise of codeless automated testing]]></title>
            <link>https://medium.com/rootcodelabs/the-rise-of-codeless-automated-testing-8ac7beaa10c8?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/8ac7beaa10c8</guid>
            <category><![CDATA[automated-testing]]></category>
            <category><![CDATA[qa-automation]]></category>
            <category><![CDATA[test-automation]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Danyl Pachake]]></dc:creator>
            <pubDate>Tue, 01 Mar 2022 10:13:08 GMT</pubDate>
            <atom:updated>2022-03-01T10:13:08.748Z</atom:updated>
            <content:encoded><![CDATA[<p>An informative guide to automated testing and why it’s becoming prominent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mNdQDyRlhwzL5zik" /></figure><p>We have come a long way since manual testing ruled the software world. As soon as Selenium was introduced back in 2004 as means of automating test cases, it took center stage as tech teams realized that in the long run, it offered a good return on investment. And since it was open-source it had all the momentum behind it which has led to its fame among testers today.</p><p>As companies started investing in automation it meant that manual testers had to embrace coding. But many non-coder testers struggle to embrace automation. After some time Selenium introduced <a href="https://chrome.google.com/webstore/detail/selenium-ide/mooikfkahbdckldjjndioackbalphokd?hl=en">Selenium IDE</a> which paved the way for manual testers who had difficulties learning code. Simply put, any person would be able to record steps of a test case of a website or a web application by simply recording it and playing it back when needed. Those steps could be converted into a Selenium-supported program language if needed. Though it was deemed beneficial, there were noticeable setbacks as well.</p><p>As technology kept evolving and the complexity of software kept increasing, the capabilities Selenium IDE offered seemed insufficient to meet the needs. A mix of both manual testing and powerful codeless automation testing could prove a very efficient and deadly combination. Thus, creating the pathway for the rise of advanced and powerful codeless automation tools. <a href="https://www.futuremarketinsights.com/reports/codeless-testing-market#:~:text=Future%20Market%20Insights%20(FMI)%20projects,applications%20will%20surge%20through%202021.">Future Market Insights</a> (2021) predicts that the demand for Codeless Automation Testing is set to increase by 15.5% in the next decade.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PlfnflpXRaNJS_GM" /></figure><p>Picture credit: <a href="https://testsigma.com/blog/modern-codeless-test-automation-myths-facts/">Testsigma</a></p><h3>What exactly are codeless automation tools?</h3><p>When it comes to automation testing, an Automation Engineer could be seen as a mix of a programmer and a QA Engineer. Coding often seems to be a distraction when it comes to a tester as it could be seen as deviating from the main role of a QA Specialist. Codeless automation takes center stage here, as it enables testers to continue automation testing using these tools thus taking away the need to learn advanced code. Although this is regarded as the “Codeless Future” it doesn’t mean that there will be no code involved at all. It simply means that there will be a minimum code required.</p><p>So, how do these tools work? These tools are simple to install with minimum rigmarole. A Tester should have sound knowledge about the requirements and business logic before getting started. Once the test cases are defined, the tester simply needs to click on a record button and run through the test steps and click on the stop recording button at the end. The tool will automatically capture the URLs, the data passed, and functionalities and create the test scripts. The test scripts can be categorized and organized as Test Suites.</p><p>Testers can run these test scripts as regression tests and can even edit these test scripts if the functionality has changed. This record and play feature not only saves time but also has proven very efficient as it enables users with minimal exposure to automation to easily record and manage test scripts. These tools are quite straightforward as they can get, and they require very little training to get started. In a nutshell, this is how code-based automation testing that required a lot of effort, time, and patience, has now transformed into a codeless testing World.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m6yoCmd5JgZxzw8t" /></figure><p>Picture credit: <a href="https://www.mobilelive.ca/blog/codeless-automation-the-future-or-overhyped/">mobilelive</a></p><h3>Self-healing? What else do codeless automation tools offer?</h3><p>One of the problems with automating test scripts is that there will be maintenance that needs to be done on a regular basis. As we all know change is constant and in web applications we may see regular changes being done by developers to fix bugs or even improve user experience by carrying out UI changes. Every little change can have a big effect on automated test scripts.</p><p>Let’s take a simple example of a login screen of a web application. The project team decides to change the position of the login button as well as its size. This could be a small change from the Developer’s perspective but from a tester’s perspective, they have to re-look at the login test flow as well as all other test cases that involve the login flow.</p><p>This is where the self-healing traits of codeless automation tools come in handy. Most of the advanced codeless automation tools utilize <strong>Artificial Intelligence (AI) based self-healing algorithms</strong> which combine codeless automation with machine learning (ML) which results in automatic updates in the test flow when it detects any changes.</p><p><strong>Healenium </strong>is another technology that provides self-healing capabilities and it is open-source. When invalid elements or when there are elements that are unable to detect in the existing test scripts due to changes made in the code, Healenium replaces such elements with new values that match previous elements. These self-healing traits enable more resilient tests and reduce the time and effort put in when it comes to maintaining test scripts.</p><p>Codeless automation offers much more than resilient test scripts. It takes less time to automate a system and it reduces the effort spent on maintenance. According to Software testing <a href="https://www.lambdatest.com/blog/12-software-testing-trends-2021/">trends </a>for 2021, <strong>almost 38% of IT firms have brought AI / ML into their testing efforts </strong>with an intention of ensuring Continuous Improvement / Continuous Delivery (CI/CD) while mitigating production level bugs as it automatically handles processes.</p><p><strong>Speed </strong>is one of the main features of codeless automation as it accelerates the delivery of projects. Since less time is spent on automating scripts and more time on writing comprehensive test suites the quality of the products will be higher. Testers will have more control over the test scripts and the efficiency will also increase as all of this will be performed in a highly controlled environment.</p><p><strong>Scalability </strong>is another key factor when it comes to codeless automation tools as most of them are cloud-based. If you take a traditional automation tool like Selenium, scalability has proven to be expensive and inefficient. Codeless automation tools that are cloud-based make upgrading or maintenance look effortless as you can scale up or down depending on the requirement of a project.</p><h3>Can’t decide on which codeless automation tools and platforms to use?</h3><p>As the importance of codeless automation tools surges, and with trends and predictions all pointing towards a future that is building around codeless automation, there are a number of tools that have surfaced in the recent past. Each tool shares many common features as well as unique features. This has made the decision of choosing the required codeless automation tool even more challenging. When deciding on an automation tool it is of utmost importance to select a solution that integrates effortlessly with the team’s current workflow. Let’s look at three of the most popular and in-demand automation tools.</p><p><a href="https://www.katalon.com/"><strong>Katalan Studio</strong></a></p><p>Katalan studio has been one of the most sought-after tools in the market as it offers testers automation capabilities across desktop, mobile, web, APIs, and applications. One of the main reasons for its popularity among testers is the simple-to-use features that make it easier for both experienced and beginners. Below listed are a few features that give Katalan studio a cutting-edge over its competitors.</p><ul><li>Limited programming knowledge to get started</li><li>Robust test generation on all platforms</li><li>Self-healing capabilities</li><li>Powerful and advanced reporting features</li></ul><p><a href="https://www.accelq.com/"><strong>AccelQ</strong></a></p><p>AccelQ is regarded as one of the most perfect tools among testers and its AI-powered automation capabilities have seen them rise to the very top. A powerful tool with robust features as mentioned below has taken AccelQ right to the top of the codeless automation tools list. Implementation is effortless and enables manual testers to quickly grasp the concepts of automation.</p><ul><li>Natural English coding, No-Code Automation with self-healing capabilities</li><li>One-stop platform for both Manual &amp; Automation testing</li><li>Promotes efficient visual test designs by creating app blueprints</li><li>Generating test scenarios and test cases with its projecting and path analysis traits</li></ul><p><a href="https://www.perfecto.io/"><strong>Perfecto</strong></a></p><p>Perfecto is the most trusted codeless automation tool when it comes to huge teams as its scalability features are second to none. Network virtualization and user simulation capabilities ensure that end products will be of high quality, as issues would be identified and sorted as soon as possible. Quoted as providing services across multiple industries and catering to more than 50% of fortune 500 companies, Perfecto has established itself as one of the leaders in the codeless automation industry.</p><ul><li>Cloud-based secure web and mobile testing</li><li>Smart analytics and reporting capabilities</li><li>AI-driven test maintenance capacities</li><li>Self-healing capabilities</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2u0itjTMxJMpDa-1" /></figure><h3>Are codeless automation tools the future of test automation?</h3><p>As codeless automation tools offer many features that increase the productivity of tech teams, it is not surprising that it is heading towards an era where it has the potential to become mainstream. The whole concept is based on the idea that anyone in an organization, from development teams to testing teams, even the teams who don’t directly involve themselves in the production, should be able to utilize such tools. Considering the fact that it is limited or no programming knowledge required, along with the robust and advanced features and functionalities it offers, it is safe to say codeless automation starting to look like the future of test automation.</p><p>It is quite common that a single bug in a complex software solution can result in huge financial losses for organizations. The speed and reliability of codeless automation tools along with skilled automation engineers could prove a powerful combination to overcome this.</p><p>The demand for automation engineers is unlikely to reduce, as firms look towards investing more and more in automating the testing processes. These tools could simply fast-track and build solid test scripts that are easily maintainable with unique features it offers. In the future, we might see codeless automation tools that are sophisticated and smart enough to completely eliminate the requirement of coding test scripts.</p><p>These tools seem to be the answer for the ever-evolving IT industry where methodologies such as Agile and DevOps have taken center stage. The QA solutions have to keep pace with the demands of Agile and DevOps. Codeless automation has removed the barrier of entry for a wide range of users when it comes to automation and its easy-to-use interfaces and simple functionality have been a much-needed booster to the software industry.</p><p>Although the advancement of technology through the likes of ML and AI has taken automation testing to new heights, the true potential of codeless automation tools is still yet to be seen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ac7beaa10c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/the-rise-of-codeless-automated-testing-8ac7beaa10c8">The rise of codeless automated testing</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting  started with React Native]]></title>
            <link>https://medium.com/rootcodelabs/getting-started-with-react-native-96a92ed6dd6b?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/96a92ed6dd6b</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Charith Wijesena]]></dc:creator>
            <pubDate>Mon, 21 Feb 2022 04:52:37 GMT</pubDate>
            <atom:updated>2022-02-21T04:52:37.384Z</atom:updated>
            <content:encoded><![CDATA[<h3>Getting started with React Native</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3df-3SQkEkApdBcwOtvaDg.png" /></figure><p><strong>What Exactly Is React Native?</strong></p><p><a href="https://reactnative.dev/">React Native</a> is a popular JavaScript-based mobile app framework developed by Facebook (the company behind both ReactJS and React Native) for creating native-style apps for iOS &amp; Android under one common language. If you’ve ever used the Facebook app on Android or iOS, you have already seen React Native in action.</p><p>React Native was developed in 2013 as Facebook’s internal hackathon project and in March of 2015, they released it for public use. In just a couple of years, it became one of the top solutions used for mobile development.</p><p>Facebook, Instagram, and Walmart have built their apps using React Native. You can visit React Native’s website to see a list of other companies that are currently using React Native in their applications. There is a rich community of React Native developers and also there are plenty of courses available online to get started with React Native.</p><blockquote><em>“Google Trends says React Native’s framework popularity has grown during the previous three years. That is very remarkable.”</em></blockquote><p>React Native was initially developed to support iOS. However, Facebook quickly followed it up with Android support and the library can now render mobile UI’s for both platforms. And in 2019 Microsoft announced its plans of incorporating React Native Framework for Windows’ desktop application as well.</p><p>React Native is a great pick for developers who have expertise in JavaScript, which is a mainstream language as there is no need to learn new languages like Objective-C, Kotlin, or Swift.</p><p>React Native development is simple, super-fast, and efficient compared to a lot of mobile development frameworks out there. When we talk about the advantages, you can get a glimpse of how it helps to speed up the development process.</p><p><strong>How does React Native work?</strong></p><p>Let’s have a look at how React Native works under the hood and see how JavaScript is compiled into Native code.</p><p>There are two important threads running on every React Native application, the JavaScript thread, and the Native thread. Both of these threads are able to share information using a “bridge”, the part that provides a way for bidirectional and asynchronous communications between these two realms. With the help of this bridge, React Native can ask native code to provide the native elements it needs.</p><p>Let’s take a look at the following diagram, which explains how the bridge works:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5cEjD6_lepNjeEPVWLOmdA.png" /></figure><p><strong>What makes React Native special?</strong></p><p>The difference between React Native and other cross-platform frameworks like Ionic or Cordova is that React Native doesn’t render web views in its code. It comes with native modules and native components that improve performance. If there is a feature that you need to add to your app, which is not yet supported by the React Native library, then you can write your own native module using a platform-specific language which can then be linked to the React Native codebase.</p><p>Let’s take a sneak peek into some of the advantages of using the React Native framework and why you should choose it as a solution to build your next mobile application.</p><p><strong>Code reusability</strong></p><p>Code reusability is an important advantage React Native gives over others. You can minimize a lot of duplicate code by simply sharing logic across the web and mobile versions of an application. With the convenience of this framework, you don’t have to build the same application for iOS and Android separately, as React Native allows you to reuse the common logic layer.</p><p><strong>Live reload</strong></p><p>Developer experience is brilliant with React Native because you can get fast feedback with it. Instead of recompiling you can reload an app instantly by making use of the hot reloading feature. The development time also improves by reloading the application automatically as the code changes. This is one of the very loved features of React Native.</p><p><strong>Large developer community</strong></p><p>React Native has a large community of developers. If you are facing any issues in the development process, you have a high chance of getting the right kind of help from the community and experts, thereby, saving you when you get stuck. It also means you get to have more approachable access to great developers and their experience.</p><p><strong>Cost efficiency</strong></p><p>React Native apps lower your development and maintenance costs because you don’t have to deal with two separate code bases for each platform.</p><p>So from an organization’s perspective, you don’t have to hire two teams with different skill sets to work on the project, One team is enough.</p><p><strong>React Native Drawbacks</strong></p><p>Like any other technology React Native also comes with its share of limitations. Most of the issues are now getting addressed by React Native’s community but there are some that you need to be aware of before you decide on developing a React Native app.</p><p><strong>Let’s focus on some of its major cons:</strong></p><p><strong>Smaller ready-made Components collection</strong></p><p>React Native is a newbie as compared to other Android and IOS programming languages and at the moment the ready-made components collection is quite small. This limits developers from taking advantage of pre-built commonly used components.</p><p><strong>Third-party components</strong></p><p>React Native has a lot of third-party plugins to choose from but be mindful about your choice because some of the plugins might not behave as expected.</p><p>Also, React Native updates happen frequently. And when that happens, third-party libraries often get outdated and can cause trouble.</p><p><strong>Native Developers are still Needed</strong></p><p>In some cases, developers can’t limit themselves to writing code only in React Native. They might need to use additional native codes for components that aren’t compatible with React Native. The implementation of some more advanced features requires Java/Objective-C/Swift expertise. So you’ll still occasionally need some assistance from native developers.</p><p><strong>Final Thoughts</strong></p><p>React Native is a great selection for creating apps that will work smoothly irrespective of the platform. Currently, the Facebook crew keeps upgrading React Native so it can resolve a lot of the issues that are commonly reported with the framework.</p><p>Overall, in my opinion, React Native is a very good choice for most use cases.</p><p>“learn once, write anywhere”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=96a92ed6dd6b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/getting-started-with-react-native-96a92ed6dd6b">Getting  started with React Native</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Metaverse & NFTs are shaping the world of Marketing]]></title>
            <link>https://medium.com/rootcodelabs/how-metaverse-nfts-are-shaping-the-world-of-marketing-74bebc92b019?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/74bebc92b019</guid>
            <category><![CDATA[metaverse]]></category>
            <category><![CDATA[branding]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Dewni De Silva]]></dc:creator>
            <pubDate>Sun, 13 Feb 2022 02:14:13 GMT</pubDate>
            <atom:updated>2022-02-13T02:15:47.926Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DypVcCZp1eYalhMJuPx1Bw.png" /></figure><p><strong>What is Metaverse?</strong></p><p>Metaverse might sound like a random comic book term, but in reality, it’s a place where your digital self can reside. Your digital self is what is known as an avatar, and it is able to move around and interact with other people who also have their own avatars in the virtual world. Both Virtual Reality and Augmented Reality will no doubt be key elements of the metaverse. At this point, you can already attend virtual events with your avatar and interact with other people in a VR setting. The metaverse is likely going to expand this to a much more interactive and massively promoted alternate reality.</p><p>Most brands haven’t realized that we are in the 3rd era of social — the creator economy. In brief, the creator economy is made of creatives, designers, artists, musicians, and writers who leverage technology to create an audience and therefore their own influential brand. Metaverse just helps brands do this but in a better way. Recent reports predict the metaverse market will grow to over <a href="https://cointelegraph.com/news/why-are-major-global-brands-experimenting-with-nfts-in-the-metaverse">$1,544 billion</a> in less than ten years.</p><p><strong>What’s the connection between Metaverse and NFTs?</strong></p><p>Are these two connected? The answer is yes. The metaverse and NFTs are related to digital assets and how they are given value. The metaverse will allow people to showcase digital forms of art and property, and NFTs will allow them to put a price on that content with proof of ownership.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wsi1LmyPdKT5s-Br.png" /></figure><p>It’s generally built using the same kind of programming as cryptocurrency, like <a href="https://www.forbes.com/advisor/investing/what-is-bitcoin/">Bitcoin</a> or <a href="https://www.forbes.com/advisor/investing/what-is-ethereum-ether/">Ethereum</a>, but that’s where the similarity ends. Each NFT is attached to a specific item. That item could be a painting, video game content, music, or anything else that can be attached to that specific token. This is ideal for digital assets, and NFTs have turned into a great way for artists and creators in general to monetize their work. Again, a plus point for creator economy.</p><p>The metaverse-NFT interplay is undoubtedly a prominent highlight because it could end up becoming the optimal currency to enter Metaverse. This will allow people to show proof of ownership, something like a deed to a property that only exists in a virtual world. Another possibility is that NFT could be treated as a token or a perfect access point for specific virtual events happening inside the metaverse. The possibilities are endless, that’s what makes the idea so attractive.</p><p><strong>Why is it a big deal for brands?</strong></p><p>Consumers crave experiences. Now that most businesses have had a taste of what Metaverse could be for their brand, they aren’t going to settle for anything less. And consumers are getting tired of static displays and video ads that crowd social media. With web 3.0 or the 3rd era of social, everyone expects a rich, interactive, immersive experiences. The Metaverse is built on such experiences. The replacement of the flat, two-dimensional world of the web with 3D (or in some cases 4D) is making brands flock around metaverse because that being a part of the momentum itself is a huge marketing success. Given that metaverse is a representation of the real world in a virtual setting, there’s no question that it will open a world of possibilities for brands to thrive. Brands can start to create virtual representations of their products now to ensure that they can be found by other people in this new universe. How-to guides and product pitches can also be done in a much more interactive way by marketers. The joy!</p><p>We are more likely to be living in two different realities, one is the offline world we’ve always known and the other is the virtual environment. Being able to be discovered by your customers in both of these worlds will be crucial for most brands.</p><p><strong>The entire customer journey within the Metaverse</strong></p><p>However, the metaverse contains opportunities to affect the entire customer journey in a streamlined, holistic way. The metaverse allows brands to reach new audiences in new and inventive ways while enabling them to dig deeper, learn more and ultimately make purchases, all in a single, cohesive experience.</p><p><strong>Taking co-creation to the next level</strong></p><p>Marketers spend their whole life cracking the Instagram, Facebook, and Google algorithms just to make sure they are at the top of their game when creating engaging content that cuts through the noise and millions of competitors. And as marketers, we strive to involve consumers in the co-creation of user-generated content for as long as I can remember. It’s a marketer’s dream to have end-customers create, publish and share content that features their brand, but the challenge has always been how to encourage co-creation that’s meaningful and authentic. And by the looks of it, with Metaverse, this will become less of a challenge.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74bebc92b019" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/how-metaverse-nfts-are-shaping-the-world-of-marketing-74bebc92b019">How Metaverse &amp; NFTs are shaping the world of Marketing</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dockerizing A Node.Js Application]]></title>
            <link>https://medium.com/rootcodelabs/dockerizing-a-node-js-application-66843f99a325?source=rss----1e3cfe39ccfd---4</link>
            <guid isPermaLink="false">https://medium.com/p/66843f99a325</guid>
            <category><![CDATA[rootcode]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Lakshitha Wisumperuma]]></dc:creator>
            <pubDate>Fri, 11 Feb 2022 12:19:25 GMT</pubDate>
            <atom:updated>2023-01-07T18:20:55.297Z</atom:updated>
            <content:encoded><![CDATA[<h3>A guide on how to Deploy Node Application in a Docker container</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3ncuZ05ZxETxwg1mv6I57w.png" /></figure><p>In this article, we’ll be exploring one of the most popular tools used to containerize and deploy applications over the internet, i.e., Docker. We will look into what Docker is, why we need it, and how to run a basic Node application in a Docker container.</p><p>So, let’s dive in.</p><p><strong>What is a Docker?</strong></p><p>Docker is a containerization platform that enables developers to seamlessly build, share, and run any application, anywhere. However, the question arises if you’re new to deployment, why do we need containers? Containers are a method of operating system virtualization that allows you to run an application and its dependencies in resource-isolated processes. Being resource-isolated, there are many benefits in containerization using Docker,</p><ul><li>Improve application life-cycle management through capabilities such as continuous integration and continuous delivery (CI/CD).</li><li>Increased portability gives consistent operations because applications in containers will run the same, regardless of where they are deployed, the solution to “Works on my machine” syndrome.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/422/1*2IWD6fLgoe0oMKvAD6CUqQ.jpeg" /></figure><ul><li>There are fewer overheads because of isolation at the OS level; containers share the system kernel with other containers, making them faster. (Figure 1.1)</li><li>Improves security by isolating applications from the host system and each other.</li><li>Since containers are encapsulated and loosely coupled, it allows you to replace or upgrade one container without disrupting others.</li><li>Scalable with the help of orchestration services like Kubernetes, Docker Swarm, or Apache Mesos.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aFfAIebLSa6GnOT8so8KYQ.png" /><figcaption>Figure 1.1 | Containers and Virtual Machines | Source: <a href="https://www.docker.com/resources/what-container">Docker.com</a></figcaption></figure><blockquote>Build Once, Run Anywhere.</blockquote><p>However, there is a disadvantage in tokenization: applications with different OS requirements cannot be hosted together on the same Docker host.</p><p>Docker collaborates with the open-source ecosystem. Anyone can contribute to Docker and extend it to meet their requirements if they need additional features that aren’t available out of the box. So why try to reinvent the wheel, right?</p><p><strong>What are the terminologies associated with Docker?</strong></p><p>Let us take a quick look at some of the terminology associated with Docker before looking into a practical example.</p><p><strong>Dockerfile</strong>: A Dockerfile is a text document that contains all the commands a user could call on the command line to assemble an image. Docker image is created using a Docker file.</p><p><strong>Docker Images</strong>: An image is a read-only template with instructions for creating a Docker container. Often, an image is based on another image, with some additional customization.</p><p><strong>Docker Containers</strong>: A container is a runnable instance of an image. You can create, start, stop, move, or delete a container using the Docker API or CLI. In addition, you can connect a container to one or more networks, attach storage to it, or even create a new image based on its current state.</p><p>While there are other terminologies that you should become familiar with, like Docker engine, Docker hub, and Docker architecture. You can find detailed clarifications here in the <a href="https://docs.docker.com/get-started/overview/">Docker documentation.</a></p><p><strong>Deploying a Node Application</strong></p><p>Once you are done developing your application, you need to ensure that the application is executing correctly on the assigned port. In my case, I am using port 8080. If the application is working as expected, you can proceed with deployment. You wrote it, so it should work, right?</p><p><strong>Creating a Dockerfile</strong></p><p>Create a simple Dockerfile in the app root directory as <em>Dockerfile</em> (case sensitive), with no extension.</p><p>The first thing we need to do is define what image we want to build from. After that, you can choose what you need with the application requirements. You can find base images on <a href="https://hub.docker.com/">Docker Hub</a>.</p><p>You can also specify multiple <em>FROM</em> instructions which are called a multi-stage build, but for this article, let’s keep things simple.</p><pre><em>FROM node:14.15.1</em></pre><p>Then we need to define the working directory using <em>WORKDIR</em>.</p><pre><em>WORKDIR /usr/src/app</em></pre><p>Now we need to install our node application dependencies using the npm or yarn. We are only copying the <em>package.json </em>file using a wildcard. Since Docker creates a layer for <em>COPY</em> command, this allows us to take advantage of cached Docker layers.</p><p>Then we install using <em>RUN</em>. This instruction does what it says; it runs commands. Or, more specifically, it executes a specific command.</p><pre><em>RUN npm install</em></pre><p>Next, we bundle the app source using <em>COPY</em>.</p><pre><em>COPY …</em></pre><p>Then we <em>EXPOSE</em>, the <em>EXPOSE</em> instruction informs Docker that the container listens on a specific network port at runtime. However, this is optional.</p><pre><em>EXPOSE 8080</em></pre><p>We define our runtime using <em>CMD</em>; CMD sets a default command, which will be executed when you run the Docker image without specifying a command.</p><pre><em>CMD [ “node”, “server.js” ]</em></pre><p>Your final <em>Dockerfile</em> should be something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/14db2b6a5b6a06103f7cf8e5662e9e7b/href">https://medium.com/media/14db2b6a5b6a06103f7cf8e5662e9e7b/href</a></iframe><p>Time to leverage <em>.dockerignore</em>. This allows you to exclude files from the context like a .<em>gitignore</em> file will enable you to exclude files from your git repository. This is more of an optimization approach. In the root directory, create a .<em>dockerignore</em> file and add the following lines.</p><pre><em>node_modules</em></pre><pre><em>npm-debug.log</em></pre><p><strong>Building your image</strong></p><p>Now that we are done with Dockerfile, let’s build. First, in the root directory, run:</p><pre><em>$ docker build -t &lt;your-username&gt;/&lt;repository-name&gt; .</em></pre><p>When you have many images, it becomes difficult to know which image is what. So Docker provides a way to tag your images with the <em>-t</em> flag.</p><p><strong>Running a Docker image</strong></p><p>You can now run the Docker image by using the docker run API. The command is as follows:</p><pre><em>$ docker run -p 80:8080 -d &lt;your-username&gt;/&lt;repository-name&gt;</em></pre><p><em>-d</em> flag is added to run the container in detached mode, leaving the container running in the background, and the <em>-p</em> flag redirects a public port to a private port inside the container.</p><p><em>docker ps</em> and <em>docker logs &lt;container id&gt;</em> command will help you to list containers and get container logs details, respectively. Now we are at the end of the journey, get container-id using <em>docker ps </em>and get the port of your app that Docker mapped.</p><pre><em>curl -i localhost:&lt;port&gt;</em></pre><p><strong>Conclusion</strong></p><p>In this article, we mapped the basics of containerization, what Docker is, why we need it, and how to dockerize a simple node application. While we only scratched the surface of the Docker world, there is a lot more to learn and get hands-on. It needs to be said, combined with mechanics like Docker Compose, volumes, and container orchestration solutions, you can deploy your applications in a seamless transition between your development environment and the live environment. You and your organization can benefit immensely by continuous integration and continuous deployment of application life-cycles.</p><p><strong>Additional Resources:</strong></p><p>Here are some valuable resources mentioned throughout the article; it might be helpful to check them out.</p><ol><li><a href="https://docs.docker.com/get-started/overview/">Docker Documentation, <em>Docker overview</em></a></li></ol><p>Retrieved from: <a href="https://docs.docker.com/get-started/overview/">https://docs.docker.com/get-started/overview/</a></p><p>2. <a href="https://docs.docker.com/develop/develop-images/dockerfile_best-practices/">Docker Documentation, <em>Best practices for writing Dockerfiles</em></a></p><p>Retrieved from: <a href="https://docs.docker.com/develop/develop-images/dockerfile_best-practices/">https://docs.docker.com/develop/develop-images/dockerfile_best-practices/</a></p><p>3. <a href="https://docs.docker.com/get-started/overview/">Hub.docker.com, <em>Docker Hub</em></a></p><p>Retrieved from: <a href="https://docs.docker.com/get-started/overview/">https://docs.docker.com/get-started/overview/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66843f99a325" width="1" height="1" alt=""><hr><p><a href="https://medium.com/rootcodelabs/dockerizing-a-node-js-application-66843f99a325">Dockerizing A Node.Js Application</a> was originally published in <a href="https://medium.com/rootcodelabs">Rootcode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>