<?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[Stories by Yonatan Dawit on Medium]]></title>
        <description><![CDATA[Stories by Yonatan Dawit on Medium]]></description>
        <link>https://medium.com/@yoncity?source=rss-2abd1c910f7a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1c8N2YDpGwmammmLV2QUkg.jpeg</url>
            <title>Stories by Yonatan Dawit on Medium</title>
            <link>https://medium.com/@yoncity?source=rss-2abd1c910f7a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 11:39:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yoncity/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Build a Note Taking Desktop Applications With Tauri and React]]></title>
            <link>https://medium.com/better-programming/building-cross-platform-desktop-applications-with-tauri-part-ii-8d6ad1927093?source=rss-2abd1c910f7a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d6ad1927093</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[tauri]]></category>
            <category><![CDATA[rust]]></category>
            <dc:creator><![CDATA[Yonatan Dawit]]></dc:creator>
            <pubDate>Sun, 25 Sep 2022 20:50:52 GMT</pubDate>
            <atom:updated>2022-09-27T07:31:29.914Z</atom:updated>
            <content:encoded><![CDATA[<h4>Create awesome cross-platform apps</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M6hebxNAfqWUYO0ci1s6hA.png" /><figcaption>image by author</figcaption></figure><p>Hello all. Today, we shall look at how we can develop a Simple Notes desktop application using Tauri and ReactJS.</p><p>The finished project can be found in <a href="https://github.com/Yoncity/simple-note-app">this GitHub repository</a> if you wish to compare it with what you built.</p><h3>Abstract</h3><p>The main idea of this article is to show you how you can leverage Tauri and some of its api to develop desktop applications with the FileSystem (fs) in particular. <a href="https://tauri.app/v1/api/js/">Read more on all the APIs here.</a></p><p>The fs API provides us with some common functionalities (creating, reading and writing files, and making folders) that we can import and use. This will come in handy especially if you don’t want to get your hands dirty with Rust and save us so much time.</p><p>So, here goes the flow of our Notes app:</p><ul><li>Users will be able to create notes</li><li>When creating notes, we have to provide them with native Save dialog option to specify where they want their note saved</li><li>Create the note file in their desired location and let them add their content.</li><li>Once the note has been created, we shall save it in the localStorage such that we keep track of our notes regardless of where they are stored on our computer.</li><li>Read the contents of a note saved on the user’s computer</li><li>When a user deletes a note, delete the file</li></ul><p>As you can see, we shall see how we can interact with File system to create, read and delete files using Tauri. We shall also talk about how Tauri implements allow list to only allow certain features of an API, i.e., restrict to which folder our note app will have access to control using the fs API.</p><h4>Disclaimer</h4><p>This tutorial assumes the user has a basic understanding of Reactand programming as a whole.</p><h3>Getting Started</h3><p>There are a couple of tools you will need to get this development underway and fortunately, <a href="https://tauri.app/v1/guides/getting-started/prerequisites">Tauri’s official website</a> has got us covered. Go ahead and install all the necessary dependencies for your appropriate platform as they have specified.</p><p>Once you have finished up, you may need to restart your bash so Rust can be added to the environmental variables, but the easiest way is to reboot your computer.</p><p>Now, we can proceed to create a Tauri project. I will be creating the project using yarn, but you can use the package manager of your preference as specified <a href="https://tauri.app/v1/guides/getting-started/setup">here</a>.</p><p>To create the Tauri project, type the code below in your terminal:</p><pre>yarn create tauri-app</pre><p>Once this finishes, it will present you with the option to give it a name. Let’s call it simple-notes-app-v1 as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ajdOK5LA4n7bhkMkP0eXEQ.png" /></figure><p>After that, you can choose the package manager of your choice. Then proceed to choose the UI template. For this tutorial, we shall use react-ts as shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9AwzETQpNjnVcCX-Lx1SA.png" /></figure><p>That’s it. Now we have our Tauri App template and we can start by navigating to the folder and installing the packages shown below:</p><pre>cd simple-notes-app-v1</pre><pre>yarn</pre><p>Once all our packages are downloaded, you can run the following command to see what our project looks like.</p><pre>yarn tauri dev</pre><p>If everything goes right, you should see the compiled app as seen in the image below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zb-4YBJW1jWuTuvDsGu_Dw.png" /></figure><p>Now, close the app, and let’s go ahead and add two more packages to use:</p><ul><li>dayjs — package used to deal with date and date formatting</li><li>sass — better way of writing CSS that includes nesting and variables</li></ul><p>To install those packages above, run the following code on your terminal:</p><pre>yarn add dayjs sass</pre><p>Now, the only thing remaining is to download three icons and put them in the /src/assets.</p><ul><li><a href="https://github.com/Yoncity/simple-note-app/blob/main/src/assets/plus_icon.png">PlusIcon</a>: save it as plus_icon.png</li><li><a href="https://github.com/Yoncity/simple-note-app/blob/main/src/assets/note_icon.png">NoteIcon</a>: save it as note_icon.png</li><li><a href="https://github.com/Yoncity/simple-note-app/blob/main/src/assets/delete_icon.png">DeleteIcon</a>: save it as delete_icon.png</li></ul><p>At this point, all the necessary packages, assets, and dependencies are installed and ready to go, so let’s start writing some code.</p><p>Let’s start by deleting all the CSS codes in /src/style.css. Usually, we would have put all the global CSS that we wanted to reuse for our app, but considering our app is going to be rather a simple one, we are just going to delete all the contents and leave the file empty.</p><p>Now we can also modify our /src-tauri/tauri.conf.json. By default, the file comes as shown below:</p><pre>&quot;allowlist&quot;: {<br>    all: true<br>}</pre><p>Since we want our app to be secure and not ship all the API codes that Tauri gives us, we shall only opt-in to the features that we need. So, you will need to replace allowlist with the content shown below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf497da9985599d93ca8211f1d3a6a70/href">https://medium.com/media/cf497da9985599d93ca8211f1d3a6a70/href</a></iframe><p>So, out of the box, we can see that we are only giving our app access to the Document &amp; Desktop folders, and if the user tries to save notes outside of this scope, it won’t allow him. <a href="https://tauri.app/v1/api/js/fs#security">Read more on security here.</a></p><p>Now, let’s replace the contents of /src/App.tsx with the content below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1770a7126c051c1695fff28f09accf5d/href">https://medium.com/media/1770a7126c051c1695fff28f09accf5d/href</a></iframe><p>There is a lot to unpack here, so let’s get started step by step. First off, if you notice the HTML content, it may seem to have a weird class name. That&#39;s because we are using <a href="https://css-tricks.com/bem-101/">BEM</a>. If it&#39;s your first time hearing about it, <a href="https://css-tricks.com/bem-101/">learn more here</a>.</p><p>We have three states that will be storing our note-related data:</p><ul><li>Line 15: this will store a list of all our notes that we shall retrieve from the localStorage.</li><li>Line 16: this will store the id of the current active note such that we can read and modify its contents.</li><li>Line 17: this will store the content of the active note. When the active note changes, we shall fetch the file of the new active note and read its content, so we are storing it in a state so that we can trigger a rerender when the content changes.</li></ul><p>Line 37–54 houses the function addNote that will be called when a user clicks on New Note and it will call the Tauri Save Dialog which will give the user the option to select the filename and location where to save the note.</p><p>Whenever the Save Dialog opens and the user selects the name and location, it will return a string of the location + name. But if the user closes the popup, it will be null, hence we are asserting it has value on Line 39. Read more on <a href="https://tauri.app/v1/api/js/dialog#save">save dialog</a>.</p><p>Assuming everything goes right, Line 41 will create the Note with empty content. Yup, it&#39;s that easy. The rest of the code is pretty much basic programming that you can read on your own, or replace with your own version if you have a better idea. Read more on <a href="https://tauri.app/v1/api/js/fs#writetextfile">writeTextFile</a>.</p><p>Line 78 makes a call to readTextFile which takes in location as its first argument, and takes on Options as its second argument but we shall not use it now. Read more on <a href="https://tauri.app/v1/api/js/fs#readtextfile">readTextFile</a>.</p><p>Line 25 makes a call to removeFile which we pass location as its first argument and will permanently delete the file from our computer. Read more on <a href="https://tauri.app/v1/api/js/fs#removefile">removeFile.</a></p><p>After that, delete /src/App.css and create a new file /src/App.scss. We have opted to use scss as it will be easier to nest CSS. App.scss should look like the file below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fcccefd723d0bce6ef7c3073c0d383ee/href">https://medium.com/media/fcccefd723d0bce6ef7c3073c0d383ee/href</a></iframe><p>Now, we can create getFromLocalStorage.ts file in the src/helpers folder as seen below. This will handle how we set, get, and update our notes in our localStorage.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d0d53a1b46d40523e5b44aa26786a9c0/href">https://medium.com/media/d0d53a1b46d40523e5b44aa26786a9c0/href</a></iframe><p>Now, let’s see how our app looks. Go ahead and run yarn tauri dev. If everything is right, it will run and open the app with the interface as seen above.</p><p>Now the only thing remaining is building the app as a distributable file that we can share with the world. But first, we need to edit the identifier of our app i.e. must be unique to every application, kind of an id. We can set this in src-tauri/tauri.conf.json</p><pre>&quot;identifier&quot;: &quot;com.yoncity.article.simple_note&quot;</pre><p>Feel free to set the id you prefer, just make sure you don’t use the default one. If you do so, Tauri will return an error requesting you to change it.</p><p>Then you can run yarn tauri build and it will generate our distributable that we can share. It will generate the release file for your current operating system. <a href="https://tauri.app/v1/guides/building/">Read more on building your app here.</a></p><p>You can also play around and change some of the things there like the display name of our app and also app icons.</p><h3>Conclusion</h3><p>We have built a simple notes app using a fraction of the APIs that Tauri provides us with. If we need custom functions, we can write up using Rust and call the functions in the frontend. <a href="https://tauri.app/v1/guides/features/command">Read more here.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TEtyYsTSmzzbts4yTkvjYw.png" /></figure><p>Stay tuned for the subsequent parts showing other real-world applications implemented in Tauri.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d6ad1927093" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/building-cross-platform-desktop-applications-with-tauri-part-ii-8d6ad1927093">Build a Note Taking Desktop Applications With Tauri and React</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Cross-Platform Desktop Applications with Tauri — Part I]]></title>
            <link>https://yoncity.medium.com/building-cross-platform-desktop-applications-with-tauri-part-i-e1c8bd0f68c8?source=rss-2abd1c910f7a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1c8bd0f68c8</guid>
            <category><![CDATA[rust]]></category>
            <category><![CDATA[desktop-app]]></category>
            <category><![CDATA[cross-platform]]></category>
            <category><![CDATA[tauri]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Yonatan Dawit]]></dc:creator>
            <pubDate>Fri, 23 Sep 2022 18:50:38 GMT</pubDate>
            <atom:updated>2022-09-23T23:18:13.316Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1zzctUzwIArJxD6MU_G7pQ.png" /><figcaption>Tauri</figcaption></figure><h3>Building Cross-Platform Desktop Applications with <strong>Tauri — Part I</strong></h3><p>The catchy statement <strong>“Write once, run everywhere”</strong> rings bells to a software developer’s ears, as they just have to do an excellent job of developing the app once, and it will run on multiple platforms with minor tweaks.</p><p>This approach is doing wonders in saving time and resources for developers and companies especially in the mobile app sector as they can use the rapidly growing libraries and frameworks such as<strong> “Angular, React &amp; Flutter…”</strong> to develop applications that are cross-platform yet still “native”.</p><p>Since the web frameworks and libraries offer so many functionalities, developers have been working on bringing that option to be used to develop cross-platform desktop apps and <strong>Tauri </strong>has just made the list.</p><p>As the Tauri team say on their <a href="https://tauri.app/about/intro">description page,</a></p><blockquote>Tauri is a toolkit that helps developers make applications for the major desktop platforms, using virtually <strong>any frontend framework</strong> in existence. The core is built with <strong>Rust</strong>, and the CLI leverages <strong>Node.js</strong> making Tauri a genuinely polyglot approach to creating and maintaining great apps.</blockquote><h4>How does it fare against its competitors?</h4><p>One of the dominant frameworks used both by indie developers and companies to develop cross-platform desktop applications is <strong>Electron. </strong>Electron uses the Node.js for its backend and Chromium for its front end which in a way fuels its shortcomings.</p><p>No doubt you have heard how all Chromium projects result in large bundle size and what they are most notoriously known for as <strong>“memory hog”. </strong>To combat this, Tauri uses the <a href="https://github.com/tauri-apps/tao"><strong>TAO</strong></a> and <a href="https://docs.rs/wry/latest/wry/"><strong>WRY</strong></a> libraries to create a <strong>lightweight </strong>WebView that results in a smaller bundle size and less memory usage.</p><h4>Security</h4><ul><li>No Server is Required. Tauri doesn’t need to run a server in order to communicate the backend but rather is compiled and exported with the app so no traffic can be sniffed on TCP ports or external processes.</li><li>Allowing API. Tauri doesn’t ship all the native functionality code with the application i.e. file system access, notifications…etc, but rather the developers choose to <strong>opt-in </strong>to the feature they want to be shipped. <a href="https://tauri.app/v1/references/architecture/security#system-features">Read more on <strong>Allowing API</strong>.</a></li></ul><h4>Pro of Tauri</h4><ul><li>Ultimate freedom to use whatever frontend framework you want. And this works out of the box and you can also integrate an existing project into a desktop app easily.</li><li>The distributable file is also much smaller i.e. starting from 3MB compared to Electron starting from 50MB.</li><li>Ability to use the robustness of Rust i.e. performance and memory management out of the box.</li><li>Tauri uses Rust for the backend and it does so without the need of starting a server in order to communicate with the frontend, which is memory efficient and secure.</li></ul><h4>Cons of Tauri</h4><ul><li>Everyone agrees Rust has a steep learning curve, so it might slow down development.</li><li>As of Tauri v1.0, cross-compilation is buggy and you will probably use a VM, or using a CI/CD service such as GitHub actions as a workaround.</li><li>Tauri is a new framework so it doesn’t have a wide range of communities which might make it difficult to seek help.</li></ul><h3>Conclusion</h3><p>Tauri offers a wide range of advantages over its competitors. With that, given time, it will no doubt be competing neck to neck with the already established frameworks, so it would be wise to give it a try.</p><p>Stay tuned for the subsequent parts showing real-world applications implemented in Tauri.</p><p>If you found this story helpful, don’t forget to give it a clap, and please do share your thoughts in the comment section. Thanks for taking the time to read my story.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1c8bd0f68c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day and Night theme with React Native]]></title>
            <link>https://yoncity.medium.com/day-and-night-theme-with-react-native-9610c34ee5e4?source=rss-2abd1c910f7a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9610c34ee5e4</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[themes]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[Yonatan Dawit]]></dc:creator>
            <pubDate>Mon, 24 May 2021 09:18:55 GMT</pubDate>
            <atom:updated>2021-07-31T09:52:58.819Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A Day and Night Themed Application Overview." src="https://cdn-images-1.medium.com/max/1024/1*MlLa2RtYoDUxBAB5W1B2qg.png" /><figcaption>On the left we have the “Day” theme and on the right we have the “Night” theme.</figcaption></figure><p>Hello all, today we are going to dive deep into developing a themed application with react native. There are a number of ways to do that i.e. using global state like redux but for our case we shall be using <strong>React Context API</strong>. Here are a few things we will be done within a short time.</p><ol><li>Build an application that will detect the default theme of the phone and adapt to that theme.</li><li>Let the user override the default theme of the phone and store the user’s theme preference so we can later retrieve and apply the setting when the application is opened at a later time.</li><li>Do all those we mentioned above, neatly and professionally that can allow our application to be scaled up and down with ease.</li></ol><h3>What you should know by now?</h3><p>This tutorial is targeted at developers with at least basic knowledge of react and react-native, if you don’t find yourself comfortable with the development in those libraries, I suggest you first learn the basics down to intermediate from other sources.</p><h3>Getting Started</h3><p>I will be working on this project and using Github as a repository so feel free to check and compare it with your implementation at <a href="https://github.com/Yoncity/LetsGetThemed.git">https://github.com/Yoncity/LetsGetThemed.git</a></p><p>So here are a few of the libraries and packages that we are going to use today to achieve our objective.</p><ol><li><strong>react</strong> v17.0.1 and <strong>react-native</strong> v0.64.1 or above.</li><li><strong>@react-navigation/bottom-tabs</strong> that you can learn more from <a href="https://reactnavigation.org/docs/tab-based-navigation/">https://reactnavigation.org/docs/tab-based-navigation/</a></li><li><strong>@react-native-async-storage/async-storage </strong>that will use to store the custom user theme preference, that you can learn more from <a href="https://react-native-async-storage.github.io/async-storage/docs/">https://react-native-async-storage.github.io/async-storage/docs/</a>.</li></ol><h4>Overall Project Structure</h4><pre>app<br>|---components<br>|  |------Header<br>|     |------index.js<br>|     |------style.js<br>|  |------AsyncStorage.js<br>|  |------ThemeManager.js<br>|---constants<br>|  |------StorageKeys.js<br>|---hooks<br>|  |------useTheme.js<br>|---screens<br>|  |------Home<br>|     |------index.js<br>|     |------style.js<br>|  |------Settings<br>|     |------index.js<br>|     |------style.js<br>|---style<br>|  |------colors.js<br>App.js</pre><h3>Get Busy…</h3><p>First off, lets get started by creating / initializing a brand new react-native project using npx react-native init LetsGetThemed .</p><p>This will create a react-native project with the name “<strong><em>LetsGetThemed</em></strong>” with default react-native template.</p><p>We can proceed by defining the colors that we shall use for our application. They will be defined in app/style/colors.js .</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7790898a1355d9956a53fb7beaeb2712/href">https://medium.com/media/7790898a1355d9956a53fb7beaeb2712/href</a></iframe><p>Now, we can create ThemeManager.js file in the app/components folder as seen below.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d8986f90bb6ac7cfa7f632fa209ab877/href">https://medium.com/media/d8986f90bb6ac7cfa7f632fa209ab877/href</a></iframe><p>So let us break down the code above. Firstly, we started by creating a context called ThemeContext, and then we went ahead and provided a way we can pass the values of the context to children by creating a ThemeContext.Provider and putting it in a functional component so we can change its state easily.</p><p>Then let us go ahead and create a AsyncStorage.js file, that will help us store the custom user theme preference so we can retrieve and set it later. Let’s create this file on app/components/ folder.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/daaa50c3db8e2d2c2dc1b9be42341625/href">https://medium.com/media/daaa50c3db8e2d2c2dc1b9be42341625/href</a></iframe><p>And once we have setup the <strong>AsyncStorage</strong> and <strong>ThemeManager</strong>, we can proceed to creating a <strong>Custom Hook </strong>that will help us retrieve and set themes. So we will create a useTheme.js file under app/hooks/ folder.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7c3acb04acae5c638e35b9b921b8bfc1/href">https://medium.com/media/7c3acb04acae5c638e35b9b921b8bfc1/href</a></iframe><p>This file is what most of our next screens will be interacting with and if it is hard to understand, dont worry, you can first learn about creating custom react hooks. And as time passes you will get familiar with it.</p><p>So if we are to dissect it, we first have the reference to the <strong>ThemeContext</strong> we created a while back, so we can retrieve the values.</p><p>Then we have the function readTheme that we will use to read the user’s custom set theme preference. If the user has not set a custom manually, it will go with the default device theme.</p><p>And lastly, we have the function updateTheme that we will use to save the user’s custom theme.</p><p>Now, most of the heavy lifting is done, what’s remaining is creating the Home and Settings Screens and placing them in a <strong>bottom tabbed navigation.</strong></p><p>This is the Home Screen created in the app/screens/Home</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6179625233a27efad04222a7cffd8e79/href">https://medium.com/media/6179625233a27efad04222a7cffd8e79/href</a></iframe><p>So now we shall create style.js function that takes in color as a parameter to be sent from the functional component after invoking the useTheme hook.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b059623c70ac1e479034b8ded34985b7/href">https://medium.com/media/b059623c70ac1e479034b8ded34985b7/href</a></iframe><p>And below you will find the Settings screen created under app/screens/Settings</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/932b6cc3dd17131f57e700df602e62ee/href">https://medium.com/media/932b6cc3dd17131f57e700df602e62ee/href</a></iframe><p>And lastly, we can create the style.js file for styling the Settings screen.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c59ad389fc3be5572245f8f476e9c199/href">https://medium.com/media/c59ad389fc3be5572245f8f476e9c199/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*CbVjV4N_O2htaYZOpjlCLg.gif" /><figcaption><strong>LetsGetThemed</strong> application built and running on Android.</figcaption></figure><h3>The Takeaway</h3><p>Day and Night themed application design is gaining popularity nowadays and implementing this from Android Studio natively is so much easier as you simply have to create a different theme style file and place it in values-night directory and android will do most of the heavy lifting for you, but that is not the case for react native.</p><p>And what frustrated me is that in previous tutorials I watched, they were combining the design/style in the file that contains the screen or the functional component just so they can include the theme’s logic. And with the idea of file separation in mind, I was able to come up with a simple and modular approach.</p><p>If you found it helpful, don’t forget to give it a clap, and please do share your thoughts in the comment section. Thanks for taking your time and reading my story.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9610c34ee5e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>