<?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 Sushil Patil on Medium]]></title>
        <description><![CDATA[Stories by Sushil Patil on Medium]]></description>
        <link>https://medium.com/@sushil.patil01?source=rss-2efd95e7ff73------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*PYt8tcPkMMBOZzLrSXB11w.jpeg</url>
            <title>Stories by Sushil Patil on Medium</title>
            <link>https://medium.com/@sushil.patil01?source=rss-2efd95e7ff73------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:50:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sushil.patil01/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[How to Bypass App Store Reviews in React Native: OTA Updates vs. Server-Driven UI]]></title>
            <link>https://medium.com/@sushil.patil01/how-to-bypass-app-store-reviews-in-react-native-ota-updates-vs-server-driven-ui-712cafecc486?source=rss-2efd95e7ff73------2</link>
            <guid isPermaLink="false">https://medium.com/p/712cafecc486</guid>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Sushil Patil]]></dc:creator>
            <pubDate>Fri, 29 May 2026 15:14:43 GMT</pubDate>
            <atom:updated>2026-05-29T15:14:43.877Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Learn the differences, pros, and cons of Over-The-Air (OTA) updates and Server-Driven UI (SDUI) using a simple restaurant analogy that junior developers will actually remember.</em></p><p>If you have ever shipped a mobile app, you know the sinking feeling. You finally push your release to the App Store and Google Play, breathe a sigh of relief, and go to lunch. Halfway through your sandwich, a Slack notification pops up: there is a critical typo on the checkout screen, or worse, a bug crashing the app for new users.</p><p>In native mobile app development (Swift/Kotlin), you would have to fix the bug, submit a new build, and wait anywhere from 24 to 48 hours for Apple or Google to approve your changes.</p><p>But if you are using <strong>React Native</strong>, you have a superpower.</p><p>Because React Native runs on JavaScript, you can update your app’s logic and UI on the fly without going through the app stores. The two most popular architectures to achieve this are <strong>Over-The-Air (OTA) Updates</strong> and <strong>Server-Driven UI (SDUI)</strong>.</p><p>Both bypass the dreaded App Store waiting room, but they do it in entirely different ways. Let’s break them down using a story that will make the concepts stick.</p><h3>🍔 The Restaurant Analogy for Mobile App Updates</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oUQgk4iRHWpEStF5w3pxsQ.png" /><figcaption>Imagine your React Native app is a popular, bustling restaurant.</figcaption></figure><h3>OTA Updates: The Overnight Menu Swap</h3><p>Using an OTA update (via tools like <strong>Expo Updates</strong> or <strong>Microsoft CodePush</strong>) is like printing a brand-new stack of paper menus and secretly slipping them under the restaurant’s front door at 2:00 AM.</p><p>When the restaurant opens the next morning, customers walk in, sit down, and are handed the new menu.</p><ul><li><strong>The Magic:</strong> It’s a fantastic way to quickly fix a typo on the menu or swap out a dessert without needing permission from the City Council (the App Store review team).</li><li><strong>The Catch:</strong> Let’s say your new menu includes deep-fried pickles. The customers order it, but your kitchen doesn’t actually own a deep fryer. Chaos ensues, the kitchen catches fire, and the restaurant shuts down.</li></ul><p>In React Native terms, the “deep fryer” is a <strong>Native Module</strong>. OTA updates can only change your JavaScript code. If your new JS bundle relies on a native iOS or Android dependency (like adding a new camera library or Bluetooth package) that wasn’t compiled into the original App Store download, your app will crash instantly.</p><h3>Server-Driven UI: The Digital Menu Boards</h3><p>Now, let’s look at Server-Driven UI (SDUI). This approach is like tearing out the paper menus entirely and installing slick digital screens across your restaurant, all wired to a central computer in the manager’s office.</p><ul><li><strong>The Magic:</strong> If you want to run a flash sale, rearrange the layout, or change the color of the “Order Now” button, the manager just updates the system. The backend API sends a new JSON layout, and <em>boom</em> — the digital boards update instantly for everyone in the restaurant, right before their eyes.</li><li><strong>The Catch:</strong> Setting up those digital screens, wiring them perfectly, and teaching the kitchen how to read them takes a massive amount of upfront time, money, and complex software engineering.</li></ul><h3>🥊 The Technical Breakdown: Pros and Cons</h3><p>Let’s step out of the restaurant and look at how these two React Native architectures actually work in your codebase.</p><h3>📦 Over-The-Air (OTA) Updates (CodePush / Expo)</h3><p><strong>How it works:</strong> Your React Native app is essentially a native shell that runs a bundled JavaScript file. With OTA updates, you host a new version of that JS bundle on a cloud server. When the user opens the app, it checks the server, downloads the new bundle in the background, and runs it the next time the app loads.</p><p><strong>Pros:</strong></p><ul><li><strong>Total JavaScript Freedom:</strong> You aren’t just changing the UI; you can rewrite entire complex logic flows, Redux states, or API calls.</li><li><strong>Zero Backend Required:</strong> You don’t need to build a custom backend. You just plug into the Expo or CodePush ecosystem, and their infrastructure handles the hosting and delivery.</li><li><strong>The Ultimate Hotfix:</strong> It is the absolute fastest way to patch a critical bug in production.</li></ul><p><strong>Cons:</strong></p><ul><li><strong>Sync Delays:</strong> Because the app has to download the bundle in the background, users usually have to close and restart the app to actually see the new changes.</li><li><strong>The Native Dependency Danger:</strong> As mentioned in our story, if you add a library that requires running pod install or tweaking build.gradle, you <strong>cannot</strong> update via OTA. You must go through the App Store.</li><li><strong>Bundle Size:</strong> You are downloading a heavy JS bundle. On slow cellular networks, this can take time and eat up user data.</li></ul><h3>🏗️ Server-Driven UI (SDUI)</h3><p><strong>How it works:</strong> Your frontend becomes a “dumb” renderer. Instead of hardcoding a screen layout in React Native, your app makes an API call to your backend. The backend replies with a JSON payload dictating exactly what to draw (e.g., &quot;components&quot;: [{&quot;type&quot;: &quot;Header&quot;, &quot;title&quot;: &quot;Welcome&quot;}, {&quot;type&quot;: &quot;Button&quot;, &quot;action&quot;: &quot;checkout&quot;}]). Your app parses the JSON and renders the corresponding native components.</p><p><strong>Pros:</strong></p><ul><li><strong>Instantaneous Updates:</strong> Changes happen in real-time. The moment a user navigates to a screen, the API fetches the latest layout. No background downloading or app restarts required.</li><li><strong>A/B Testing Heaven:</strong> Product and Marketing teams can tweak layouts, run experiments, and launch campaigns directly from a CMS without ever bothering a mobile developer.</li><li><strong>Cross-Platform Parity:</strong> You can feed the exact same JSON schema to your React Native app, your web app, and your native apps, ensuring everyone sees the exact same layout simultaneously.</li></ul><p><strong>Cons:</strong></p><ul><li><strong>Massive Upfront Complexity:</strong> Building the JSON schema, the frontend rendering engine to parse it, and the backend infrastructure to serve it is a huge architectural lift.</li><li><strong>State Management Nightmares:</strong> Handling complex local state — like a multi-step form with conditional validation, or intricate 60fps animations — via remote JSON is notoriously difficult.</li><li><strong>Offline Limitations:</strong> If the user opens the app on the subway without internet, they might see a blank screen or a heavily degraded, cached version of the UI.</li></ul><blockquote>💡 The Verdict: Which Architecture Should You Choose?</blockquote><p>Choosing between OTA and Server-Driven UI isn’t about which technology is “better” — it’s about what business problem your engineering team is trying to solve.</p><p><strong>Choose OTA Updates if:</strong></p><ul><li>You are a small-to-medium team focused on moving fast.</li><li>Your primary goal is fixing bugs quickly and bypassing the 48-hour App Store review queue.</li><li>Your app’s core layout and user journey are relatively stable.</li></ul><p><strong>Choose Server-Driven UI if:</strong></p><ul><li>You are building a dynamic, content-heavy app where layouts change daily based on user behavior or promotions (think e-commerce, Swiggy, Netflix, or Airbnb).</li><li>You have a dedicated backend team to support the infrastructure.</li><li>Your product managers need the power to change the UI without developer intervention.</li></ul><p>Both tools are incredibly powerful additions to a React Native developer’s toolkit. Just remember: whether you are sliding a menu under the door or wiring up digital screens, make sure your kitchen actually has a deep fryer before you put fried pickles on the menu.</p><p><strong>Let’s Connect!</strong></p><p>I love talking about React Native, mobile development, and software architecture. If you found this article helpful, I’d love to hear your thoughts or learn which approach your team uses.</p><p>🔗 <strong>Connect with me on LinkedIn:</strong> <a href="https://www.linkedin.com/in/sushil-k-patil/">Sushil K Patil</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=712cafecc486" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[6 Essential Skills to Become a Senior React Native Engineer]]></title>
            <link>https://medium.com/@sushil.patil01/the-react-native-glass-ceiling-how-im-breaking-through-to-senior-engineer-a116477c8973?source=rss-2efd95e7ff73------2</link>
            <guid isPermaLink="false">https://medium.com/p/a116477c8973</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[Sushil Patil]]></dc:creator>
            <pubDate>Thu, 28 May 2026 13:55:28 GMT</pubDate>
            <atom:updated>2026-05-28T14:40:50.071Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mK4F0aAvmXoSy52itqPNUQ.png" /><figcaption>Less hype. More engineering. Bigger impact.</figcaption></figure><p>For a long time, I thought leveling up in React Native meant learning the absolute newest React 19 feature, adopting the trendiest state manager, or memorizing every hook in the latest Expo router API.</p><p>But recently, I hit a wall. When I needed to debug a memory leak, handle complex offline syncing, or read a cryptic Xcode crash log?</p><p><em>Crickets.</em> 🦗</p><p>I came to an uncomfortable realization: my growth wasn’t being limited by my knowledge of the framework. It was limited by my lack of fundamental software engineering and mobile-specific skills <em>outside</em> of it.</p><p>If I wanted to break through from a mid-level RN developer to a high-impact Mobile Engineer, I needed to stop obsessing over React and start focusing on the bigger picture.</p><p>Here is the blueprint I am actively following to level up my career this year. 🗺️</p><h3>1. Architecture Over “Spaghetti Components” 🍝</h3><p>In the web world, I used to slap an API call inside a useEffect, render the result, and call it a day. But on mobile, I realized this creates a fragile, unscalable nightmare.</p><p>A mobile app is a long-living client. State persists. Memory is constrained. Network conditions change while you walk down the street. I am learning to decouple my business logic from my UI.</p><p><strong>My Old Approach:</strong></p><p>Everything lived together. The UI, the network request, and the data parsing were all mashed into one giant 500-line screen file.</p><pre>❌ The &quot;React-First&quot; Structure<br>/src<br>  /components<br>  /screens<br>    CheckoutScreen.tsx <br>    // ^ Contained UI, fetch calls, async storage, and complex math</pre><p><strong>The Engineering-First Shift:</strong></p><p>I’m adopting Clean Architecture, Domain-Driven Design, and feature-based routing. I’m forcing my React components to be “dumb” — they only know how to render data and dispatch intents. The heavy lifting now happens in isolated, testable layers.</p><pre>✅ The &quot;Engineering-First&quot; Structure<br>/src<br>  /core<br>    /api        // API clients, interceptors, tokens<br>    /domain     // TypeScript interfaces, business rules<br>    /store      // Global state (Zustand/Redux)<br>  /features<br>    /checkout<br>      /ui       // Dumb presentational components<br>      /hooks    // useCheckout.ts (The View-Model / Logic)<br>      /services // Checkout-specific API interactions<br>  /shared       // Reusable UI components (Buttons, Inputs)</pre><p>Now, if I need to swap a REST API for a GraphQL endpoint, I don’t have to touch 40 different .tsx files. I only touch the services layer.</p><h3>2. The Native Ecosystem: Facing Xcode and Android Studio 🛠️</h3><p>React Native is an incredible bridge, but it’s still just a bridge. I realized that eventually, I have to cross it.</p><p>I used to treat iOS and Android as mysterious black boxes. If an error didn’t have a stack trace pointing to a .tsx file, I&#39;d panic, delete node_modules, clear the pod cache, and pray to the tech gods. 🙏</p><p><strong>The Shift:</strong></p><p>I am stopping treating Native as the enemy. I don’t need to build a native app from scratch, but I am learning how to survive in their IDEs and write simple bridges when open-source libraries fail me.</p><p>Writing a basic Swift module to access a native iOS API isn’t the black magic I thought it was:</p><pre>// A simple native module in Swift. <br>// I used to run from this. Now, I&#39;m learning to write it.<br>@objc(DeviceUtils)<br>class DeviceUtils: NSObject {<br>  <br>  @objc(getDeviceName:rejecter:)<br>  func getDeviceName(_ resolve: RCTPromiseResolveBlock, reject: RCTPromiseRejectBlock) {<br>    let deviceName = UIDevice.current.name<br>    resolve(deviceName)<br>  }<br>}</pre><p>I’m taking the time to learn how Info.plist and AndroidManifest.xml work. I&#39;m opening Xcode Instruments to track down memory leaks, and reading Android Studio&#39;s Logcat to figure out <em>why</em> a third-party SDK is throwing a NullPointerException.</p><h3>3. Backend Literacy: Understanding the API Contract 🤝</h3><p>I used to accept whatever JSON payload the backend threw at me, write 50 lines of parsing logic on the client, and complain that the app was slow. Or worse, I assumed APIs would always return a 200 OK in under 50ms.</p><p>But what happens when a user taps “Submit Payment” while their train goes into a tunnel, the connection drops, and they tap it again?</p><p><strong>The Shift:</strong></p><p>I am learning to speak the backend’s language. A massive milestone for me was implementing <strong>Idempotency Keys</strong> so the app can safely retry requests without double-charging the user. 🚇💸</p><pre>// ✅ Safe retry with Idempotency Key<br>const processPayment = async (cart, userId) =&gt; {<br>  // Generate a unique ID for this specific transaction attempt<br>  const idempotencyKey = crypto.randomUUID(); <br>  <br>  return await fetch(&#39;https://api.example.com/charge&#39;, {<br>    method: &#39;POST&#39;,<br>    headers: {<br>      &#39;Content-Type&#39;: &#39;application/json&#39;,<br>      // The backend tracks this key. If sent twice, it doesn&#39;t double-charge.<br>      &#39;Idempotency-Key&#39;: idempotencyKey, <br>    },<br>    body: JSON.stringify({ cart, userId }),<br>  });<br>};</pre><h3>4. Scientific Debugging (Putting down the console.log) 🔬</h3><p>I had to admit to myself: console.log(&quot;here 1&quot;) is not a debugging methodology.</p><p>When a bug report says “the app feels janky on my older Android phone,” I used to just guess at the problem and refactor random components.</p><p><strong>The Shift:</strong></p><p>I am moving from <em>guessing</em> to <em>measuring</em>. I’m practicing forming a hypothesis, using profiling tools to measure frame drops (UI/JS thread FPS), isolating the variable, and proving the fix.</p><p>I’m starting to use Performance.mark() to benchmark heavy functions, and I&#39;m forcing myself to open Flipper or the React Native DevTools to track down exactly which component triggered an unnecessary re-render of a FlatList.</p><h3>5. Testing Maturity: Confidence over Coverage 🧪</h3><p>Writing tests for React Native is notoriously annoying. So, for a long time, I just didn’t do it. Or I wrote a few snapshot tests that broke every time someone changed a CSS margin.</p><p><strong>The Shift:</strong></p><p>I am shifting my mindset to write tests that buy me <em>confidence</em>. I don’t test if a button is blue anymore. Because my logic is now decoupled (see point #1), I can unit test the core business rules. And for critical flows, I’m learning to write End-to-End (E2E) tests using modern tools like <strong>Maestro</strong>.</p><pre># A Maestro E2E test. <br># Runs on a real device/emulator to guarantee the app works.<br>appId: com.example.app<br>---<br>- launchApp<br>- tapOn: &quot;Shopping Cart&quot;<br>- tapOn: &quot;Checkout&quot;<br>- inputText: &quot;1234 5678 9101 1121&quot;<br>- tapOn: &quot;Pay Now&quot;<br>- assertVisible: &quot;Payment Successful 🎉&quot;</pre><h3>6. Communication: The Ultimate Seniority Signal 🗣️</h3><p>Finally, the most underrated skill I’m working on: pushing back.</p><p>When Product Managers brought me designs that looked beautiful on a web browser but would absolutely destroy battery life and frame rates on a mid-range mobile device, I used to just say: <em>“Okay, I’ll try to build it.”</em> (And then struggle to make it performant).</p><p><strong>The Shift:</strong></p><p>I am practicing having better architectural conversations. Instead of just saying yes, I’m learning to say: <em>“This heavy animation block will require constant bridge traffic and cause layout thrashing. If we swap it for a native Reanimated transition, we get 90% of the visual impact with zero performance hit. Let’s do that.”</em> 💡</p><p>My job isn’t to just translate Figma to Code anymore. My job is to deliver a world-class mobile experience.</p><h3>The Takeaway</h3><p>React Native is just a tool. It’s a fantastically productive, powerful tool, but it is not my entire profession.</p><p>If you’re feeling stuck at the mid-level like I was, join me in putting down the React documentation for a bit. Let’s open Xcode. Let’s read about API Idempotency. Let’s write a Maestro E2E test and restructure our folders.</p><p>The framework is just the starting line. I’m realizing the real engineering happens outside of it. 🚀</p><p><strong>💬 What do you think?</strong> What is the hardest “non-React” skill you are learning right now to level up your mobile development game? Let’s grow together in the comments below!</p><p><em>(If you found this helpful or relatable, hit the 👏 button so other engineers can find it! Also, </em><strong><em>let’s connect — follow me on LinkedIn</em></strong><em> [</em><a href="https://www.linkedin.com/in/sushil-k-patil/">https://www.linkedin.com/in/sushil-k-patil/</a><em>] as I continue to document my journey into deeper mobile engineering!)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a116477c8973" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>