<?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 Anur on Medium]]></title>
        <description><![CDATA[Stories by Anur on Medium]]></description>
        <link>https://medium.com/@annurbecirovic?source=rss-65db4f50a93------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0FhBxsBoMkt4bM-S_GzM3Q.jpeg</url>
            <title>Stories by Anur on Medium</title>
            <link>https://medium.com/@annurbecirovic?source=rss-65db4f50a93------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:58:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@annurbecirovic/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[From Vision to Reality: The Making of Comit]]></title>
            <link>https://medium.com/@annurbecirovic/from-vision-to-reality-the-making-of-comit-97a4d2d91dce?source=rss-65db4f50a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/97a4d2d91dce</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[storytelling]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[Anur]]></dc:creator>
            <pubDate>Mon, 27 Jan 2025 19:09:57 GMT</pubDate>
            <atom:updated>2025-01-27T19:09:57.394Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MV2UznVEbeSzX0g_jExeeA.png" /></figure><p>What if personal growth felt as rewarding as watching your own garden flourish — one seed at a time?</p><p>That question is at the heart of Comit, an app designed to make self-help personal, meaningful, and inspiring. Comit isn’t just an app; it’s the culmination of years of lessons, struggles, and discoveries. It’s a tool created to simplify personal growth and make it accessible to everyone, one step at a time. Here’s the story of how Comit came to life.</p><h3>The Spark: Where Comit Began</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*Zsky2PMMmBJDQ-D6jD1yPw.png" /><figcaption>Comit Logo (since 2021)</figcaption></figure><p>The idea for Comit began long before a single line of code was written. Back in 2021, I started with a rough logo and a broad vision. Initially, Comit was intended to be a platform for influencers and coaches to create community challenges and engage followers more meaningfully. I imagined brands like Red Bull and Nike leveraging the platform, but something felt off. Despite investor interest and hours spent on pitches, I couldn’t shake the feeling that this idea lacked the personal connection I craved.</p><p>This realisation led me to pause and reflect on what truly drives meaningful impact. I knew I wanted to create something I was deeply passionate about — something that would help people grow in a way that felt authentic, sustainable, and personal.</p><h3>Chasing Purpose</h3><p>At the time, I was working for a company that builds startups, giving me a front-row seat to the realities of entrepreneurship. I learned invaluable lessons about product-market fit, team building, and creating impactful solutions. But I wanted more. So, I made a bold move: I relocated to Stockholm, a city known for its thriving startup scene and innovative spirit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*weSagW18iXIx-oUfImo9fw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@aabergkvist?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Axel Antas-Bergkvist</a> on <a href="https://unsplash.com/photos/white-and-blue-boat-on-sea-during-daytime-sakSmrEMfO0?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Unsplash</a></figcaption></figure><p>In Stockholm, I joined a company with a mission I deeply believe in — making the world free from trash. For nearly three years, I contributed to this vision, learning how to build something impactful. But during this journey, another passion kept calling: helping people improve their mental well-being. Drawing from my own experiences, I began to explore how I could make a difference in this space.</p><h3>A Journey to Helping Others</h3><p>Improving mental well-being has been a deeply personal journey for me since 2014. Along the way, I realised that having the right tools and guidance can make all the difference. Comit is my way of sharing what I’ve learned and providing others with personalised tools that make growth accessible, empowering, and impactful.</p><h3>Reimagining Comit: A Fresh Perspective</h3><p>Fast forward to 2024. Fueled by a New Year’s resolution and a determination to stop making excuses, I decided to revisit Comit. This time, I focused on creating something I was truly passionate about: personalised self-help support.</p><p>The challenge was clear: personal growth is deeply individual. What works for one person might not work for another. Traditional self-help tools often lack personalisation and leave users feeling disconnected. I wanted to change that.</p><h3>The Power of Personalisation</h3><p>How do you make personal growth truly personal? That question became the cornerstone of Comit’s development. Using AI, Comit adapts to each user’s unique journey. By analysing inputs like mood logs and habits, it recommends tailored practices designed to resonate. This dynamic approach ensures that every user feels supported and understood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/948/1*bDT5aIcdwUD6QkfCq3nBLw.png" /><figcaption>Stress and Anxiety management widget system</figcaption></figure><p>AI also tackles the common barriers of cost and accessibility associated with traditional coaching. Comit bridges that gap, offering a tool that’s not only adaptive but also inclusive.</p><h3>Gamification and the Virtual Garden</h3><p>Enter Comit’s most unique feature: the virtual garden. Imagine planting the seed of a goal. Each time you work toward it, your plant grows. After a week of consistent effort, it blossoms into fruit. Over time, your garden becomes a vibrant, visual representation of your progress.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fgAO7PBf2nm2wu_TuzktbQ.png" /><figcaption>One of the 3D plants available in the App</figcaption></figure><p>The space theme adds a surreal, calming touch. Unlike other apps with bright, clinical designs, Comit’s space garden creates an environment of limitless potential. Growth feels expansive and uniquely your own.</p><h3>The People Behind Comit</h3><p>Comit wouldn’t exist without the incredible contributions of a dedicated team. Each member has left their mark:</p><p><strong>Emina</strong>, my co-founder and fiancée, challenges me to think inclusively, pushing Comit to be accessible and impactful for everyone.<br><strong>Danijel</strong>, our AI innovator, ensures personalisation lies at the heart of Comit’s functionality.<br><strong>Imad</strong>, my brother, brought the space garden to life with magical, visually captivating designs.<br><strong>Adisa</strong>, our designer, shaped Comit’s identity with her creative brilliance.<br><strong>Mustafa</strong>, our advisor and my personal mentor during my mental health journey, introduced the concept of the “<strong>Intronaut</strong>” — a metaphorical explorer of the mind that perfectly aligns with Comit’s space theme.</p><p>To our early testers, coaches, and advisors: your feedback and insights have been invaluable. <strong>Comit is as much yours as it is mine.</strong></p><h3><strong>Expanding Comit: Beta Testing and More</strong></h3><p>Soon, Comit will be available for more beta testers on both <strong>Android</strong> and <strong>iOS</strong>. We’re refining the experience, balancing free and paid versions to ensure meaningful value before launching to the world.</p><h4><strong>Balancing Passion and Priorities</strong></h4><p>Building Comit has been a labor of love — a journey carefully balanced alongside my full-time job. Progress may not always be fast, but every step forward is intentional and meaningful. Comit represents years of learning, growth, and resilience.</p><h4>Your Journey Awaits</h4><p>The journey is far from over. Comit is no longer just an idea; it’s a growing garden, a space-themed sanctuary, and a tool to make mental well-being more accessible and engaging.</p><p><strong>Are you ready to start your journey and grow your own space garden? Let’s do this together — one seed, one day, one goal at a time.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97a4d2d91dce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essential decisions when writing a new React app]]></title>
            <link>https://medium.com/mop-developers/essential-decisions-when-writing-a-new-react-app-2f6b41412632?source=rss-65db4f50a93------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f6b41412632</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[tutorial]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Anur]]></dc:creator>
            <pubDate>Mon, 29 Nov 2021 09:42:20 GMT</pubDate>
            <atom:updated>2021-11-29T09:42:20.309Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b3NeOhx4CkpWzRpU2WaI2A.jpeg" /></figure><p>Starting a new React project sounds like an easy task. We usually run <strong>npx create-react-app</strong> and the job is almost done. Eventually, we remove the Reactjs logo and change it to “<strong>This works</strong>”, grab our coffee and enjoy watching some Youtube “Day in the life of software developer” videos.</p><p>But then, we get our first assignment and it’s time to get <em>funky</em>.</p><h3><strong>In this article, we will cover:</strong></h3><ol><li><em>Typescript vs. Javascript</em></li><li><em>Localization</em></li><li><em>React components</em></li><li><em>Lint and Prettier</em></li></ol><h3><strong><em>Typescript vs. Javascript</em></strong></h3><p>For most of my work, I used plain javascript and got comfortable with it, probably after watching a lot of Udemy courses from Stephen Grider. But on my latest project, I discovered how typescript can change your life.</p><p>Typescript forces you to write as you should. It doesn’t leave you much space to be wild and send some props from one component to another without explaining them first. Before, I would spend hours to find that one variable that I mispronounced but with typescript that is just not possible.</p><p>The only downside is that you need to spend more time writing the interfaces and types, but if you work in larger teams that is beneficial in the long run.</p><p>I also support javascript. On my personal projects, I usually skip typescript and make sure I don’t make some huge mistakes in the coding process.</p><p><em>I still didn’t convince you to use Typescript?</em></p><p>Creating a <strong>Button</strong> (must in any project) or any custom component using typescript can save you a lot of time and for example, we will first write code in javascript and it usually looks like this.</p><pre>const Button = (props) =&gt; { const {variant} = props; <br>... <br>}</pre><p><em>Ok, ok I know we can also write it this way :</em></p><pre>const Button = ({ variant }) =&gt; {<br>...<br>}</pre><p>It will work, but there will be no options showed for you to decide what type of variant there is. Where in the next case:</p><pre>import React from &#39;react&#39;;</pre><pre>export interface ButtonProps { <br>variant?: &#39;primary&#39; | &#39;rounded&#39; | undefined;<br>}</pre><pre>const Button: React.FC&lt;ButtonProps&gt; = ({ variant, ... }) =&gt; <br>{ ... }</pre><p>It will be much clearer what you can use. Autocomplete will help you.</p><p>So, if you still cannot decide, investigate the pros and cons of using both and remember the only important thing is to enjoy the process.</p><h3><strong><em>Localization</em></strong></h3><p><a href="https://www.statista.com/statistics/266808/the-most-spoken-languages-worldwide/">Statistics</a> showed that in 2021, there were around 1.35 billion people worldwide who spoke English either as the first or as the second language, and most of the web applications don’t bother with introducing the localization in their app, especially if the app is in MVP (Minimum Valuable Product) state.</p><p>But this is one of those things that can backfire on you later on so it’s much better to spend few more minutes now and I will show you how.</p><pre>yarn add react-localization</pre><p>Create a new folder inside your <em>src</em> folder called translations and add <em>en.json </em>that looks something like this</p><pre>//translations &gt; en.json<br>{<br>  &quot;login&quot;: &quot;Please login to get started&quot;,<br>  ....<br>}</pre><p>We need to create a configuration for accessing these files in the same folder as the translation</p><pre>//translations &gt; index.ts</pre><pre>import LocalizedStrings from &#39;react-localization&#39;;</pre><pre>import en from &#39;./en.json&#39;;</pre><pre>const strings = new LocalizedStrings({ en });</pre><pre>export { strings };</pre><p>And the way we can use it is just by importing it and defining the key value.</p><pre>import React from &#39;react&#39;;<br>import { strings } from &#39;../translations;</pre><pre>const Login: React.FC = () =&gt; { &lt;div&gt;{strings.login}&lt;/div&gt; }</pre><pre>export default Login;</pre><p>One more, great feature of doing it this way is that you will have to autocomplete when you start typing (<em>strings. [autocomplete_key]).</em></p><h3>React components</h3><p>After a few months of working with libraries like MaterialUI, I realised that you will achieve a much faster development time of the app. However, that became obsolete in the web world, especially because designers are aiming at new standards with the general layout of the app.</p><p>Of course, we have tools and options to achieve the same things with MaterialUI but in the end, sometimes you just need to do this by yourself without installing large libraries like this one</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*z1xhA7F0r6N-DyZR9A9Vuw.png" /><figcaption>packagephobia.com</figcaption></figure><p>If you just want to use some of the components is it really worth it?</p><p>On most of my projects the components are written from scratch and for styling I usually use <strong>scss</strong> that is recommended by many other developers including me.</p><pre>yarn add node-sass</pre><p>There were few issues with this library, so if you want to be sure it’s working install a specific version: “node-sass”: “4.14.1”. And that is it, you can change all of your files like index.css or App.css to <strong>App.scss.</strong></p><p>Let&#39;s create the Login component with simple stying using scss.</p><ol><li>Create a folder inside src and name it Login</li><li>Inside the folder create these 3 files: <em>Login.tsx, Login.module.scss, index.ts</em></li><li>Start coding!</li></ol><pre>//Login.module.scss<br>@import &#39;../shared/theme/global.scss&#39;;<br>// I assume you will ask what is this line above. With scss we can create global configuration that we can import to any scss file and use it.</pre><pre>.main {<br>    display: flex;<br>    justify-content: center;<br>    align-items: center;<br>    .label {<br>        font-size: 16px;<br>        color: $red;<br>    }<br>}</pre><p>This is just simple stying we applied to make everything inside the main div centered. And also, as we already mentioned above the global configuration, let’s add that really quickly</p><pre>//global.scss<br>$red: #CD4040;</pre><p>This will allow you to change colors in the whole application without manually going through the files and changing them one by one.</p><pre>//Login.tsx</pre><pre>import { FC } from &#39;react&#39;;<br>import styles from &#39;./Login.module.scss&#39;;<br>import { strings } from &#39;../../translations;</pre><pre>const Login: FC = () =&gt; {<br> &lt;div className={styles.main}&gt;<br>   &lt;h1 className={styles.label}&gt;{strings.login}&lt;/h1&gt;<br> &lt;/div&gt;<br>}</pre><pre>export default Login;</pre><p>And at the end, we will just use index.ts for convenient import inside other components.</p><pre>//index.ts<br>import Login from &#39;./Login&#39;;<br>export { Login };</pre><p>The good thing about using this approach with <strong>scss</strong> files is that each element will be <strong>unique </strong>and will be compiled to <em>Component_class_random_text. </em>(You can inspect this inside the chrome console.)</p><p>The example above will be converted into <strong><em>Login_main__FD4NA</em></strong><em>.</em></p><h3>Lint and Prettier</h3><p>Before starting the journey of creating an amazing web app, we should consider importing these two into our project. It will allow us to see all the files that have been imported but not used and many more things that will make our life easier if we want to write a clean code.</p><h4>Lint vs. Prettier</h4><p>Check out this <a href="https://prettier.io/docs/en/comparison.html">documentation</a> if you want to investigate more about the differences but the bottom line is this: <strong>Use Prettier for formatting and linters for catching bugs</strong>. So, basically you need both to achieve a clean structure of your code.</p><h4><strong>Lint</strong></h4><p>In your project, you should add a couple of configuration files and packages as devDependency to make lint work.</p><pre>yarn add eslint -D</pre><p>After the successful installation you should run the command:</p><pre>npx eslint --init</pre><p>It will guide you to the setup process and there are few questions you need to answer. I will select in blue what you should pick.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0wiR2iMd5hCbshCyxea5Gw.png" /></figure><p>On the last question, I found it easier to just select the <strong>Yes</strong><em> </em>option and remove the <strong>package-lock.json, node_modules, yarn.lock, </strong>and run the <strong>yarn install</strong> command.</p><p>These steps will create a <strong>.eslintrc.js </strong>file at the root of your project and you can start adding custom rules or remove rules that you don’t need. Optionally you can create a <strong>.eslintignore </strong>file where you can specify things that should not fall into lint checks.</p><p>React comes with predefined lint rules. As we created our own configuration go to the <strong>package.json</strong> and <strong>remove</strong>:</p><pre>&quot;eslintConfig&quot;: {<br>  &quot;extends&quot;: [<br>    &quot;react-app&quot;,<br>    &quot;react-app/jest&quot;<br> ]<br>},</pre><p>The last thing we should do to finalize this step is to add the following line inside the <strong>“scripts”</strong> section:</p><pre>&quot;lint&quot;: &quot;eslint . --ext .js,.jsx,.ts,.tsx&quot;</pre><p>And run:<strong> yarn lint</strong> command</p><p>This will list all the files and warnings in your code. If you see this <strong>warning</strong> at the top of your list: <em>Warning: React version not specified in eslint-plugin-react settings. </em>In your <strong>.eslintrc.js </strong>file add:</p><pre>module.exports = {<br>   settings: {<br>     react: {<br>       version: &#39;detect&#39;<br>     },<br>   },<br>   ..... //rest of the configuration</pre><h4>Prettier</h4><p>We all have our own styles of coding and that can be seen if you start working on larger projects, so we call Prettier to the rescue. Let’s quickly set this up by running the command:</p><pre>npm install prettier -g</pre><p>This will install the prettier globally and now in our project directory install</p><pre>yarn add prettier -D</pre><p>At the root of the project we need to create a file called <strong>.prettierrc.js </strong>and add some rules inside that we want to follow:</p><pre>module.exports = {<br>  bracketSpacing: true,<br>  jsxBracketSameLine: true,<br>  singleQuote: true,<br>  trailingComma: &#39;all&#39;,<br>  printWidth: 100,<br>};</pre><p>You can check what each of these rules means <a href="https://prettier.io/docs/en/options.html">here</a>.</p><p>To integrate prettier with ESLint we will need few more packages.</p><pre>yarn add eslint-config-prettier eslint-plugin-prettier -D</pre><p><strong>eslint-plugin-prettier</strong>: Runs <a href="https://github.com/prettier/prettier">Prettier</a> as an <a href="http://eslint.org/">ESLint</a> rule and reports differences as individual ESLint issues.</p><p><strong>eslint-config-prettier</strong>: Turns off all rules that are unnecessary or might conflict with <a href="https://github.com/prettier/prettier">Prettier</a>.</p><p><em>Make sure if you are using Visual Studio Code to install the </em><strong><em>Prettier — Code formatter</em></strong><em> extension.</em></p><blockquote>If you are just starting with React or have been working for a long time these steps will help you to have that clean and painless architecture that you always wanted. Feel free to ask questions and stay tuned for <strong>Part 2</strong>.</blockquote><blockquote>Rome Wasn’t Built in a Day, But They Were Laying Bricks Every Hour — John Heywood</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f6b41412632" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mop-developers/essential-decisions-when-writing-a-new-react-app-2f6b41412632">Essential decisions when writing a new React app</a> was originally published in <a href="https://medium.com/mop-developers">Ministry of Programming — Technology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>