<?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 Adnan Sahinovic on Medium]]></title>
        <description><![CDATA[Stories by Adnan Sahinovic on Medium]]></description>
        <link>https://medium.com/@i-ads?source=rss-9e88cd96a7eb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*bjCd8AP6Rzk_xGlK8oUGtg@2x.jpeg</url>
            <title>Stories by Adnan Sahinovic on Medium</title>
            <link>https://medium.com/@i-ads?source=rss-9e88cd96a7eb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:42:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@i-ads/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[80+ Commands To Bookmark For React Native]]></title>
            <link>https://i-ads.medium.com/80-commands-to-bookmark-for-react-native-687d285bbf72?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/687d285bbf72</guid>
            <category><![CDATA[react-native-developers]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react-native-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Tue, 08 Oct 2024 07:56:11 GMT</pubDate>
            <atom:updated>2024-10-13T02:41:14.336Z</atom:updated>
            <content:encoded><![CDATA[<p>A list of commands with explanations every <strong>React Native developer</strong> should bookmark for the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bMY1TMmkJpkywCjOme7phw@2x.jpeg" /><figcaption>Photo by <a href="http://christinhumephoto.com/">Christin Hume</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Since React Native is multi-platform, we will divide this into four sections: iOS, Android, Expo, and React Native core commands.</p><h3>1. iOS Commands</h3><p>Commands to help you with the iOS development and Xcode:</p><p><strong>1. Open the project in Xcode</strong></p><pre>open ios/YourApp.xcworkspace</pre><ul><li>Opens the iOS project in Xcode, allowing you to build, run, and modify native iOS configurations.</li></ul><p><strong>2. Install iOS dependencies</strong></p><pre>pod-install</pre><ul><li>Installs CocoaPods dependencies listed in the Podfile for the iOS project. It ensures all required libraries are installed.</li></ul><p><strong>3. Update iOS dependencies</strong></p><pre>pod repo update</pre><ul><li>Updates the local CocoaPods repository to retrieve the latest versions of dependencies before installation. When to use: If you encounter an error about missing pod versions or outdated dependencies.</li></ul><p><strong>4. Reintegrate iOS dependencies</strong></p><pre>pod reingrate</pre><ul><li>Reintegrates CocoaPods dependencies into your Xcode workspace, which is useful when issues arise with installed libraries.</li></ul><p><strong>5. Install pods from Podfile and update the local CocoaPods repository</strong></p><pre>pod install - repo-update</pre><ul><li>Installs the necessary CocoaPods while updating the local repository to the latest version.</li></ul><p><strong>6. Clean iOS build</strong></p><pre>xcodebuild clean -workspace ios/YourApp.xcworkspace -scheme YourApp -configuration Debug</pre><ul><li>Cleans the iOS build artifacts, which is often necessary when encountering build errors.</li></ul><p><strong>7. Archive iOS App</strong> (submission to the App Store):</p><pre>xcodebuild -workspace ios/YourApp.xcworkspace -scheme YourApp -sdk iphoneos -configuration Release archive -archivePath ios/build/YourApp.xcarchive</pre><ul><li>Prepares the iOS app for submission to the App Store by creating an archived build.</li></ul><p><strong>8. Xcode Build</strong></p><pre>xcodebuild -workspace ios/YourApp.xcworkspace -scheme YourApp -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build</pre><ul><li>Builds the iOS app for development and testing on an iOS simulator.</li></ul><p><strong>9. Delete Pods</strong></p><pre>rm -rf ios/Pods</pre><ul><li>Removes all installed CocoaPods from the Pods folder.</li></ul><p><strong>10. Delete Podfile.lock</strong></p><pre>rm -rf ios/Pods</pre><ul><li>Deletes the Podfile.lock, which is useful for resetting your pod setup before reinstalling dependencies.</li></ul><p><strong>11. Clean derivated data</strong></p><pre>rm -rf ~/Library/Developer/Xcode/DerivedData/*</pre><ul><li>Cleans Xcode’s cached data, which is useful for resolving compilation issues or stale cache problems.</li></ul><p><strong>12. List connected devices</strong></p><pre>xcrun xctrace list devices</pre><ul><li>Lists all connected iOS devices and simulators for testing or debugging.</li></ul><p><strong>13. Clean Xcode build cache</strong></p><pre>rm -rf ~/Library/Developer/Xcode/DerivedData/*</pre><ul><li>Cleans the Xcode build cache to resolve potential caching issues during builds.</li></ul><p><strong>14. Pod update</strong></p><pre>cd ios &amp;&amp; pod update</pre><ol><li>Updates installed CocoaPods to the latest versions.</li></ol><h3>2. Android</h3><p>Native commands to help you with the Android development:</p><p><strong>14. Run the app on Android</strong></p><pre>react-native run-android</pre><ul><li>Builds and runs the Android app on a connected device or emulator. This is the most common command to launch the app during development.</li></ul><p><strong>15. List of open devices</strong></p><pre>adb devices</pre><ul><li>Lists all Android devices and emulators that are connected to your system. Useful to check if a device is ready for testing.</li></ul><p><strong>16. Clean Gradle</strong></p><pre>./gradlew clean</pre><ul><li>Cleans the Gradle build files, clearing any temporary files or cached data that might cause issues with the build process.</li></ul><p><strong>17. Build Gradle</strong></p><pre>./gradlew build</pre><ul><li>Compiles and builds the Android project using Gradle. This prepares the app for deployment or testing.</li></ul><p><strong>18. Debug connected devices</strong></p><pre>adb logcat</pre><ul><li>Streams logs from connected Android devices or emulators. Useful for debugging and monitoring app performance or errors.</li></ul><p><strong>19. Debug connected devices (filter by app)</strong></p><pre>adb logcat | grep com.app.name</pre><ul><li>Filters the log output to display logs specific to your app’s package name. This helps you pinpoint issues related to your app more quickly.</li></ul><p><strong>20. Build APK for testing</strong></p><pre>cd android &amp;&amp; ./gradlew assembleDebug</pre><ul><li>This command generates a debug APK that can be installed on devices for testing purposes. This APK contains extra debugging information.</li></ul><p><strong>21. Generate a signed app for production</strong></p><pre>cd android &amp;&amp; ./gradlew assembleRelease</pre><ul><li>Builds a signed release APK suitable for submission to the Google Play Store. This APK is optimized for performance and security.</li></ul><p><strong>22. Open Android emulator</strong></p><pre>emulator -avd &lt;your_avd_name&gt;</pre><ul><li>Launches the specified Android emulator using the name of your Android Virtual Device (AVD).</li></ul><p><strong>23. Open Android Logcat for debugging</strong></p><pre>adb logcat *:S ReactNative:V ReactNativeJS:V</pre><ul><li>Opens Android’s logcat for detailed logging but only shows logs related to React Native and JavaScript activity to help filter out noise and focus on relevant logs.</li></ul><p><strong>24. Uninstall app from Android</strong></p><pre>adb uninstall com.projectname</pre><ul><li>Uninstall your app from a connected Android device or emulator using the app’s package name.</li></ul><p><strong>25. Install .apk on device</strong></p><pre>adb install path_to_apk.apk</pre><ul><li>Installs a specific APK file on a connected Android device or emulator for testing or debugging purposes.</li></ul><p><strong>26. Run adb reverse (for device debugging):</strong></p><pre>adb reverse tcp:8081 tcp:8081</pre><ul><li>Sets up reverse port forwarding, allowing the device to connect to the local development server (Metro) running on your machine. Useful for debugging on real devices.</li></ul><p><strong>27. Clear Android build cache:</strong></p><pre>cd android &amp;&amp; ./gradlew cleanBuildCache</pre><ol><li>Clears the Android build cache. This can resolve issues caused by stale build files or cache corruption when building the Android project.</li></ol><h3>3. React Native</h3><p>React Native CLI commands:</p><p><strong>28. Initialize a new project</strong></p><pre>react-native init ProjectName</pre><ul><li>Initializes a brand new React Native project. This sets up the project structure and installs all necessary dependencies.</li></ul><p><strong>29. Run the project on iOS</strong></p><pre>react-native run-ios</pre><p><strong>30. Run the project on Android</strong></p><pre>react-native run-android</pre><p><strong>31. Run the project on a specific iOS simulator</strong></p><pre>react-native run-ios --simulator=&quot;iPhone 14&quot;</pre><p><strong>32. Install project dependencies</strong></p><pre>npm install or yarn install</pre><ul><li>Installs all the project’s dependencies listed in package.json</li></ul><p><strong>33. Link dependencies (for versions below 0.60):</strong></p><pre>react-native link</pre><ul><li>Before React Native 0.60, linking was required to connect native modules to the iOS and Android projects.</li></ul><p><strong>34. Unlink a package</strong></p><pre>react-native unlink package-name</pre><ul><li>This command removes the link to a specific package from your project. It works only on RN 0.60 and earlier.</li></ul><p><strong>35. Open DevTools</strong></p><pre>react-devtools</pre><ul><li>Opens React Native DevTools and provides tools to inspect and debug React components.</li></ul><p><strong>36. Check for outdated packages</strong></p><pre>npm outdated or yarn outdated</pre><ul><li>Checks for outdated dependencies in the project. It shows which packages have newer versions available.</li></ul><p><strong>37. Upgrade the project to the latest version</strong></p><pre>react-native upgrade</pre><ul><li>Updates the React Native version in your project to the latest stable release. Don&#39;t use for larger and projects with multiple native libraries.</li></ul><p><strong>38. Start a metro bundler</strong></p><pre>npm start</pre><ul><li>Starts the Metro bundler, which bundles the JavaScript code for the app and makes it available for development. It is essential for running and testing your app.</li></ul><p><strong>39. Clear cache &amp; start Metro Bundler</strong></p><pre>npm start --reset-cache</pre><p><strong>40. Run React Native in release mode (iOS)</strong></p><pre>react-native run-ios --configuration Release</pre><ul><li>Builds and runs the iOS app in release mode, creating an optimized build for production testing.</li></ul><p><strong>41. Run React Native in release mode (Android)</strong></p><pre>react-native run-android --variant=release</pre><ul><li>Builds and runs the Android app in release mode, optimized for production. This is used for final testing before releasing the app.</li></ul><p><strong>42. Run Yest test</strong></p><pre>npm test or yarn test</pre><ul><li>The command that runs all the <strong>yest</strong> tests in your project</li></ul><p><strong>43. Run Eslint</strong></p><pre>eslint .</pre><ul><li>Runs ESLint to check your codebase for potential errors, warnings, or style issues based on the rules defined in the ESLint configuration file.</li></ul><p><strong>44. Fix Eslint issues</strong></p><pre>eslint . --fix</pre><ul><li>Auto fixes linting issues in your codebase based on the defined ESLint rules.</li></ul><p><strong>45. Run Prettier</strong></p><pre>prettier --write .</pre><ul><li>This command formats your code according to the rules defined in your Prettier configuration.</li></ul><p><strong>46. Run Detox (testing)</strong></p><pre>detox tes</pre><h3>4. Expo</h3><p>Expo CLI commands:</p><p><strong>47. Create a new Expo project</strong></p><pre>create-expo-app ProjectName</pre><p><strong>48. Installing Expo</strong></p><pre>yarn add expo</pre><ul><li>It adds Expo as a dependency to an existing project, which is useful when integrating Expo into an existing React Native CLI project.</li></ul><p><strong>49. Run Expo App (Android)</strong></p><pre>expo start --android</pre><p><strong>50. Run Expo App (iOS)</strong></p><pre>expo start --ios</pre><p><strong>51. Run Expo App</strong></p><pre>expo start --ios</pre><p><strong>52. Expo login</strong></p><pre>expo login -h</pre><ul><li>Logs into your Expo account from the command line, required for publishing apps or using Expo services.</li></ul><p><strong>53. Open project in Expo DevTools</strong></p><pre> expo start --dev-client</pre><ul><li>Starts the Expo project with DevTools, allowing you to debug the app in a custom development client.</li></ul><p><strong>54. Clear Expo app</strong></p><pre>expo eject</pre><ul><li>Ejects the Expo, allowing for full native customization.</li></ul><p><strong>55. Publishing Expo</strong></p><pre>expo publish</pre><ul><li>Publishes the Expo project to the cloud, allowing users to access it via a permanent URL or the Expo Go app.</li></ul><p><strong>56. Build a project for production (iOS)</strong></p><pre>expo build:ios</pre><ul><li>Builds the app for production on iOS, generating a .ipa file for submission to the App Store.</li></ul><p><strong>57. Build a project for production (Android)</strong></p><pre>expo build:android</pre><ul><li>Builds the app for production on Android, generating an .apk or .aab file for submission to the Google Play Store.</li></ul><p><strong>58. Create Expo development build</strong></p><pre>expo run:ios or expo run:android</pre><ul><li>Creates a local development build of the Expo app to be run.</li></ul><p><strong>59. Build for web</strong></p><pre>expo build:web</pre><ul><li>Builds the project for the web platform, creating optimized assets and bundles for a web deployment.</li></ul><p><strong>60. Optimize assets for production</strong></p><pre>expo-optimize</pre><ul><li>Optimizes images and other static assets to reduce file sizes for faster load times in production.</li></ul><p><strong>61. Clear cache and start Expo</strong></p><pre>expo start -c</pre><ul><li>Clears the Expo cache and starts the development server, useful when encountering issues caused by cached data.</li></ul><p><strong>62. Install specific Expo package</strong></p><pre>expo install package-name</pre><ul><li>Installs a specific Expo-compatible package and ensures compatibility with the current SDK.</li></ul><p><strong>63. Upgrade Expo SDK</strong></p><pre>expo upgrade</pre><ul><li>Upgrades the Expo project to the latest SDK, ensuring compatibility with the latest features.</li></ul><p><strong>64. Configure iOS credentials</strong></p><pre>expo credentials:manager</pre><ul><li>Manages iOS credentials (provisioning profiles and certificates).</li></ul><p><strong>65. Check project configuration (app.json)</strong></p><pre>expo config</pre><ul><li>Displays the current configuration for the project as defined in app.json.</li></ul><p><strong>66. Run Expo Diagnostics</strong></p><pre>expo diagnostics</pre><ul><li>Gathers diagnostic information about your project setup, which is useful for troubleshooting issues or reporting bugs.</li></ul><p><strong>67. Expo</strong> <strong>Logout</strong></p><pre>expo logout</pre><ul><li>Logs out of the Expo account in the command line.</li></ul><p><strong>68. Build an app for EAS (Expo Application Services):</strong></p><pre>eas build</pre><ul><li>Builds the app using EAS, which supports iOS and Android building without the need to eject or leave the Expo.</li></ul><p><strong>69. Check your project’s build status (EAS):</strong></p><pre>eas build:status</pre><ul><li>Shows the status of the recent builds for your project in Expo Application Services.</li></ul><p><strong>70. Configure EAS for automatic app signing:</strong></p><pre>eas config</pre><ul><li>Configures the EAS service to handle your app&#39;s automatic signing and simplifies the submission process for iOS and Android.</li></ul><p><strong>71. View Expo logs:</strong></p><pre>expo logs</pre><ul><li>Displays logs generated by Expo, which help debug the Expo app during development.</li></ul><p><strong>72. Install Expo Updates:</strong></p><pre>npm install -g expo-cli or yarn global add expo-cli</pre><ul><li>Installs or updates the Expo CLI globally, ensuring you work with the latest version.</li></ul><p><strong>73. List All Available Expo Commands:</strong></p><pre>expo --help</pre><ul><li>Displays a list of all available Expo CLI commands with descriptions for each.</li></ul><p><strong>74. Check Expo&#39;s release notes:</strong></p><pre>expo release-notes</pre><ul><li>Displays the release notes for the latest Expo SDK, including updates and changes.</li></ul><p><strong>75. Check &amp; update project dependencies</strong></p><pre>expo doctor</pre><ul><li>This command checks and update your project’s dependencies to ensure they are compatible with the current Expo version.</li></ul><p><strong>76. Open Expo Documentation</strong></p><pre>expo docs</pre><p><strong>77. Configure OTA (Over The Air) updates:</strong></p><pre>expo publish --release-channel &lt;channel&gt;</pre><ul><li>Publishes an Over The Air (OTA) update to a specific release channel, allowing your app to receive updates without requiring a full app store submission.</li></ul><p><strong>78. Run app on specific release channel</strong></p><pre>expo start --release-channel &lt;channel-name&gt;</pre><ul><li>Runs the Expo app on a specific release channel, which is useful for testing different app versions.</li></ul><p><strong>79. Roll back to the previous update</strong></p><pre>expo publish:rollback</pre><ul><li>Rolls back the app to the previous OTA update, undoing the most recent changes.</li></ul><p><strong>80. Test deep-linking in the Expo project</strong></p><pre>expo start --scheme &lt;your-scheme&gt;</pre><ul><li>The command that tests deep linking for your Expo project by specifying a custom scheme to open the app.</li></ul><p><strong>81. Check the bundle size of an Expo project</strong></p><pre>expo bundle:analyze</pre><ul><li>Analyzes and provides a report on the bundle size, helping to optimize the app for faster load times.</li></ul><p><strong>82. Delete the Expo project from Expo&#39;s servers</strong></p><pre>expo delete</pre><ul><li>Command that will permanently delete the project from Expo’s servers, removing all published versions and data associated with it.</li></ul><p>Happy coding! 🎉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=687d285bbf72" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React & React Native: Measuring Screen Load Time]]></title>
            <link>https://medium.com/geekculture/performance-measuring-screen-load-time-0c3322b2a2a4?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c3322b2a2a4</guid>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Mon, 29 Apr 2024 15:13:53 GMT</pubDate>
            <atom:updated>2024-04-29T20:57:21.357Z</atom:updated>
            <content:encoded><![CDATA[<h4>An easy way to create custom performance monitoring for React and React Native apps</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L06rJWXCl_TNbznrJNnIEA@2x.jpeg" /><figcaption>Photo by Cody Fitzgerald on Unsplash</figcaption></figure><p>This article aims to measure the time it takes for a screen to load data and draw its UI elements. These steps must be taken before the user can interact with the UI.</p><p>Measuring load time is not just a task, it&#39;s a critical step to ensure a fast and smooth user experience. It&#39;s your key to determining if new feature development or refactoring positively or negatively impacted the app’s performance.</p><p>Rest assured, after finishing this guide, you’ll build a custom hook that can be seamlessly plugged into any React, or React Native app and start measuring load time.</p><h3>Implementation</h3><p>Let&#39;s dive into the implementation. Our first task is to define the properties we want to use. Our goal is to create a solution that can be effortlessly integrated into any screen and start measuring time.</p><ul><li>screenName: defined screen name</li><li>isLoading: indicating if loading is finished and a user can start with interaction</li></ul><p>With these two in place, we can start building a custom hook.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b070f47f2658f19ca629a51787104ac9/href">https://medium.com/media/b070f47f2658f19ca629a51787104ac9/href</a></iframe><ul><li>In useEffect we start measuring time with performance.now() once the user arrives on the screen and sets the start time.</li><li>The performance.now() method returns a high-resolution timestamp in milliseconds.</li><li>After the data is loaded, we set the endTime and calculate the time to load by measuring the difference between the end and start times.</li></ul><h3>Start Measuring</h3><p>Let’s simply use what we have built so far and start measuring time. To do this, we need to simply import and call useGetPerformance hook with its properties.</p><h4>React Native</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bfde0c4d3f9e0a862ce14954e853ad2f/href">https://medium.com/media/bfde0c4d3f9e0a862ce14954e853ad2f/href</a></iframe><h4>React</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/72994f82588580aff1f6490507982d98/href">https://medium.com/media/72994f82588580aff1f6490507982d98/href</a></iframe><p>Now, open a console; you should see a log message with calculated milliseconds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/454/1*pr7Tlt0BJpLgamhjlED7jQ.png" /><figcaption>results: time to load end render in milliseconds</figcaption></figure><blockquote>We usually want to log load time to monitor it in real-time and take action. You can start logging data using the Amplitude or Datadog event logging tool.</blockquote><p>Datadog: <a href="https://docs.datadoghq.com/service_management/events/">https://docs.datadoghq.com/service_management/events/</a></p><p>Amplitude: <a href="https://www.docs.developers.amplitude.com/">https://www.docs.developers.amplitude.com/</a></p><p>Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c3322b2a2a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/performance-measuring-screen-load-time-0c3322b2a2a4">React &amp; React Native: Measuring Screen Load Time</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software Mentoring: Five Important Lessons To Remember]]></title>
            <link>https://i-ads.medium.com/software-mentoring-five-important-lessons-to-remember-efcd34736616?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/efcd34736616</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mentorship]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Sat, 10 Feb 2024 17:03:50 GMT</pubDate>
            <atom:updated>2024-05-05T12:16:11.895Z</atom:updated>
            <content:encoded><![CDATA[<h4>If you’re starting with coding, this will help you navigate through mentorship. If you’re a mentor, this will help you make fewer mistakes I made.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*olzi74gD8TQYAkXW" /><figcaption>Photo by <a href="https://unsplash.com/@sigmund?utm_source=medium&amp;utm_medium=referral">Sigmund</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Mentorship is an essential process in the making of a software engineer. As a lead engineer, I often encounter mentoring as part of my daily job.</p><p>As a self-taught programmer, I understand the importance of having someone to support you and provide you with a stress-free environment to grow.</p><p>For junior developers, mentorship is like sailing in an open sea with a constant weather change. Your job as a mentor is to control this weather and ensure no storm is on the horizon.</p><p>Programmers usually come from different backgrounds. If someone is a good engineer, don’t expect him to be a good mentor. If someone has had a mentoring experience before, don’t expect him to communicate well or set expectations right.</p><p>I had a chance to mentor and teach over fifty software developers in my career, and some of them are working on large-scale projects and have a dream job they always wanted.</p><p>Along the way, I documented what worked and what did not. Here are the key mentoring takeaways from my experience:</p><h3>1. Set expectations early</h3><p>The earliest you set expectations, the better. I’ve found out that most of the problems come from unrealistic expectations or not setting expectations at all.</p><p>Mentorship is a two-way road, and mentors and mentees should communicate their expected goals. This doesn’t have to be formal or documented but has to happen at least as a dialogue.</p><blockquote>The better you lay, the more stable the mentorship process will be.</blockquote><p>Depending on the length of the mentorship, these goals should be adjusted to fit needs. Here is an example:</p><ul><li>1st month: Get to know the basics of frontend</li><li>2nd month: Understand business logic and backend</li><li>3rd month: Become an independent engineer</li></ul><blockquote><em>When setting learning milestones, you set a foundation for a successful mentorship.</em></blockquote><h3>2. Steer, but don’t drive the mentorship</h3><p>This is where a lot of new mentors make a mistake. It’s a thin line between trying to be too helpful and an over-controlling person.</p><p>Every relationship should start with trust. If you find yourself in a situation where you need to micromanage, something is wrong.</p><p>Don’t over-control anyone. Let the mentee have a space, but also help him steer in a pool of information.</p><p>No person can be forced to do something unless they think it benefits them. You should be gently guiding a person.</p><blockquote>You have to understand that mentees are sailing in a pool of information. Your job is to help them filter relevant information.</blockquote><p>Before mentee starts with their work, your job is to provide technical and business information about their upcoming work. The more context they have — the better job they can do.</p><h3>3. Don’t enforce your learning styles</h3><p>People tend to think their way of learning things is the best. I was this person for a long time. I’m the type of person who is methodical and always looking to learn something new, whether it is a course, book, or documentation.</p><blockquote>If someone doesn’t like reading books or tutorials, that’s fine. Let him find what works for him, but provide important guidelines.</blockquote><p>The big lesson I learned in the past few years is that not all of us have the same learning methods, discipline, and cognitive capacity.</p><h3>4. Lead with important conversations</h3><p>Crucial conversations are where emotions and stakes are high. Most junior programmers often have problems with self-confidence and reaching out to mentors.</p><p>These convos needs to happen and be initiated by you as a leader.</p><p>Keep in mind what you want out of these conversations, and your job as a mentor is to start these crucial talks.</p><h3>5. Track the progress</h3><p>Don’t just document progress, document every mistake you made and your key findings. If there is more than one mentee, it’s almost impossible to do it efficiently without tracking a progress.</p><p>Most of the developers don’t do mentoring as their primary job. There is regular work most of us have to do – because of this, you must document each step. This will help you not forget what was done perfectly and what needs to be improved.</p><blockquote>Tracking progress will help you manage your current mentorships and set a standard for future ones.</blockquote><p>There are no written rules, and you should create your tracking document. This document should hold the biggest wins and failures during a mentorship.</p><p>Every mentorship is a new opportunity for you as a mentor to expand and grow.</p><p>Everyone has different experiences when it comes to mentoring, and we are learning new things each day.</p><p>The most important thing is to be supportive and provide a clear growth plan. By being a good mentor and a leader, your job is to provide everything necessary for a student to grow.</p><p>Looking forward to hearing from other mentors and their experiences.</p><p>Happy mentoring!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=efcd34736616" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Simple Way To Store Data Into Google Sheets Using API]]></title>
            <link>https://medium.com/geekculture/a-simple-way-to-store-data-into-google-sheets-using-api-8e51005bd941?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e51005bd941</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[google-sheets]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Thu, 11 Jan 2024 16:35:33 GMT</pubDate>
            <atom:updated>2024-02-07T19:28:53.534Z</atom:updated>
            <content:encoded><![CDATA[<p>A simplistic guideline on how to store data in Google Sheets using an API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q49k1GMMNeByFZgC" /><figcaption>Photo by <a href="https://unsplash.com/@khachiksimonian?utm_source=medium&amp;utm_medium=referral">Khachik Simonian</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>Introduction</strong></h3><p>Often, developers need to store simple data that doesn’t require an SQL database or writing an API and connecting these two.</p><p>NoSQL is a good option but, again, requires a connection with your DB client and building an API layer.</p><p>After researching the simplest way to store textual data using just an API, I discovered that Google Sheets is a good and viable option.</p><p><em>For this tutorial, I chose a </em><a href="https://sheet.best/"><em>sheet. best</em></a><em> as it’s the best available Google Sheets wrapper option to store data – because it doesn’t require complicated Google setup + it’s less code, and it comes with many other features.</em></p><p>With sheets.best, everything is abstracted, and their service makes writing and querying sheets a piece of cake.</p><p>After completing the initial setup, you will receive a URL that will allow you to write and query data on the sheets.</p><h3><strong>1. Prepare your sheet</strong></h3><ul><li>Create a simple Google sheet with a minimum of one column.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*eaJS9V9dha96evWFO1Fdtw.png" /></figure><h3><strong>2. Connection URL</strong></h3><ul><li>Once you have created your sheet, click on the “Share” button and then copy the link provided.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*C2eK7nKiqXALjW--q96oYQ.gif" /></figure><blockquote>Note: Make sure to turn off restrictions so everyone can write to a file</blockquote><h3>3. Insert your Connection URL</h3><ul><li>Please log in to sheet.best account</li><li>After logging in, go to the initial page and click on the ‘+ CONNECTION’ button.</li><li>Input the title of your sheet and paste the link that you previously copied from Google Sheets.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8PC1tvlYvAqmM6OIXuYSw.gif" /></figure><h3>4. Write Data</h3><p>You can now connect to your sheet using an API via Postman or your client app.</p><blockquote>Make sure to use your own generated API URL from the dashboard.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t6alx-Qlgm3jeZMXhrXKdw.png" /></figure><p>🎊 Voila! You should see your data populated in Google Spreadsheets.</p><p>If you want to find out how to query data or any more advanced options, here is a link to the official documentation.</p><p><a href="https://sheetbestdocs.netlify.app/#get-read-rows">QuickStart</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e51005bd941" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/a-simple-way-to-store-data-into-google-sheets-using-api-8e51005bd941">A Simple Way To Store Data Into Google Sheets Using API</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What It Means To Be An Exceptional Manager]]></title>
            <link>https://i-ads.medium.com/what-it-means-to-be-an-exceptional-manager-35a1a12a420c?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/35a1a12a420c</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Wed, 03 Jan 2024 15:58:06 GMT</pubDate>
            <atom:updated>2024-05-05T12:17:33.021Z</atom:updated>
            <content:encoded><![CDATA[<p>What can you learn from others to become an exceptional engineering manager, and what core values set you apart from the rest of the world?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dfSSr8wGCGLkuHow" /><figcaption>Photo by <a href="https://unsplash.com/@supernov?utm_source=medium&amp;utm_medium=referral">Edi Libedinsky</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Story</h3><p>Being a manager is like fighting a 100-year-old stereotype that managers are evil and don&#39;t trust them by default. My manager told me this whenever I felt bad for being unable to solve a human problem.</p><p>Some people you meet during a career either help you grow or make your life a disaster. I am writing this story to thank a manager who taught me more than any book, more than any family member, or a course you can buy for only $999 and become a manager overnight.</p><p>As someone coming from a software world, where input is usually equal to output, and things are straightforward, becoming manager at first was the worst and the best decision I ever made.</p><p>I was making the same money, but the issues I was dealing with were beyond a bug fixing or a new feature request. Suddenly, I had to solve human problems — and humans are bundles of ego, emotions, and joy.</p><p>By default, I love to see everyone around me happy and cheerful, which is a lousy mentality if you want to manage and lead people. You can&#39;t please and make everyone happy, but you can support and be there for your people.</p><p>However, step by step, I picked up the most important parts, documented them, and observed what my manager did when things were going well and when things were going down.</p><blockquote>“Your life quality is as good as your manager is.”</blockquote><h3>Understanding Your People</h3><p>Understanding the people you manage, their habits, hobbies, and how they work is essential to becoming an exceptional manager.</p><p>You need to be able to put together different characters and steer them in the right direction. To do that, you need to understand deeply each of them, and that can only be done with 1:1 meetings.</p><p>Understanding your people means understanding what they want to become in life. Some want to become better engineers, others don&#39;t, and that&#39;s fine. As people go through different aging phases, their priorities shift, and you&#39;re the one to understand this and support their path.</p><h3>1:1 Meetings</h3><p>Never skip a 1:1 meeting, as this is the only moment to meet and pick up someone&#39;s brain — 1:1 is a place to meet your peers and bond with them.</p><p>Never start them straight with business, and try to use an introduction to ask how they feel and how their week was, rather than going into business first.</p><p>It&#39;s OK to spend this meeting talking about feelings. Sometimes, humans are going through a challenging period, and you need to be there and support them rather than talk about your following team goals.</p><h3>Trust &amp; Micromanage</h3><p>You always start a relationship with trust! If you need to micromanage someone too often, that usually means the person is not fit for a role.</p><p>There are rare times when micromanaging is okay, but if this is a regular part of your job, you are doing something wrong.</p><blockquote>Trust can be broken in a second, so always remember that.</blockquote><h3>Take Responsibility &amp; Never Blame Others</h3><p>When things go wrong (and they will 100%), never blame others and always be the first to take the blame and responsibility. This way, you will gain trust in a team, and people will feel safe around you.</p><p>Everyone makes a mistake, and our job as managers is to avoid repeating mistakes. Doing a post-mortem after mistakes are done is the best thing you can do to make sure things don&#39;t fall again the same way they did before.</p><p>I had a case when a junior developer almost broke the whole company by adding the correct code at the wrong time. <strong>I was the one who assigned him this task, and I was the one to blame and take responsibility.</strong></p><p>Later on, we had a post-mortem meeting and found a way never to make a similar error again. Usually, when things go down, this is the best time for learning opportunities, and don&#39;t waste it by putting things below the carpet.</p><h3>Solving Conflicts</h3><p>The first human conflict I had to solve left me sleepless for nights as I wasn&#39;t sure why two people didn&#39;t like working with each other while both of them were hardworking and good people in the first place.</p><blockquote>If you&#39;re becoming an engineering manager, solving human issues is the most challenging part of your new job.</blockquote><p>After days of chaos in my head, I asked my manager how to approach this problem. He said, &quot;Put them in the same room and let them talk to each other.&quot;</p><p>The first two minutes of this meeting were the worst gut feeling and pure awkwardness. But guess what? After spending half an hour together, they concluded, solved issues together, and became excellent friends and colleagues even to this day.</p><p>After some time had passed, I realized that as a manager, you don&#39;t need to be a bridge between two people and their problems. Putting them in the same room is already one step towards solving an issue.</p><blockquote>“You control the inputs, not the human outputs.”</blockquote><h3>Humans Over Technology</h3><p>If humans grow, technology will evolve. There is no single good-performing team with good developers who don&#39;t have significant interaction, don&#39;t bond, or hate working together.</p><blockquote>You should never jeopardize development but always put your people before technology.</blockquote><p>When people make mistakes or things go wrong, be there for them and support them. Our job is more than just building an app; it&#39;s about creating an environment where everyone will grow and learn.</p><p><strong>If people grow, technology will follow their growth.</strong></p><p>I learned many other things from having an exceptional manager; one article isn&#39;t enough to thank you.</p><p>I hope our paths will cross again, and I promise to keep your legacy and help others the way you helped me to become a better human and a leader.</p><p>Thank you, Michael!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35a1a12a420c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Event Logging with Amplitude & React Native]]></title>
            <link>https://i-ads.medium.com/event-logging-with-amplitude-react-native-0f7e972241e7?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/0f7e972241e7</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[event-tracking]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[amplitude]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Wed, 03 Jan 2024 09:28:39 GMT</pubDate>
            <atom:updated>2024-01-04T07:24:49.349Z</atom:updated>
            <content:encoded><![CDATA[<p>Short step-by-step guide on installing, logging events, and setting user properties with React Native and Amplitude</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jEdKG9CdJpbYCTS3" /><figcaption>Photo by <a href="https://unsplash.com/@jeremyperkins?utm_source=medium&amp;utm_medium=referral">Jeremy Perkins</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>1. Instal npm modules</strong></h3><p>Let&#39;s start by installing the dependencies we need to run Amplitude.</p><blockquote><strong>npm install </strong><a href="http://twitter.com/amplitude/react-native"><strong>@amplitude/react-native</strong></a></blockquote><p>or</p><blockquote><strong>yarn add </strong><a href="http://twitter.com/amplitude/react-native"><strong>@amplitude/react-native</strong></a></blockquote><p>if you want to make it work with iOS, you need to do an additional step and install pod files:</p><blockquote><strong>cd ios &amp;&amp; pod install</strong></blockquote><h3>2. Create a base code</h3><p>Initialize Amplitude and create helper functions we can reuse across the app.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c8774d6abe2de379f334d345789a493/href">https://medium.com/media/2c8774d6abe2de379f334d345789a493/href</a></iframe><blockquote>Remember to add your API key and set any user property you wish to track</blockquote><h3>3. Log events and set user properties</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c4937e1386dd1c91c726199aeec6852a/href">https://medium.com/media/c4937e1386dd1c91c726199aeec6852a/href</a></iframe><p>Make sure to rebuild your app, and you’re good to start capturing user events with Amplitude.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0f7e972241e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Steps To Build A Perfectly-Sized Software Team]]></title>
            <link>https://i-ads.medium.com/steps-to-build-a-perfectly-size-software-team-b015df678e5?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/b015df678e5</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Mon, 18 Dec 2023 12:47:32 GMT</pubDate>
            <atom:updated>2024-01-04T07:25:07.479Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using the Dunbar Numbers to calculate perfectly sized cohesive software teams</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M8yezdvg_aFBdcXk" /><figcaption>Photo by <a href="https://unsplash.com/@museumsvictoria?utm_source=medium&amp;utm_medium=referral">Museums Victoria</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>A good team is a combination of capabilities and interactions; it is more than the sum of the parts.</blockquote><h3>Introduction</h3><p>Most software developers had experience working in understaffed or overstaffed teams. I can’t remember how often teams tried solving productivity issues by adding just one more developer.</p><p>Adding a new developer is more complex than it seems at first. Firstly, it takes time to onboard and get him up to speed; secondly, it adds communication load to existing team members.</p><p>Different companies have different rules. Amazon tends to organize small teams (max five people), and their rule of thumb is if the group can be fed with two pizzas, they’re perfectly sized.</p><p>According to Scrum, the ideal software team size is <strong>between three and nine members</strong>, with seven being the best match.</p><p>However, the ideal team number depends on various facts. When forming a development team, it is essential to consider the team&#39;s needs and not just random numbers. Here are some factors to consider:</p><ul><li><strong>Team: </strong>The<strong> </strong>team<strong> </strong>should have the skill set to build the product.</li><li><strong>Availability</strong>: Ideally, each team member works on just one project at a time.</li><li><strong>Stability</strong>: The members spend significant time on this team and must be reliable.</li><li><strong>Diversity: </strong>A wide array of ideas, backgrounds, beliefs, and life experiences might be helpful for creativity and versatility of approaches.</li><li><strong>Psychological safety</strong>: The environment within the team should be favorable so that the team members can share ideas.</li><li><strong>Communication Equality:</strong> Each team member should be able to speak their mind and be heard</li><li><strong>Manager</strong>: How many people the team leader can manage well</li><li><strong>Types of work</strong>: The kind of work done in the team</li><li><strong>Team overall demographics</strong>: The age and personality of the team (not the team members)</li></ul><h3>Communication Load</h3><p>Each new member adds productivity to the team but increases the communication load.</p><p><strong>A formula is applied: N (N — 1) / 2.</strong></p><p>The formula shows how many interactions will be within teams of different sizes.</p><ul><li>N is the number of people on the team.</li><li>In a team of <strong>five</strong>, there will be ten interactions. This means ten different combinations of communication among the team members.</li><li>In a team of <strong>seven</strong> members, there will be 21 interactions.</li><li>In a team of <strong>nine</strong>, there will be 36 interactions.</li></ul><p>An increase in team size from <strong>five</strong> <strong>to seven members almost doubles the communication load,</strong> which can hurt productivity after a certain point.</p><p>When adding new members, the team needs to put extra effort into onboarding and bringing them up to speed. And all that time not spent developing the project means the performance could be better.</p><p>To avoid this challenge, understaffing the team initially with the intent of growing it later is a good solution.</p><blockquote>When planning team size, make sure to take the communication load into calculation.</blockquote><h3><strong>The Dunbar Numbers</strong></h3><blockquote><strong>The Dunbar Number</strong>, named after anthropologist Robin Dunbar, is the maximum number of social connections a human can actively maintain. It’s based on studies in the early 90s attempting to quantify our brain sizes and behavior.</blockquote><p>5, 15, 50, and 150 are essential numbers to consider when considering group size and workplace productivity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oJhVYepPZr63dQhNgXLseQ.png" /><figcaption>Dunbar’s optimal team numbers</figcaption></figure><blockquote><em>Human capacity is an essential constraint in steering team building.</em></blockquote><h3>Groups of 5 People</h3><p><strong>Dunbar’s numbers</strong> tell us that around five people can closely trust each other. Trust is a crucial thing, being a necessity for <em>psychological safety.</em></p><p>Smaller teams benefit from stronger bonds, which keep work focused and contained and provide less room for social loafing.</p><blockquote><em>Assuming meetings are productive, everyone is </em>contributing, <em>and goals are being met, teams of around five people are optimal for maximum productivity.</em></blockquote><h3>Groups of 15 People</h3><p>Dunbar says, &quot;Fifteen is the number of good friends in our inner circle — friends we interact with regularly and have strong bonds with, including our five best friends. You can turn to these people for help whenever you need it.&quot;</p><p>People-to-manager ratios of 15:1 tend to be an upper boundary, as connections between members become geometrically more complex and more difficult to manage once you hit those digits.</p><blockquote>“While it is not the only lens to look through when designing an optimal team size, it’s my belief the moment that when it becomes a struggle to spend 30 minutes a week with each of the folks on your team, it’s time to consider your team might be too big.” — <a href="https://randsinrepose.com/archives/seven-plus-or-minus-three/"><em>Michael Lopp</em></a><em>.</em></blockquote><h3>Groups of 50 People</h3><p>Dunbar says that 50 is the number of people we call friends, including our five closest and 15 good friends. Having 50 people in a group means weaker connections, as we usually don&#39;t hang out with 50 people regularly.</p><p>You can have over fifty team members on Slack, but you&#39;ll only talk about 40% of them.</p><p>At this size, a company must establish a solid structure and well-defined roles to maintain order, stay in control, and thrive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4WgztpsVLYvKKncZF-4wAQ.png" /><figcaption>Adding new members increases the communication load.</figcaption></figure><h3>Groups of 150 People</h3><p>The number that Dunbar is best known for is 150 (rounded from 148). It’s the maximum number of social connections humans can manage, beyond which groups struggle to operate effectively.</p><p>For example, once Facebook exceeded 150 employees, they ran into large-scale communication, retention, and turnover problems that were only solved by establishing solid structures, goals, and all-inclusive company values.</p><p>Dunbar numbers found that a long time ago, Roman legions were about 150, and army troops in WW2 were similar in size. Neolithic farming communities would, like many tribes, subdivide into separate communities at around 150.</p><h3>Groups of <strong>500 &amp; 1500 People</strong></h3><p><em>“At around 500-strong, these people are acquaintances and tend to remain just that.”</em></p><p><strong>500</strong>: The number of not-so-close acquaintances we can keep. We have contact with these people, but the additional 350 people are not part of your network, and you don’t know much about them.</p><p>1500: The number of people you can recognize, but these are people with whom you don’t have much social contact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lh8vPRlO_WOLZvOpbPt7aA.png" /></figure><p><em>Dunbar’s findings affect our personal lives and how we interact at work and maintain business relationships. It means there are limits to the number of people on one team, the number of people that should belong to a department (~50), or a division (~1500).</em></p><h3>Conclusion</h3><p>Ultimately, ideal team size depends on more than Scrum or any other recommendations. To build a perfect team, we need to consider a few factors:</p><ul><li>Scope of project</li><li>Deadlines</li><li>Experience of developers</li><li>Team capabilities and their stack</li><li>Did this team ever work together?</li><li>What is a general team organization structure?</li><li>Who is the team lead, and their capabilities</li></ul><p>Additionally, it’s essential to consider the manager&#39;s capabilities and whether he can manage a group. Ideally, a software team shouldn’t be larger than ten and lower than three members.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b015df678e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Hooks: The Dangers Probably No One Told You About]]></title>
            <link>https://medium.com/geekculture/react-hooks-the-dangers-probably-no-one-told-you-about-264fb4393e9c?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/264fb4393e9c</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[react-hook]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Fri, 30 Sep 2022 15:15:58 GMT</pubDate>
            <atom:updated>2022-10-13T06:24:28.796Z</atom:updated>
            <content:encoded><![CDATA[<h4>Explore the dangers React introduced with hooks and how to stay ahead and avoid them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8RpghVYVzO0jmgfIdCJ8A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@xodusdigitals?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Oscar Omondi</a> on <a href="https://unsplash.com/s/photos/mentorship?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Since the introduction of hooks in React 16.8, a few years have passed, and most developers have abandoned the old class structure.</p><blockquote>Hooks made it easy to extract the logic and an easy way to reuse it. After the initial release, they took the front-end world by storm.</blockquote><p>In the past few years, I found dozen hooks-related problems in my and by reviewing others’ code. I’ll try to share the dangers I encountered using hooks, so you don’t have to make the same mistakes.</p><p>We often take mainstream innovations for granted, and rarely we’re critical enough about them. I believe new tools should also be measured by how easy it is to introduce new bugs or create bad coding habits.</p><p>Don’t get me wrong — hooks are everything the old-school React lacked, as there was no easy way to extract and share logic between components. Developers had to deal with HOC (High Order Components) or Render Props. Both of these patterns were too difficult for most to use.</p><blockquote>If you don’t know anything about the hooks or need a refresher, here is a good one. <a href="https://medium.com/@dan_abramov/making-sense-of-react-hooks-fdbde8803889">Dan Abramov — Making sense of react hooks</a></blockquote><h3>1. Dependencies</h3><p>Strings, booleans, numbers, and other primitives are straightforward to add as dependencies to useEffect. However, you can&#39;t use arrays and objects as dependencies. Reason — they&#39;re not comparable in a simple way.</p><blockquote><strong>By default, arrays and objects will compare by reference.</strong></blockquote><p>These dependencies may affect the execution of useEffect hooks in these two cases:</p><ul><li>Array or object is the same - JS will compare them using different references</li><li>Array or object have different values - JS will compare them using the same reference.</li></ul><p>In both cases, the hook will lead to bugs, and they won&#39;t perform correctly.</p><p>There are known hacks and tricks to overcome this issue. None of these is the perfect solution, but sometimes we just need to make things work.</p><ul><li><strong>The first option is to use </strong><strong>JSON.stringify()</strong></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/06cecd40b4be4a9efb506603c9747ddf/href">https://medium.com/media/06cecd40b4be4a9efb506603c9747ddf/href</a></iframe><ul><li><strong>Another (ES6) option would be to use </strong><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals"><strong>t</strong></a><strong>emplate literals to turn them into strings. </strong>Similar to JSON.stringify(), except the result won&#39;t be wrapped in an array.</li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bfef4b781abb5b9f5379d54ae7412d1f/href">https://medium.com/media/bfef4b781abb5b9f5379d54ae7412d1f/href</a></iframe><ul><li><strong>The third option, if the array size doesn&#39;t change, would be to use the spread operator:</strong></li></ul><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f4935b2c91d48b1a91635596ddd316f3/href">https://medium.com/media/f4935b2c91d48b1a91635596ddd316f3/href</a></iframe><h3>2. Conditionals</h3><blockquote>Hooks rely on the order of execution, so it isn’t possible to call a hook conditionally.</blockquote><p>Using hooks conditional would change the order, and your Linter would complain. This issue reduces the way we can structure hooks.</p><p>Technically, you can’t work with hooks in conditionals. However, if you know how they work internally, you can make conditional hooks work for you.</p><p>You need to create two or more components for each hook you want to render. In each component, you can add its logic.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cdccdebd8391eba21a4986b749edd07a/href">https://medium.com/media/cdccdebd8391eba21a4986b749edd07a/href</a></iframe><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/913cb75a62b8b0ac88ce90ebc7a9885b/href">https://medium.com/media/913cb75a62b8b0ac88ce90ebc7a9885b/href</a></iframe><p>This way, we can render two different hooks based on the userId variable.</p><h3>3. Issue with useEffect</h3><p>Developers use useEffect to modify state, DOM, or make API calls.</p><blockquote>I can’t even think of how often I’ve been asked, “why is useEffect called twice?” or “Why do I have an infinite loop in useEffect?”.</blockquote><p>So why is useEffect bad in the first place?</p><ul><li>The good thing about useEffect: You can use it almost for everything</li><li>The bad thing about useEffect: You can use it almost for everything</li></ul><h4>Infinite loop issue</h4><blockquote><a href="https://stackoverflow.com/questions/53070970/infinite-loop-in-useeffect">https://stackoverflow.com/questions/53070970/infinite-loop-in-useeffect</a> — This issue was not the only one — added 11 months ago and seen by 175k developers.</blockquote><p>The most straightforward way to accomplish an infinite loop is to trigger the effect when some state changes, and when it does, you run code that triggers this exact state change.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/869b6caeacb4809dac53dd3cdfe08ca3/href">https://medium.com/media/869b6caeacb4809dac53dd3cdfe08ca3/href</a></iframe><p>The fastest solution is to remove the dependency causing this problem.</p><p><strong>You should always use multiple useEffect to keep the single responsibility principle.</strong> The fewer dependencies you have, the fewer bugs you could potentially have.</p><p>Too much code inside of this hook could get you into problems. Take some time to extract and refactor functions inside of useEffect .</p><h3>4. Overusing useCallback &amp; useMemo</h3><p>Fresh React developers often think it’s a safer approach to memoize function than it’s not. When needed, memoization provides a powerful set of tools to prevent unneeded rendering.</p><p>However, everything too good comes with a high price. By using useCallback and useMemo we increase code complexity, which affects the speed of development and can introduce bugs in the long term.</p><blockquote>Performance optimizations are not free. We should think of useMemo and useCallback as fine-tuning for apps.</blockquote><h4>When NOT to optimise</h4><p>As powerful as they are, you shouldn’t use useMemo or useCallback for every function. Before using, consider checking app performance first. It’s often better to start improving your code before adding these hooks.</p><p><strong>Most of the time, developers shouldn’t bother optimizing unnecessary rerenders</strong>. React is fast by nature; I can’t think that I’ve ever experienced performance issues using it. — This isn’t true for React Native and mobile app development.</p><p>These two can’t fix harmful code, but if everything is already in place, it can take your code from good — great.</p><h4>Cases when it’s BETTER to optimise</h4><p>You can use useMemo when working with functions where inputs gradually change. Also, when data is large enough to cause memory issues, or when parameters are large so that the costs of comparison doesn’t outweigh the use of the wrapper.</p><p>useCallback works well in instances where the code would otherwise be recompiled with every call. Memoizing the results can decrease the cost of calling functions over and over again when the inputs change over time.</p><p><strong>Expensive calculations with useMemo</strong></p><p>The benefit of useMemo is that you can get a value like this:</p><pre>const a1 = {b: props.b}</pre><p>And get it lazily:</p><pre>const a2 = useMemo(() =&gt; ({b: props.b}), [props.b])</pre><p>For this case useMemo isn’t useful, but imagine a function that calculates a value which is computationally expensive to calculate. Not a lot of apps do this, but in case they do — useMemo is a perfect solution.</p><p><strong>Usually, If you start noticing rendering issues, it’s a perfect moment to optimise rerendering.</strong></p><p>Happy coding! ✋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=264fb4393e9c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/react-hooks-the-dangers-probably-no-one-told-you-about-264fb4393e9c">React Hooks: The Dangers Probably No One Told You About</a> was originally published in <a href="https://medium.com/geekculture">Geek Culture</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Six Things That Could Shape The Future Of Mobile Apps]]></title>
            <link>https://i-ads.medium.com/six-things-that-could-shape-the-future-of-mobile-apps-23eea190ac23?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/23eea190ac23</guid>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mobile-app-developers]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[cross-platform]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Sun, 27 Feb 2022 15:00:32 GMT</pubDate>
            <atom:updated>2022-03-12T05:13:29.131Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9adKzXGxwaiQNx3pfIZPQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@shofukan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Colin Avery</a> on <a href="https://unsplash.com/@shofukan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The gold rush area of idea-based mobile apps is a long time gone. In 2010 you could create a new app and become a star overnight, and nowadays, creating an app is just the beginning of a journey.</p><p>Creating a new app is like opening a pizza shop in Italy and hoping it will become booming one day. The main reason for that is that the app market is oversaturated. However, people still need to eat pizza, and new restaurants will open no matter what’s the situation on the market.</p><p>Smartphones and technologies we use to build mobile apps made huge improvements in the past decade. Back in those days, developers used Java, Objective-C, or one of the infamous frameworks such as Xamarin or Ionic. Nowadays, we use Swift and SwiftUI, Kotlin, and incredible cross-platform solutions such as React Native and Flutter.</p><p>Today, we use mobile apps to wake us up, help us sleep, meditate, buy food, and pay our bills. Smartphones are deeply integrated into our society that it’s almost impossible to think about our day-to-day life without them. We have come a long way from playing Snake on our Nokia 3310.</p><p>However, the mobile app industry is going through a transformation, just like any other thing in the world now. To understand the possible future outcomes, we should know the industry’s current state.</p><h3>Current State</h3><p>There are currently 3 million Android and 2 million iOS apps available in app stores with over 6 billion smartphone users worldwide. Although the growth of mobile apps in the past ten years was steady, COVID-19 significantly accelerated digital transformation and mobile app usage.</p><p>Android OS maintained its position as a leading operating system for mobile apps. It’s controlling the market with close to 70% share, while iOS holds around 25% of the mobile OS market share.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33YFH6AiDg-Xzux0_X67iw.png" /><figcaption>Statista: Number of mobile app downloads worldwide from 2017 to 2025 (in a million downloads)</figcaption></figure><p>Some categories are getting more favored than others. Games are most downloaded, and there is no sign this will change soon. Photo &amp; video apps had a growth primarily due to popular social media platforms that are “forcing” users to share good quality videos and pictures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xzlzuPVO2tGWgGw0ldvrbQ.png" /><figcaption>Statista: Revenue of mobile apps worldwide 2017–2025, by segment</figcaption></figure><p>The top app categories on <strong>Google Play</strong> are games &amp; entertainment, personalization, lifestyle, education, books &amp; reference. The category with the fewest apps is music &amp; audio.</p><p>Out of the 24 categories in the <strong>App Store,</strong> games make up the largest category, followed by education, lifestyle, business, and entertainment. Weather apps sit at the bottom with around 0.3% of all apps.</p><blockquote>Mobile app revenues will probably exceed $500 billion by 2023.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/622/1*pvj0pmhTY2l9OpSYopWIig.png" /><figcaption>Statista: average apps number per user (per country)</figcaption></figure><p>In terms of average app usage, millennials usually have more than 67 apps installed on their phone. However, the commonly used app number remaining per person is 25. With the increase in age, the number of installed apps decreases.</p><h3>Future Trends</h3><h4>1. Artificial Intelligence</h4><p>Artificial Intelligence plays a crucial role in the development process as this technology brings a personalized app experience that matches user needs. It will stay as an all-development trend in 2022. By 2023, Artificial intelligence revenue will reach<strong> $70.94 billion</strong>.</p><p>Popular AI mobile apps on the market right now are: Youper, DataBot, ELSA Speak, Cortana, Socratic, and Replika.</p><h4><strong>2. Blockchain</strong></h4><p>It’s predicted that global blockchain revenues will grow in the future to <strong>39 billion</strong> by 2025. Blockchain is changing the way apps are developed and deployed. In the beginning, blockchain was recognized for crypto. Nowadays, developers use blockchain as a decentralized database solution<strong>.</strong></p><p>In 2021 we saw a rising trend of crypto exchanges, crypto wallets, and NFT apps. In 2022 we expect to see a rise in dApps. Decentralized applications (dApps) are digital apps that exist on a <a href="https://www.investopedia.com/terms/b/blockchain.asp">blockchain</a> network of computers instead of a single computer. DApps are often built on the <a href="https://www.investopedia.com/terms/e/ethereum.asp">Ethereum</a> platform.</p><p>Popular blockchain/crypto apps on the market: Uniswap, Rarable, OpenSea, Uniswap, and TraceDonate</p><h4><strong>3. AI &amp; VR</strong></h4><p>In 2021, the AR, VR, and mixed reality market reached <strong>$30.7 billion</strong> and will probably catch up with about<strong> $300 billion</strong> by 2024. With the AR/VR launch, it is expected that by the end of 2026, the working of mobile apps and games will change. People are also shifting from PCs to AR/VR, revealing advancements in ticket booking, trading, watching, mini-games, etc.</p><h4><strong>5. Internet of Things</strong></h4><p>IoT and cloud integration eases the data processing and storage, offers streamlined processes, enhances collaboration, improves productivity, reduces hosting cost, accelerates installation and integration, and cuts down the data processing cost and their complex performance. In 2021 IoT market size was around <strong>308.97 billion </strong>USD<strong>.</strong></p><h4><strong>6. Instant Apps</strong></h4><p>Instant Apps are launched a few years ago by Google. They’re allowing users to use an app without downloading it. We expect to see a rise in usage and development this year. They have a size restriction, so they’re usually not a full version of the app. These limitations might change in the coming years.</p><p>If you’re developing apps for the Google Play Store in 2022 or 2023, you need to have an instant version as well.</p><blockquote>In 2021, 72.9 percent of all e-commerce is expected to be generated via m-commerce, up from 58.9 percent in 2017.</blockquote><h3>Conclusion</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FVIJxPwIvOsmL4XTikd%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FVIJxPwIvOsmL4XTikd%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FVIJxPwIvOsmL4XTikd%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="297" frameborder="0" scrolling="no"><a href="https://medium.com/media/b7ab21c479a7160b3307487749844044/href">https://medium.com/media/b7ab21c479a7160b3307487749844044/href</a></iframe><p>The motivation for this post is many irrelevant articles I’ve read in the past few months. People are trying to go viral by spreading fear among developers and writing misleading titles saying mobile apps are dead. They’re not dead, but mobile apps are going through a transformation, just like the world is now.</p><p>We will probably see a rise in no-code and low-code tools in the future, but developers shouldn’t be worried much. However, If you’re looking to make money with your next app, you should think about a pizza restaurant in Italy. There is always a place on a market for good pizza and this opportunity won’t go any time soon.</p><p>👋 Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23eea190ac23" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native: Two Important Lessons I Learned The Hard Way]]></title>
            <link>https://i-ads.medium.com/react-native-two-important-lessons-i-learned-the-hard-way-3a524bbcef48?source=rss-9e88cd96a7eb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a524bbcef48</guid>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Adnan Sahinovic]]></dc:creator>
            <pubDate>Wed, 17 Nov 2021 16:45:43 GMT</pubDate>
            <atom:updated>2026-09-21T04:37:22.079Z</atom:updated>
            <content:encoded><![CDATA[<h4>Notice and prevent things from going in the wrong direction when building a cross-platform app.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*8-ORnL3mTyS-DJHX" /><figcaption>Photo by <a href="https://unsplash.com/@sigmund?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sigmund</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The first months of development are like running the first hundred meters of a marathon. Builds are light, the codebase is small, no production issues or tech debt: life is good. Once we start onboarding new users, our day-to-day routine changes.</p><p>Having a React Native app in production is like sailing in an open sea. There are many important decisions to analyze and make. There is no standard solution for anything, and that’s probably the hardest thing about it. You’ll have to be smart and choose options that suit your needs best. Initial decisions you have to make:</p><ul><li>Expo or RN CLI</li><li>Redux, Apollo, MobX, or Context API</li><li>StyleSheet or StyledComponents</li><li>Typescript or Javascript</li></ul><p>Even though you’re left on your own to decide what’s best for you, React Native still holds the first position when it comes to cross-platform development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nf3Y-IoVKZW2Znb37YHe3g.png" /><figcaption>statists: cross-platform frameworks</figcaption></figure><p>No matter how well you prepare and think you make the right decisions, things will go wrong. Most mobile apps live out of their app store rating, and a single crash in production can be expensive. However, keeping an eye on important factors will lower disaster risks (crashes or performance issues).</p><h3>1. Navigation</h3><p>Two common issues with React Native are either slow transitions between screens or outdated data, and both are associated with navigation. Various things can go wrong with react-navigation, but one of the most important is how we pass data between screens.</p><p><strong>Red Flag</strong>: Passing a lot of data when navigating makes screens dependent on that data.</p><p>Each component should be treated as an isolated view, and we should think about how to navigate to that view with as little as possible information.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dbf9284fe621a2c6d01e78be78facf30/href">https://medium.com/media/dbf9284fe621a2c6d01e78be78facf30/href</a></iframe><p>You can also think of the route object like a URL. If the Profile screen had a URL, what should be in there? It’s important to understand that not all data should be in params. Params are like an option for a screen, and they should only contain information to configure what is being displayed.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d34c0a9ee9f22e763f39a1318d9274f2/href">https://medium.com/media/d34c0a9ee9f22e763f39a1318d9274f2/href</a></iframe><p>Data such as user objects should be in your global store instead of the navigation state. Otherwise, you have the same data duplicated in multiple places. This can lead to bugs, such as the profile screen showing outdated data.</p><p><strong>Red Flag: Nesting navigators</strong></p><p>It’s recommended to reduce nesting navigators to a minimum. Always try to achieve the behavior you want with as little nesting as possible. Nesting has many downsides:</p><ul><li>Nesting the same type of navigators (drawer inside drawer, tabs inside tabs) might lead to confusing UX.</li><li>A deeply nested view hierarchy can cause memory and performance issues with lower-end devices.</li><li>With nesting, code can become difficult to follow when navigating to nested screens, and configuring deep links can become a nightmare.</li></ul><blockquote>Keep your navigators flat and pass as little as possible information when navigating between screens.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FSACoDGYTvVNhZYNb5a%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FSACoDGYTvVNhZYNb5a%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExcm9hZms1NjlocDlqM3NwaXR2OHh6NnB4czFmMG5yZmIxamwxODlnbSZlcD12MV9naWZzX2dpZklkJmN0PWc%2FSACoDGYTvVNhZYNb5a%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/01bc38bb93a4df89fee64a5e8be20fcc/href">https://medium.com/media/01bc38bb93a4df89fee64a5e8be20fcc/href</a></iframe><h3>2. Animations</h3><p>Animations are necessary to create a great user experience. To work with them, you should first understand React Native architecture. It consists of threads and processes, and it’s essential to understand the difference between them.</p><h4>What is a thread?</h4><p>It’s a thread of execution. You can think of it as a set of instructions to be executed by the CPU.</p><h4>What is a process?</h4><p>A process is a running program — for example, the browser (Chrome, Safari). You can see all of the processes running on your computer by opening a task manager.</p><h4>What is single-threaded?</h4><p>Single-threaded means that a process only has one thread of execution. This means only one set of instructions executes at once.</p><h4>What is multi-threaded?</h4><p>Multi-threaded means that a process has two or more threads, and it can execute multiple instructions simultaneously.</p><h4>React Native is single-threaded</h4><p>That means for each process; there is only one single thread. Because of this, if you have a process that has many purposes, you can have performance problems. Imagine having a process responsible for live streaming and showing a list of comments below the video. The live stream could block the comments and vice-versa because of React Native’s single-threaded nature.</p><h4>React Native is multi-processed.</h4><p>Instead of multi-threading, RN is multi-processed. Three primary processes are running in React Native. Each process has one thread attached to it, and this is where all confusion comes from.</p><ul><li><strong>UI Thread — </strong>It’s responsible for rendering IOS and Android views.</li><li><strong>JS Thread — </strong>Responsible for handling all of the logic of your react native application.</li><li><strong>React Native Modules Thread — </strong>This happens when an app needs to access native components. For example, if you’re working with animations, you may use the native driver to handle your animations.</li></ul><blockquote>If you want to create additional processes, you can achieve that by using the npm module <a href="https://github.com/joltup/react-native-threads">react-native-threads</a>.</blockquote><p><strong>Red Flag</strong>: Animations running on JS thread</p><p>Most of the stuff going on occurs on the JS thread. While it works well most of the time, it might get jammed by things going on in your app, resulting in it being slow and unresponsive. That’s where useNativeDriver might come to help. It tells the app to run animation on the UI instead of the JS thread.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1eb0941870354e9288a87b2ea4aa4de1/href">https://medium.com/media/1eb0941870354e9288a87b2ea4aa4de1/href</a></iframe><p>In other words, this runs animations in the world of Native, which offers higher performance, and you don’t have to worry about the Javascript thread being blocked by something else.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d5482b6c867586a5bd538b2bff05dfce/href">https://medium.com/media/d5482b6c867586a5bd538b2bff05dfce/href</a></iframe><p>Alternatively, you can use <a href="https://reactnative.dev/docs/interactionmanager">Interaction Manager</a>, which allows long-running tasks to be scheduled after animations have been completed. This allows JS animations to run smoothly.</p><h3>Bonus: CI/CD</h3><p>Remember the marathon? Manually building and shipping your app is like running it barefoot. Fine for the first hundred meters, painful by kilometer five.</p><p><strong>Red Flag: </strong>Releases that depend on your machine</p><p>Cross-platform means every release is really two releases: an iOS build and an Android build, each with its own signing, provisioning, and store upload. When those builds happen on your laptop, they depend on your Xcode version, your certificates, and node_modules folder. All of it works, until the day one of those things silently changes, and your release breaks exactly when you can least afford it. “It works on my machine” is not a release strategy.</p><p>The fix follows the same principle as everything above: remove the fragile dependency. Move builds off your machine and onto a pipeline.</p><p>I use Bitrise for this, and it fits React Native well because it’s built for mobile and nothing else:</p><ul><li>Setup is quick. The project scanner detects your React Native app and generates a working build–test–deploy workflow on the first run, so you’re not writing pipeline config from scratch.</li><li>iOS code signing stops being a 2 AM problem. Certificates and provisioning profiles are automated, and macOS build machines come out of the box.</li><li>One pipeline, both platforms. A single build produces your iOS and Android binaries, runs your unit and Detox E2E tests, and collects everything in Test Reports.</li><li>Builds are reproducible. Every build runs on a clean stack, independent of anyone’s local setup, with pre-built Steps for Slack, App Store and Play Store deployment, Fastlane, and more.</li></ul><p>Notice the pattern? Slow transitions, janky animations, broken releases.. the same lesson every time. Things will go wrong, and your job is to lower the risk before they do. Navigation and animations protect your users’ experience; CI/CD protects your release day. Automate the boring, breakable parts, and spend your time on the code that matters.</p><p>👋 Happy coding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a524bbcef48" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>