<?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 Sai Yan Naing on Medium]]></title>
        <description><![CDATA[Stories by Sai Yan Naing on Medium]]></description>
        <link>https://medium.com/@saiyannaing.dev?source=rss-a978ffe6953c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LSBGy_ntuvyDqW_nNZOdXA.jpeg</url>
            <title>Stories by Sai Yan Naing on Medium</title>
            <link>https://medium.com/@saiyannaing.dev?source=rss-a978ffe6953c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:45:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@saiyannaing.dev/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[OTA Published, But Device Not Updating?]]></title>
            <link>https://medium.com/@saiyannaing.dev/ota-published-but-device-not-updating-9b68cc42890b?source=rss-a978ffe6953c------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b68cc42890b</guid>
            <dc:creator><![CDATA[Sai Yan Naing]]></dc:creator>
            <pubDate>Mon, 11 May 2026 02:42:52 GMT</pubDate>
            <atom:updated>2026-05-11T02:42:52.497Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I debugged an OTA issue in an Expo React Native app where updates were publishing successfully, but devices still showed noUpdateAvailable.</p><p>What happened</p><ul><li>Store build and OTA publish were coming from different source states.</li><li>OTA pipeline looked healthy, but devices were not receiving updates.</li></ul><p>Root cause</p><ul><li>App uses fingerprint-based runtime policy.</li><li>OTA updates only apply when runtime compatibility matches exactly.</li><li>The published update was compatible with a different binary line than what users had installed.</li></ul><p>How I confirmed</p><ul><li>Compared runtime info shown in-app with OTA dashboard runtime.</li><li>Probed manifest endpoint using app request headers.</li><li>Server correctly returned noUpdateAvailable for that installed binary line.</li></ul><p>Fix</p><ul><li>Publish OTA from the exact same source snapshot as the installed binary line.</li><li>Keep release channel mapping consistent (no channel name drift).</li><li>Validate compatibility before publish, not after.</li></ul><p>Takeaway<br>In OTA workflows, compatibility state matters more than whether “publish succeeded.”</p><p>#ReactNative #Expo #OTA #MobileEngineering #SoftwareEngineering #DevOps</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b68cc42890b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Performance Matter]]></title>
            <link>https://medium.com/@saiyannaing.dev/performance-matter-18027bdc504e?source=rss-a978ffe6953c------2</link>
            <guid isPermaLink="false">https://medium.com/p/18027bdc504e</guid>
            <category><![CDATA[web-performance]]></category>
            <category><![CDATA[clean-architecture]]></category>
            <dc:creator><![CDATA[Sai Yan Naing]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 05:02:32 GMT</pubDate>
            <atom:updated>2026-03-30T05:02:32.060Z</atom:updated>
            <content:encoded><![CDATA[<p>Most developers focus on making things work.</p><p>Great developers focus on making things scale.</p><p>Two things I’ve learned while building real-world apps</p><p>⚡ Performance matters</p><p>=========================</p><p>Users don’t care how clean your code is if your app is slow.</p><p>Slow screens = user frustration</p><p>Unnecessary re-renders = wasted resources</p><p>Heavy components = bad UX</p><p>Even a small delay can break user trust.</p><p>🏗️ Clean architecture matters</p><p>==========================</p><p>Without structure, your app becomes harder to maintain every day.</p><p>Hard to debug</p><p>Hard to scale</p><p>Hard for teams to collaborate</p><p>Clean architecture helps you:</p><p>✔ Separate concerns</p><p>✔ Write reusable code</p><p>✔ Scale features without breaking existing ones</p><p>💡 Real lesson:</p><p>Performance keeps users.</p><p>Clean architecture keeps developers sane.</p><p>Balance both — that’s how you build production-level apps.</p><p>#ReactNative #Frontend #SoftwareEngineering #CleanCode #Performance #MobileDevelopment</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18027bdc504e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Communication Gap Between Frontend and Backend Developers]]></title>
            <link>https://medium.com/@saiyannaing.dev/communication-gap-between-frontend-and-backend-developers-ac6b3951af96?source=rss-a978ffe6953c------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac6b3951af96</guid>
            <category><![CDATA[misunderstanding]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[query]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Sai Yan Naing]]></dc:creator>
            <pubDate>Mon, 23 Mar 2026 07:25:41 GMT</pubDate>
            <atom:updated>2026-03-23T07:28:22.795Z</atom:updated>
            <content:encoded><![CDATA[<p>Had a small but impactful issue in production recently 😅</p><p>We were getting unexpected <strong>“Unauthenticated” errors</strong>, even though everything looked fine on the frontend.</p><p>After digging deeper, the root cause wasn’t a bug in logic — it was a <strong>wrong GraphQL query + a communication gap with backend</strong>.</p><p>The query I used didn’t match the expected auth flow from the backend, which caused the request to fail silently until production 🚨</p><p>💡 Lesson learned:<br>Clear communication between frontend &amp; backend is just as important as writing correct code.</p><p>Now I double-check:</p><ul><li>API contracts</li><li>Auth requirements</li><li>Query structure before shipping</li></ul><p>Small mismatch, big impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TmFU07u9Rd0im1t6DBfKpQ.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac6b3951af96" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>