<?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 Arul mani on Medium]]></title>
        <description><![CDATA[Stories by Arul mani on Medium]]></description>
        <link>https://medium.com/@codingwitharul?source=rss-6a5e42cee40f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WAWacks2vBwwnY7zP0V3YQ.jpeg</url>
            <title>Stories by Arul mani on Medium</title>
            <link>https://medium.com/@codingwitharul?source=rss-6a5e42cee40f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 21:52:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@codingwitharul/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 Connect ESP32 to Wi-Fi on Android (The Right Way) | EasyEsp]]></title>
            <link>https://proandroiddev.com/how-to-connect-esp32-to-wi-fi-on-android-the-right-way-easyesp-b110317a5a41?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b110317a5a41</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[kotlin-multiplatform]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Thu, 05 Nov 2026 17:59:37 GMT</pubDate>
            <atom:updated>2026-11-06T15:14:24.022Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_fS0Qmh6V8oG19Hu" /><figcaption>Photo by <a href="https://unsplash.com/@vishnumaiea?utm_source=medium&amp;utm_medium=referral">Vishnu Mohanan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Stop frustrating your IoT users. Build a seamless ESP32 Wi-Fi provisioning flow using Jetpack Compose, Ktor, and MVI Architecture.</p><p>The Painless Way to Connect ESP32 Devices to Wi-Fi on Android 📱⚡</p><p><strong>How to build seamless IoT provisioning flows using Jetpack Compose, Ktor, and MVI Architecture.</strong></p><p>If you’ve ever built an IoT product, you know the biggest hurdle isn’t writing the firmware or building the cloud backend — it’s the <strong>onboarding process</strong>. Getting a screenless microcontroller (like an ESP32) connected to a user’s home Wi-Fi network is notoriously frustrating.</p><p>Users have to leave your app, go to their phone’s Wi-Fi settings, connect to a temporary hotspot, ignore the “Internet may not be available” warnings, go back to the app, enter their credentials, and pray it works.</p><p>As Android developers, we can do better.</p><p>Today, I am open-sourcing <a href="https://github.com/codingwitharul/esay-esp"><strong>EasyESP Connect</strong></a> — a battle-tested Kotlin Multiplatform (KMM) Library, Android App, and companion ESP32 firmware that makes provisioning ESP32 devices incredibly simple, resilient, and fully automated.</p><p>The Android IoT Routing Problem 🚧</p><p>Before diving into the solution, let’s talk about why Android makes IoT provisioning so hard.</p><p>When your phone connects to an ESP32’s temporary Wi-Fi hotspot, that hotspot doesn’t have internet access. Modern Android versions (Android 9+) are smart — if they detect a Wi-Fi network has no internet, they will silently route all HTTP requests through the user’s Cellular Data instead.</p><p>This means when your app tries to send the Wi-Fi password to <a href="http://192.168.4.1,/">http://192.168.4.1,</a> the request goes to the cellular tower, times out, and the setup fails.</p><p>The Solution: EasyESP Connect ✨</p><p>EasyESP Connect solves this (and many other edge cases) by taking full control of the Android Networking stack and providing a beautiful, state-driven Jetpack Compose UI.</p><p><strong>Key Features:</strong> * <strong>Automated Device Discovery:</strong> Passively scans for local ESP32 devices broadcasting setup SSIDs using Android’s WifiManager. * <strong>Programmatic Hotspot Binding:</strong> Uses WifiNetworkSpecifier (Android 10+) to securely connect the phone to the ESP32 <em>without leaving the app</em>, and explicitly binds the app’s process to the Wi-Fi network so HTTP requests don’t leak to cellular data. * <strong>Smart Fallbacks:</strong> If the OS blocks the automatic connection, it gracefully degrades to a guided manual connection screen. * <strong>ESP32 Dual Mode:</strong> The firmware runs in WIFI_AP_STA mode, acting as a configuration portal while simultaneously scanning the environment for home routers.</p><p>How to use it in your app 🛠️</p><p>I built EasyESP Connect to be as flexible as possible. Whether you want a plug-and-play UI or you want to build your own custom screens, integration takes minutes.</p><p><em>Method 1: The Drop-In Compose UI</em></p><p>If you are building a modern Jetpack Compose app, you can drop the pre-built EasyEspSetupUI directly into your screen. It handles permissions, Wi-Fi scanning, Lottie animations, and error states automatically.</p><pre>import com.easyesp.shared.ui.EasyEspSetupUI<br> import com.easyesp.shared.mvi.EasyEspConfig<br> <br> @Composable<br> fun ProvisioningScreen() {<br>     EasyEspSetupUI(config = EasyEspConfig(scanTimeoutMillis = 60_000L),<br>                 onSuccess = { <br>                    println(&quot;ESP Device Provisioned Successfully! 🎉&quot;) <br>                 },<br>     onError = { error -&gt; println(&quot;Setup Failed: $error&quot;) })<br> }</pre><p><em>Method 2: The Activity Result API</em></p><p>If your app is built with XML Views or Fragments, you can launch the Compose flow using a standard ActivityResultContract and just wait for the callback:</p><pre>val launcher = registerForActivityResult(EasyEspSetupContract()) { result -&gt;<br>   result.onSuccess { <br>   // Device is connected!<br>   }.onFailure { error -&gt;<br>   // Handle failure<br>   }<br> }<br> <br> // Start Setup Flow<br> launcher.launch(EasyEspConfig())</pre><p><em>Method 3: Headless MVI (Build Your Own UI)</em></p><p>For developers who want complete control over the pixel-perfect design of their app, EasyESP provides a headless <strong>MVI (Model-View-Intent) Session</strong>.</p><p>You simply send EasyEspIntents to the session and observe the EasyEspState. The library handles all the ugly networking, timeouts, and state transitions in the background.</p><pre>val session = EasyEsp.createSession(context, coroutineScope, EasyEspConfig())<br> <br> // 1. Observe State<br> lifecycleScope.launch {<br>   session.state.collect { state -&gt; <br>       when(state) {<br>       is EasyEspState.Discovering -&gt; showCustomRadarAnimation()<br>       is EasyEspState.EspDevicesFound -&gt; displayDeviceList(state.devices)<br>       is EasyEspState.Provisioning -&gt; showLoadingSpinner()<br>       is EasyEspState.Success -&gt; navigateToDashboard()<br>       // …<br>       }<br>   }<br> }<br> <br> // 2. Send Intents to control the flow<br> session.sendIntent(EasyEspIntent.CheckPreconditionsAndStart)</pre><p>The Firmware Side 🔌</p><h3>3. Flash the Firmware (Arduino Library)</h3><p>To make your ESP32 compatible, you can use the official EasyEspAndroid Arduino Library.</p><h4>Search LibraryManager “EasyEspAndroid” and install Simply</h4><h4>or</h4><ol><li>Download this repository as a ZIP file.</li><li>In Arduino IDE, go to Sketch -&gt; Include Library -&gt; Add .ZIP Library… and select the ZIP.</li><li>Open Arduino IDE and go to File -&gt; Examples -&gt; EasyEspAndroid -&gt; BasicSetup.</li><li>Select your ESP32 board and upload at 115200 baud.</li></ol><p>Here is how simple your ESP32 code becomes:</p><pre>#include &lt;EasyEspAndroid.h&gt;<br><br>EasyEspAndroid easyEsp;<br><br>void setup() {<br>  Serial.begin(115200);<br>  easyEsp.onConnected([](String ip) {<br>    Serial.println(&quot;Wi-Fi connected! IP: &quot; + ip);<br>  });<br>  easyEsp.begin(&quot;EasyEsp-Setup&quot;); // Start the hotspot<br>}<br>void loop() {<br>  easyEsp.loop(); // Handle incoming setup requests from Android<br>}</pre><p>Flash this to your ESP32 via the Arduino IDE. It uses a lightweight asynchronous WebServer to expose two endpoints: 1. GET /networks — Returns a JSON array of surrounding Wi-Fi networks and signal strengths (RSSI). 2. POST /credentials — Accepts the target ssid and password from the Android app, drops the temporary hotspot, and connects to the home router.</p><p>Because it uses standard HTTP (via Ktor on Android), you can easily extend this to pass user tokens, MQTT broker URLs, or custom sensor data during the setup phase!</p><p>Get Started Today 🚀</p><p>Building IoT products is hard enough; onboarding shouldn’t be.</p><p>You can find the complete source code, the KMM shared library, the Jetpack Compose app, and the ESP32 firmware on GitHub.</p><p>🔗 <strong>GitHub Repository:</strong> <a href="https://github.com/codingwitharul/esay-esp">codingwitharul/esay-esp</a> 📚 <strong>Full Documentation:</strong> <a href="https://codingwitharul.github.io/esay-esp/">EasyESP Documentation</a></p><p>If this helps you build your next hardware project, drop a star on the repo! Happy coding! 👨‍💻💡</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b110317a5a41" width="1" height="1" alt=""><hr><p><a href="https://proandroiddev.com/how-to-connect-esp32-to-wi-fi-on-android-the-right-way-easyesp-b110317a5a41">How to Connect ESP32 to Wi-Fi on Android (The Right Way) | EasyEsp</a> was originally published in <a href="https://proandroiddev.com/">ProAndroidDev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Business Bench Karur Personal Review |When a Dream Home Becomes a Lesson in Construction…]]></title>
            <link>https://codingwitharul.medium.com/when-a-dream-home-becomes-a-lesson-in-construction-accountability-982966743f15?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/982966743f15</guid>
            <category><![CDATA[middle-class]]></category>
            <category><![CDATA[construction]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Mon, 13 Oct 2025 14:47:45 GMT</pubDate>
            <atom:updated>2026-08-31T06:32:38.513Z</atom:updated>
            <content:encoded><![CDATA[<h3>Business Bench Karur Personal Review |When a Dream Home Becomes a Lesson in Construction Accountability</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GnrL7vS6MIUynLdFVvXczA.png" /></figure><p>This is my personal experience with Business Bench Construction <a href="https://maps.app.goo.gl/imhozRGQif9muRVL6">https://maps.app.goo.gl/imhozRGQif9muRVL6</a> and I’m sharing it purely for awareness — don’t be swayed by glossy social-media marketing. I’ve managed to push the work forward and spent extra money to make the house habitable, but it’s far from the dream home we envisioned. Many homeowners won’t have the time or resources to fix these issues, so please read carefully and think twice before you start building your dream home.</p><p>In October 2023, I signed a construction agreement with a firm called <strong>Business Bench (Karur) </strong>for building my family’s home in Thoothukudi. Like most middle-class families, this wasn’t just another project — it was my parents’ lifelong dream.</p><p>My father, a 75-year-old auto driver, and my mother, 65, had waited years for this. I trusted the company’s advertisements, positive social media presence, and professional branding. They presented themselves as a <a href="https://www.linkedin.com/company/business-bench-construction-builders/">Business Bench Construction</a> that handled Project Monitoring, Quality Verification, and Material Checks (PMC).</p><p>But what followed was months of frustration, poor quality, and a complete lack of accountability.</p><h3>⚠️ What Went Wrong</h3><h3>1️⃣ Misleading Role and Supervision</h3><p>Business Bench acted more like a <strong>consultant or broker</strong>, not a true construction company. They designed, assigned an Associate Engineer, and moved to other projects. Once work began, there was no active supervision or site verification as promised. Even their so-called supervision did nothing — they won’t flag problems to you. You’re forced to discover defects yourself, and they simply refuse to take responsibility.</p><p>By the time I realised what was really happening, it was already too late to complain. I had no choice but to struggle and push them just to get the house finished — but not in the way I dreamed of.</p><h3>2️⃣ Material &amp; Execution Defects</h3><p>During site inspection and later stages, I found several serious issues:</p><ul><li><strong>Wrong TMT bars used</strong> — DSRM 500D instead of Ashwaryam 550D (as per agreement).</li><li><strong>Mulai Mattam</strong> (foundation alignment) completely off from the basement level.</li><li>Electrical points missing for exhaust fans and exterior lights. And poor cable management.</li><li><strong>Poor tile</strong> alignment and colour variation due to welding marks left uncleaned. Which is unrecoverable now and will cost 2–3 lakhs.</li><li><strong>Water leakage</strong> in terrace door caused by incorrect door fitting.</li><li><strong>Main door cracked </strong>open, and grouting tiles missing in many places.</li><li><strong>Elevation design </strong>didn’t match the original drawing they shared.</li><li><strong>Plumbing mishandling </strong>damaged the motor, which I had to repair for ₹5,000.</li><li>Even a chandelier light was stolen from the site after they stopped work.</li><li>Main door as per contract it should be teak but given was some other and its cracked</li></ul><h3>3️⃣ Abandonment and Blame</h3><p>Their Associate Engineer left the project midway without notice. When I approached Business Bench for rectification, they simply said <em>“we are not responsible”</em> and blamed me for trusting the engineer.</p><p>Ironically, every payment I made was as per the contract and shared transparently in our official WhatsApp group. Instead of owning up to failed supervision, they shifted blame onto the customer.</p><p>Finally, after 3–4 months of continuous struggle and with so many defects still left unresolved, they refused to take any responsibility. Gowthem from Business Bench bluntly told me, ‘We are not responsible for the defects — you have to bring back the engineer who left the project.’ How is that even possible? How can a company that marketed itself as a complete construction solution just walk away from its own commitment?</p><h3>4️⃣ Customer Support Failure</h3><p>After the engineer left, Business Bench’s customer support completely failed. Calls went unanswered, and no one visited the site for inspection. The company that once promised “end-to-end construction handling” simply distanced itself from the situation.</p><p>To make things worse, Business Bench even posted on Google Maps claiming they had completed my house, showcasing interior photos that were not done by them. It’s completely deceptive and manipulative — using someone’s unfinished home to promote their business.</p><h3>🧱 Professional Observation from Site Workers</h3><p>When the painters entered to complete finishing work, they noticed numerous cracks across walls and uneven paint layers because rollers weren’t used — only brushes. They had to repaint the entire house due to the poor earlier workmanship.</p><p>Every step exposed more hidden issues that proper quality control or PMC verification should have prevented.</p><h3>💔 The Human Side of It</h3><p>Every time I visit the site, the unfinished walls remind me of my parents’ dream fading little by little. It’s not just financial — it’s emotional. What started with excitement turned into exhaustion and regret.</p><p>No middle-class family should ever go through this pain — trusting marketing promises and ending up with stress instead of a home.</p><h3>🧩 What I Learned (And What You Should Know)</h3><p>If you’re planning to build a home or hire a construction firm, here’s my advice from experience:</p><p>✅ 1. Verify their actual role — Are they a <em>builder</em> or just a <em>consultant</em>? Ask clearly.</p><p>✅ 2. Demand detailed contracts — Include material brands, timelines, penalty clauses, and defect liability periods.</p><p>✅ 3. Track all payments in writing — Never make cash or off-record payments.</p><p>✅ 4. Document everything — Keep photos, messages, and proof of every commitment.</p><p>✅ 5. Visit the site regularly — Don’t rely only on updates or ads.</p><p>✅ 6. Get third-party verification — Hire an independent civil engineer to inspect the site monthly.</p><p>✅ 7. Review social media ads carefully — Marketing can be polished, but delivery matters. And don’t ignore 1 star reviews, watch 5 star reviews are deceptive.</p><h3>🕊️ Final Thoughts</h3><p>This post isn’t written out of anger. It’s written as a warning and awareness for others — especially middle-class families like mine who save for years to build a dream home.</p><p><a href="https://www.linkedin.com/company/business-bench-construction-builders/">Business Bench Construction</a> Business Bench (Karur) may have moved on to other projects, but for us, the damage remains — emotionally, financially, and structurally.</p><p>I truly hope no one else faces the same. Homes are built on trust, and once that cracks, no paint or plaster can fix it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GnrL7vS6MIUynLdFVvXczA.png" /></figure><p>If anyone needs guidance, I’m open to sharing everything I’ve learned through this difficult journey. My experience with Business Bench taught me hard lessons about construction, contracts, and supervision — and I’m willing to help others avoid the same mistakes.</p><p>My personal review: <a href="https://maps.app.goo.gl/BadBVViD8QGoPTdb7">https://maps.app.goo.gl/BadBVViD8QGoPTdb7</a></p><p>X Detailed Review: <a href="https://x.com/codingwitharul/status/1968379213460951421">https://x.com/codingwitharul/status/1968379213460951421</a></p><h3>#Construction #ConsumerRights #Thoothukudi #QualityControl #HomeBuilding #BusinessBench #MiddleClassDream #RealEstateAwareness #Tamilnadu #reivewBusinessBench</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=982966743f15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Compose Multiplatform with Google OAuth | Desktop, Android, iOS]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://codingwitharul.medium.com/compose-multiplatform-with-google-oauth-desktop-android-ios-39a6e256a6cb?source=rss-6a5e42cee40f------2"><img src="https://cdn-images-1.medium.com/max/1010/1*x3so59Debqr-7FbHYYqXvQ.png" width="1010"></a></p><p class="medium-feed-snippet">Seamless Google OAuth in Compose Multiplatform | Android, iOS &amp; Desktop, All in One Login |</p><p class="medium-feed-link"><a href="https://codingwitharul.medium.com/compose-multiplatform-with-google-oauth-desktop-android-ios-39a6e256a6cb?source=rss-6a5e42cee40f------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://codingwitharul.medium.com/compose-multiplatform-with-google-oauth-desktop-android-ios-39a6e256a6cb?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/39a6e256a6cb</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[kotlin-multiplatform]]></category>
            <category><![CDATA[desktop-app]]></category>
            <category><![CDATA[compose-multiplatform]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 16:59:33 GMT</pubDate>
            <atom:updated>2025-08-19T18:14:25.022Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Compose Multi Platform + Custom Camera With Common Capture Design]]></title>
            <link>https://proandroiddev.com/compose-multi-platform-custom-camera-with-common-capture-design-386dbc2aa03e?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/386dbc2aa03e</guid>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[jetpack-compose]]></category>
            <category><![CDATA[compose-multiplatform]]></category>
            <category><![CDATA[kotlin-multiplatform]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Mon, 21 Jul 2025 00:54:03 GMT</pubDate>
            <atom:updated>2025-11-18T06:23:29.854Z</atom:updated>
            <content:encoded><![CDATA[<h3>Compose Multi-Platform + Custom Camera With Common Capture Design</h3><p>In this article, we’ll dive into how to build a <strong>custom camera module</strong> in a <strong>Compose Multiplatform (CMP)</strong> project using a shared design pattern. We’ll leverage expect/actual to abstract platform-specific camera logic, while keeping the <strong>UI </strong>and <strong>interaction layer </strong>common across Android and iOS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uEcvB_Ufx2Zct1OSxiKqUw.png" /></figure><h3>Why a Custom Camera in CMP?</h3><ul><li>Native camera APIs are platform-specific</li><li>Compose Multiplatform enables shared UI but needs abstraction for platform access</li><li>A common capture interface improves testability, reuse, and architectural cleanliness</li><li>Does not depend on 3rd party libraries</li></ul><figure><img alt="Kotlin Multiplatform Shared Camera" src="https://cdn-images-1.medium.com/max/717/1*lccxXjATwY75uhtbtN18tA.png" /></figure><p>Like above mentioned diagram we implement <strong>CameraView</strong> in separate platform and controls &amp; control designs are in <em>commonMain</em>.</p><h3>Lets get started</h3><p>Add following in commonMain</p><p>/commonMain/common/Camera.kt</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4460cb0597c9c26980fdd311329326df/href">https://medium.com/media/4460cb0597c9c26980fdd311329326df/href</a></iframe><h4><strong>Explanation:</strong></h4><ul><li><strong>Platform-Agnostic Structure</strong> CameraView is defined as an expect composable, which allows you to implement platform-specific camera UIs separately for Android, iOS, etc., using Kotlin Multiplatform.</li><li><strong>Event-Driven Camera Control</strong> CameraEvent is a sealed class that represents user actions (like capturing or switching camera). These events are dispatched through a coroutine-based Channel to the UI layer.</li><li><strong>Reactive State Handling via Flow</strong> CameraCallback collects camera events using eventFlow, making the UI respond dynamically to user-triggered actions outside the composable.</li><li><strong>Abstracted Capture Result Handling</strong> onCaptureImage() is an abstract function that handles image results uniformly across platforms, providing a clean contract for success or error callbacks.</li></ul><blockquote>We used <strong>CameraCallback</strong> to observer user event on each platform. And received <strong>onCaptureImage</strong> in common UI to get the image path.</blockquote><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/426807d4c83facb5c95f9e5d7c7e7fd8/href">https://medium.com/media/426807d4c83facb5c95f9e5d7c7e7fd8/href</a></iframe><h4>Explanation</h4><p><strong>Preview Setup</strong></p><ul><li>PreviewView: A view that displays the camera preview.</li><li>Preview.Builder(): Creates a preview use case.</li><li>Binds the preview to the lifecycle of the activity using cameraProvider.bindToLifecycle.</li></ul><p><strong>Capture Photo (</strong><strong>takePicture)</strong></p><ul><li>Creates a file in the app’s internal or external storage.</li><li>Uses ImageCapture.takePicture() to capture the photo.</li><li>Handles success and error via OnImageSavedCallback.</li></ul><p><strong>Switch Camera Lens (</strong><strong>switchLens)</strong></p><ul><li>Toggles between front (CameraSelector.LENS_FACING_FRONT) and back (LENS_FACING_BACK) cameras.</li><li>Rebinds the camera with the updated lens configuration.</li></ul><p><strong>Camera Binding (</strong><strong>LaunchedEffect)</strong></p><ul><li>Waits for the camera to be ready (cameraProviderFuture).</li><li>Builds and binds the camera use cases (preview and image capture).</li><li>Reacts to lens changes to rebind camera.</li></ul><p><strong>Composable Lifecycle Hooks</strong></p><ul><li>DisposableEffect: Unbinds camera use cases when CameraView is disposed, preventing resource leaks.</li><li>LaunchedEffect: Observes camera events (CameraEvent) and triggers actions accordingly.</li></ul><p><strong>File Storage</strong></p><ul><li>getOutputDirectory(): Ensures the image is saved in either a custom external media directory (bms) or fallback to internal storage.</li><li>No special permissions are required for internal storage.</li></ul><p><strong>Event Observer</strong></p><pre>callback.eventFlow.collect {<br>    when (it) {<br>        CameraEvent.CaptureImage -&gt; takePicture()<br>        CameraEvent.SwitchCamera -&gt; switchLens()<br>    }<br>}</pre><ul><li>Listens for camera-related events.</li><li>Makes the composable reactive to user actions outside the view (like a button click elsewhere that triggers CameraEvent).</li></ul><p>And <strong>Finally</strong> <strong>iOS</strong> Implementation,</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b4719dbcbc931edb20fdd35cd8bb282e/href">https://medium.com/media/b4719dbcbc931edb20fdd35cd8bb282e/href</a></iframe><h4>Explanation</h4><p><strong>Camera Setup</strong></p><ul><li>Initializes AVCaptureSession with photo preset for high-resolution image capture.</li><li>Adds AVCaptureStillImageOutput with JPEG codec configuration to the session.</li></ul><p><strong>Camera Devices &amp; Switching</strong></p><ul><li>Retrieves <strong>front and back cameras</strong> using AVCaptureDevice and determines which one to activate.</li><li>Switches between front/back cameras by removing and re-adding the appropriate AVCaptureDeviceInput.</li></ul><p><strong>Preview Rendering</strong></p><ul><li>Creates a UIView container and inserts an AVCaptureVideoPreviewLayer to show live camera feed.</li><li>Uses UIKitView from Compose to embed the native preview into the Compose UI with full size and dynamic resizing.</li></ul><p><strong>Event Handling via Flow</strong></p><ul><li>Collects camera-related events from CameraCallback.eventFlow:</li><li>CameraEvent.CaptureImage captures a photo asynchronously and saves it to a temporary location.</li><li>CameraEvent.SwitchCamera reconfigures session inputs to switch between cameras.</li><li>The result is passed back via callback.onCaptureImage(imagePath).</li></ul><p>So basically same implementation like android with <strong>iosComponent</strong> in it. Dont forget the callback!!!</p><h3>How to Consume?</h3><p>Lets see how we consume inside commonMain</p><p>Create <strong>ImageCaptureView</strong> <em>Composable</em> <em>Component, </em>below approach will be useful when we reuse the <strong>ImageCaptureView</strong> on different screens.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c126c286c0975dcbe1de6eb468ec7f21/href">https://medium.com/media/c126c286c0975dcbe1de6eb468ec7f21/href</a></iframe><p>And wherever we want to implement in application we can do like following.</p><pre>var showCamera by remember { mutableStateOf(false) }<br>var imagePath by remember { mutableStateOf&lt;Path?&gt;(null) }<br>if (showCamera) {<br>    ImageCaptureView(onImageCaptured = {<br>        scope.launch {<br>            showCamera = false<br>            imagePath = it<br>        }<br>    }, onClose = { showCamera = false })<br>}</pre><h3>Conclusion</h3><p>Our implementation successfully combines shared business logic with powerful native features, delivering a consistent UI across platforms. It’s scalable for additional capabilities like video recording, zoom, and filters. You’ve achieved a modern, maintainable solution that aligns with best practices for <strong>MultiPlatform</strong> development.</p><p>There are libraries that make this easier, but if we truly want a custom camera solution, this thread will be helpful. :-)</p><p>Let me know if you’d like to extend this with extra functionality or refactor pieces for even better performance or testing. ;-)</p><p>—</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=386dbc2aa03e" width="1" height="1" alt=""><hr><p><a href="https://proandroiddev.com/compose-multi-platform-custom-camera-with-common-capture-design-386dbc2aa03e">Compose Multi Platform + Custom Camera With Common Capture Design</a> was originally published in <a href="https://proandroiddev.com/">ProAndroidDev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Compose Multiplatform + Ktor: Secure Networking with Bearer Auth and Shared Code]]></title>
            <link>https://proandroiddev.com/compose-multiplatform-ktor-secure-networking-with-bearer-auth-and-shared-code-93a5e32b2c4e?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/93a5e32b2c4e</guid>
            <category><![CDATA[compose-multiplatform]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[kotlin-multiplatform]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Mon, 07 Jul 2025 07:00:47 GMT</pubDate>
            <atom:updated>2025-07-13T07:56:06.192Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wo1SxpHZrJnxMA4tLN046A.png" /></figure><p>Compose Multi Platform (CMP) is the future of cross-platform UI development, powered by JetBrains and Kotlin. It lets you write UI once and run it across Android, iOS, Desktop, and Web.</p><p>But great UI needs data — and that’s where <strong>Ktor</strong> comes in.</p><blockquote><em>🤔 </em>What if we could use a single networking client across all platforms — Android, iOS, Desktop, and even Web?</blockquote><p>With <strong>Ktor</strong>, we can.</p><p>In this guide, we’ll walk through setting up Ktor in a CMP project, making real API calls, and connecting them to your Compose UI.</p><h3>Why Ktor?</h3><p>Ktor is Kotlin-native, coroutine-friendly, and <strong>multiplatform-ready</strong>. It gives you a single API to:</p><ul><li>Make HTTP requests (GET, POST, etc.)</li><li>Parse JSON with kotlinx.serialization</li><li>Handle timeouts, headers, and logging</li><li>Run seamlessly across platforms</li></ul><blockquote><em>CMP + Ktor = Minimal boilerplate, maximum productivity</em></blockquote><h4>Project Structure</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0105ff806772f10795db672f5ad4531f/href">https://medium.com/media/0105ff806772f10795db672f5ad4531f/href</a></iframe><p>This is a <strong>clean and modular architecture</strong>, and it gives a great real-world foundation for the CMP project.</p><h4>Directory Overview</h4><p>Your networking code is cleanly structured inside the data layer:</p><ul><li><strong>networking</strong>/<strong>models</strong>/ — contains shared data models and helpers like: <strong>ApiClientHelper.kt</strong> — defines the Ktor client setup</li><li><strong>networking</strong>/<strong>ApiResponse.kt</strong> — defines the generic response wrapper</li><li><strong>networking</strong>/<strong>Constants.kt</strong> — stores base URLs, endpoints, etc.</li></ul><p>This separation improves maintainability and makes your codebase scalable for adding authentication, caching, or interceptors.</p><p>Lets see whats inside B&gt;</p><p>In <strong>CommonMain</strong>, Create <a href="https://www.jetbrains.com/help/kotlin-multiplatform-dev/multiplatform-expect-actual.html"><strong><em>expect</em></strong></a> functionality like below</p><p>Learn more about expect/actual <a href="https://www.jetbrains.com/help/kotlin-multiplatform-dev/multiplatform-expect-actual.html">here</a></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1b0700e73209bdece696e2f9a183db9a/href">https://medium.com/media/1b0700e73209bdece696e2f9a183db9a/href</a></iframe><p>In <strong>AndroidMain</strong>, Create <strong><em>actual </em></strong>functionality like below</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/471ec9e45028484236d4c7d4c34c3523/href">https://medium.com/media/471ec9e45028484236d4c7d4c34c3523/href</a></iframe><p>Then In <strong>iosMain, </strong>Create <strong><em>actual </em></strong>functionality like below</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2acacc7620276b8e8dd4c8deccd5001b/href">https://medium.com/media/2acacc7620276b8e8dd4c8deccd5001b/href</a></iframe><h3><strong>Explanation</strong></h3><p>In <strong>Ktor</strong>, a “driver” is the <strong>HTTP engine</strong> that powers the actual network communication for the HttpClient.</p><p>Since Ktor is designed to run on multiple platforms — like Android, iOS, JVM, and the browser — it cannot rely on a single networking implementation. Instead, it uses <strong>pluggable drivers</strong>, one for each platform.</p><p>So in simple terms:</p><blockquote><em>A </em><strong><em>Ktor driver</em></strong><em> is like the </em><strong><em>network engine</em></strong><em> specific to each platform that tells Ktor how to actually send and receive HTTP requests.</em></blockquote><h4>Why Do We Need Drivers?</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F15519638&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fen-GB%2Fview%2Fcat-driving-serious-cat-driving-focus-driving-gif-15519638&amp;image=https%3A%2F%2Fmedia.tenor.com%2FuB6486L-xFMAAAAN%2Fcat-driving-serious.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/a66facd2400994e9ea57ac3d0d405ae8/href">https://medium.com/media/a66facd2400994e9ea57ac3d0d405ae8/href</a></iframe><p>Because different platforms have <strong>different underlying technologies</strong> for networking:</p><blockquote>Ktor abstracts these differences using drivers.</blockquote><p>That way, you can write <strong>one piece of networking code</strong> in your shared Kotlin module — and the correct driver will handle how that request works on Android, iOS, etc.</p><ul><li><strong>Android</strong> uses <strong>OkHttp</strong>, a popular HTTP client that is reliable, efficient, and optimized for mobile.</li><li><strong>iOS</strong> uses <strong>URLSession</strong> via <strong>Darwin</strong>, Apple’s native networking layer, ensuring deep integration with the iOS ecosystem.</li><li><strong>Desktop and JVM</strong> targets use <strong>Java Sockets</strong> or the <strong>CIO (Coroutine-based I/O) engine</strong>, depending on configuration and performance needs.</li><li><strong>Web</strong> targets rely on the browser’s built-in <strong>fetch() API</strong>, aligning with modern web standards and security models</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*32O6qN3KYS-JpHceQ7GIOA.png" /><figcaption>Above <strong>highlighted</strong> shows android implementation of <strong>OkHttp</strong></figcaption></figure><p>Lets do some common code,</p><p><strong>ApiResponse.kt</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf2c503ed657e419ef9792741ec22fbf/href">https://medium.com/media/cf2c503ed657e419ef9792741ec22fbf/href</a></iframe><p><strong>Constants.kt</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2f6d7b8bc1b2d48a7c383a7e0e29249f/href">https://medium.com/media/2f6d7b8bc1b2d48a7c383a7e0e29249f/href</a></iframe><p><strong>ApiClientHelper</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/256d87071238a468609811a9883d6d99/href">https://medium.com/media/256d87071238a468609811a9883d6d99/href</a></iframe><h3>Explanation</h3><h4>Overview: ApiClientHelper</h4><p>This class sets up a <strong>Ktor HttpClient</strong> with:</p><ul><li>Timeout</li><li>Logging</li><li>Bearer Authentication (from DB)</li><li>JSON serialization</li><li>Safe error-handling</li></ul><p>It’s used to make API calls in a <strong>Compose Multiplatform app</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/1*YS3UWDv70AX3Inp-zHVP9Q.png" /><figcaption>Using <strong>expect</strong> <strong>httpClient</strong> inside common code.</figcaption></figure><h4>sendWithoutRequest</h4><p>This block is part of Ktor&#39;s Auth plugin — specifically the bearer { ... } block — used to <strong>control when the Authorization header should be added</strong>.</p><h4>Extension: apiEndPoint(endPoint: String)</h4><ul><li>Prepends the base Constants.HOST to a given endpoint</li><li>Sets Content-Type: application/json</li></ul><h4>safeRequest Extension Function</h4><p>Handles API calls with <strong>typed error handling</strong>:</p><pre>HttpClient.safeRequest&lt;T, E&gt; { ... }</pre><ul><li>On success → returns:</li></ul><p>ApiResponse.Success&lt;T&gt;</p><ul><li>On failure → returns:</li></ul><p>Unauthorized, HttpError, NetworkError, or SerializationError</p><h4>errorBody&lt;E&gt;()</h4><ul><li>Extracts error response body and deserializes it to E?</li></ul><h3>Lets Consume the API</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F15408812760974594408&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fen-GB%2Fview%2Fsitting-down-while-enjoying-and-eating-an-apple-pie-happily-blushes-gif-15408812760974594408&amp;image=https%3A%2F%2Fmedia.tenor.com%2F1dcZkRRlkWgAAAAN%2Fsitting-down-while-enjoying-and-eating-an-apple-pie-happily-blushes.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/2348bb9f77c8d7638e24df73c6d2ff3b/href">https://medium.com/media/2348bb9f77c8d7638e24df73c6d2ff3b/href</a></iframe><p>In this section, let’s walk through how we implemented <strong>secure OAuth-based login</strong> using Ktor, local DB storage, and clean architecture in Compose Multiplatform.</p><p>We follow a simple repository pattern:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/232223c7c44b7a50592bd3b1af8e103a/href">https://medium.com/media/232223c7c44b7a50592bd3b1af8e103a/href</a></iframe><h3>What This Does (Explained)</h3><ul><li><strong>safeRequest</strong><br> Wraps the API call and gracefully handles network, HTTP, and serialization errors. This keeps your logic clean and avoids messy try-catch blocks.</li><li><strong>apiEndPoint(...)</strong><br> Builds the complete endpoint URL by combining a base host with the given path — ensuring consistent and centralized URL formatting.</li><li><strong>setBody(user)</strong><br> Sends the GoogleUser OAuth object to your backend. It’s automatically serialized into JSON using kotlinx.serialization.</li><li>️ <strong>Error Handling</strong><br> If the response is an error, it’s wrapped in a Result.failure(...). You can extract detailed messages using getErrorData() and convert them into exceptions using .toThrowable().</li><li><strong>toUserInfo()</strong><br> Converts the successful GoogleUser response into a local UserInfo object — usually adding fields like access token, name, email, etc.</li><li><strong>saveUserInfo(...)</strong><br> Persists the logged-in user info in the local database for session management and future authenticated requests.</li></ul><h3>Conclusion</h3><p>By leveraging <strong>Ktor with platform-specific drivers (OkHttp for Android, Darwin for iOS)</strong> and Kotlin Multiplatform’s expect/actual pattern, we’ve created a powerful, clean, and scalable way to handle networking across platforms.</p><p>Our implementation of ApiClientHelper and safeRequest() ensures:</p><ul><li>Consistent error handling</li><li>Secure token-based authentication</li><li>Centralized request configuration</li><li>Native performance and behavior on each platform</li></ul><p>With this setup, adding features like <strong>token refresh</strong>, <strong>retry logic</strong>, or <strong>offline sync</strong> becomes straightforward and modular. It also plays nicely with modern MVI or MVVM patterns in your Compose UI.</p><p>Whether you’re targeting Android, iOS, or Desktop, this architecture gives you a <strong>solid foundation</strong> to build production-ready network flows that are clean, testable, and future-proof.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93a5e32b2c4e" width="1" height="1" alt=""><hr><p><a href="https://proandroiddev.com/compose-multiplatform-ktor-secure-networking-with-bearer-auth-and-shared-code-93a5e32b2c4e">Compose Multiplatform + Ktor: Secure Networking with Bearer Auth and Shared Code</a> was originally published in <a href="https://proandroiddev.com/">ProAndroidDev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jetpack Compose with Android Fragment | UI & Data Sharing]]></title>
            <link>https://proandroiddev.com/jetpack-compose-with-android-fragment-ui-data-sharing-ae7077a9a160?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae7077a9a160</guid>
            <category><![CDATA[jetpack-compose]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[kotlin]]></category>
            <category><![CDATA[fragments]]></category>
            <category><![CDATA[kotlin-multiplatform]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Tue, 21 Jan 2025 03:15:24 GMT</pubDate>
            <atom:updated>2025-07-21T16:56:38.489Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Jetpack Compose with Android Fragment: A Fun and Dynamic Duo!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*jeRe_BsNR8m5yci7JFW1rg.jpeg" /></figure><p>Ah, Jetpack Compose — the shiny new tool in our Android arsenal. It promises simplicity, elegance, and speed for building UIs. But what happens when you want to use it in an app still tethered to our good old friend, the <strong>Fragment</strong>? Fear not! You can have the best of both worlds. Let’s dive in and make this duo work, with a sprinkle of fun.</p><h3>Why Mix Compose with Fragments?</h3><p>Sure, Jetpack Compose is the future, but:</p><ol><li>Your project is legacy-heavy and built around Fragments.</li><li>You want to migrate gradually, instead of throwing everything into chaos.</li><li>Some features, like Navigation or libraries, are still Fragment-friendly.</li></ol><p>Whatever your reason, integrating Compose into a Fragment-based app can be seamless and… dare I say, fun?</p><h3>Setting Up the Scene</h3><p>Before we dive into code, ensure you’ve set up Jetpack Compose in your project:</p><p><strong>Add dependencies</strong>:</p><pre>implementation &quot;androidx.activity:activity-compose:1.7.2&quot;<br>implementation &quot;androidx.compose.ui:ui:1.4.3&quot;<br>implementation &quot;androidx.compose.material:material:1.4.3&quot;<br>implementation &quot;androidx.lifecycle:lifecycle-viewmodel-compose:2.6.1&quot;</pre><p><strong>Enable Compose in your </strong><strong>build.gradle</strong>:</p><pre>android {<br>    buildFeatures {<br>        compose true<br>    }<br>    composeOptions {<br>        kotlinCompilerExtensionVersion &#39;1.5.3&#39;<br>    }<br>.<br>.<br>.<br>}</pre><p>With this, we’re ready to rock and roll.</p><h3>Jetpack Compose Inside a Fragment</h3><p>Imagine this: You have a MyFragment where you want to sprinkle some Compose magic. Here’s how you do it:</p><h4>1. Create a ComposeView</h4><p>The magic starts with a ComposeView. It’s a bridge that connects the world of XML to Compose. In your Fragment, override onCreateView:</p><pre>class MyFragment : Fragment() {<br>  override fun onCreateView(<br>          inflater: LayoutInflater,<br>          container: ViewGroup?,<br>          savedInstanceState: Bundle?<br>      ): View {<br>          val composeView = ComposeView(requireContext())<br>          composeView.setContent {<br>              GreetingMessage(&quot;Hello from Compose inside Fragment!&quot;)<br>          }<br>          return composeView<br>      }<br>.<br>.<br>.<br>}</pre><h4>2. Define Your Compose Content</h4><p>Compose UIs are just functions. Here’s a simple composable:</p><pre>@Composable<br>fun GreetingMessage(message: String) {<br>    Box(<br>        modifier = Modifier<br>            .fillMaxSize()<br>            .background(Color(0xFFBB86FC)),<br>        contentAlignment = Alignment.Center<br>    ) {<br>        Text(<br>            text = message,<br>            color = Color.White,<br>            fontSize = 24.sp,<br>            fontWeight = FontWeight.Bold<br>        )<br>    }<br>}</pre><p>And there you go! You’ve successfully placed a Compose UI inside a Fragment.</p><h3>Android Fragment Inside Jetpack Compose</h3><p>What if the tables are turned? You want to embed a Fragment within Jetpack Compose. You can do that too, using the AndroidView or Android ViewBinding composable.</p><p>Its required <strong>Android</strong> <strong>ViewBinding</strong> on <strong>Fragments</strong>. See full details here about view binding <a href="https://developer.android.com/topic/libraries/view-binding">https://developer.android.com/topic/libraries/view-binding</a>.</p><p>After enable generate build to generate the view binding class then follow the following steps.</p><h4>1. Create following xml in layout directory.</h4><p><em>my_fragment.xml</em></p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;<br>&lt;androidx.fragment.app.FragmentContainerView xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;<br>    android:id=&quot;@+id/my_fragment&quot;<br>    android:layout_width=&quot;match_parent&quot;<br>    android:layout_height=&quot;match_parent&quot;<br>    android:name=&quot;com.hello.world.lib.ui.HelloFragment&quot;<br>    /&gt;</pre><h4>2. Use Fragment Inside Compose</h4><pre>@Composable<br>fun GreetingMessage(message: String) {<br>  AndroidViewBinding(<br>      MyFragmentBinding::inflate,<br>      Modifier.fillMaxSize(),<br>  ) {<br>     val helloFrag = this.myFragment.getFragment&lt;HelloFragment&gt;()<br>     // helloFrag.binding access all public fun and variable.<br>   }<br>}</pre><h4>Here we go another approach…</h4><h4>1. Add a FragmentContainerView</h4><p>In your Compose layout, use AndroidView to embed a FragmentContainerView:</p><pre>@Composable<br>fun FragmentContainer() {<br>    AndroidView(<br>        factory = { context -&gt;<br>            FragmentContainerView(context).apply {<br>                id = R.id.fragment_container_view<br>            }<br>        },<br>        modifier = Modifier.fillMaxSize()<br>    )<br>}</pre><h4>2. Attach the Fragment</h4><p>In your Activity or Parent Fragment:</p><pre>setContent {<br>    FragmentContainer()<br>}</pre><pre>supportFragmentManager.beginTransaction()<br>    .replace(R.id.fragment_container_view, MyFragment())<br>    .commit()</pre><h3>Communicating Between Compose and Fragment via ViewModel</h3><p>A ViewModel is your best friend for seamless communication between Compose and Fragments. The `activityViewModels` is key to transfer data between the fragments to Composable components.</p><p>Another option we can use hilt dependency injection to inject singleton class or create companion object to fragment and use the same in Composable to share static data.</p><h4>1. Create a Shared ViewModel</h4><pre>class SharedViewModel : ViewModel() {<br>    val message: MutableLiveData&lt;String&gt; = MutableLiveData(&quot;Hello from ViewModel!&quot;)<br>}</pre><h4>2. Observe ViewModel in Fragment</h4><pre>class MyFragment : Fragment() {<br>    private val viewModel: SharedViewModel by activityViewModels()<br>override fun onCreateView(<br>        inflater: LayoutInflater,<br>        container: ViewGroup?,<br>        savedInstanceState: Bundle?<br>    ): View {<br>        val composeView = ComposeView(requireContext())<br>        composeView.setContent {<br>            GreetingWithViewModel(viewModel)<br>        }<br>        return composeView<br>    }<br>}</pre><h4>3. Use ViewModel in Compose</h4><pre>@Composable<br>fun GreetingWithViewModel(viewModel: SharedViewModel) {<br>    val message by viewModel.message.observeAsState()<br>    Box(<br>            modifier = Modifier<br>                .fillMaxSize()<br>                .background(Color(0xFFBB86FC)),<br>            contentAlignment = Alignment.Center<br>        ) {<br>            Text(<br>                text = message ?: &quot;&quot;,<br>                color = Color.White,<br>                fontSize = 24.sp,<br>                fontWeight = FontWeight.Bold<br>            )<br>        }<br>    }<br>}</pre><p>This approach ensures both your Fragment and Compose UI stay in sync, fostering a harmonious relationship between the two.</p><p>Boom! XML and Compose working together like peanut butter and jelly. 🍓🍪</p><p><strong>GIF Time!</strong> Picture this: Compose and Fragments awkwardly working together for the first time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/195/0*pS84bzmcE0iBtyJe.gif" /></figure><p>But after some code love, they become best friends:</p><h3>Tips for a Happy Integration Folks</h3><p><strong>State Management</strong>: Use ViewModel to manage state and pass data to Compose. This avoids tight coupling and ensures reusability.</p><pre>class MyViewModel : ViewModel() {<br>    val message = MutableLiveData(&quot;Hello from ViewModel!&quot;)<br>}</pre><p>In Compose:</p><pre>@Composable<br>fun GreetingMessage(viewModel: MyViewModel) {<br>    val message by viewModel.message.observeAsState()<br>    Text(text = message ?: &quot;&quot;)<br>}</pre><p><strong>Animation Fun</strong>: Add some Compose animations for a touch of pizzazz ;).</p><pre>@Composable<br>fun AnimatedGreetingMessage() {<br>    var isBig by remember { mutableStateOf(false) }<br>    val size by animateDpAsState(targetValue = if (isBig) 200.dp else 100.dp)<br><br>    Box(<br>        modifier = Modifier<br>            .size(size)<br>            .background(Color.Red)<br>            .clickable { isBig = !isBig }<br>    )<br>}</pre><p><em>Imagine this box growing and shrinking. Fun, right?</em></p><h3>Problem we face with Android Fragment &amp; Compose</h3><p>Yeahhhhh, Apart from fun its give us little struggles we solved with workaround but still its fun :P.</p><p><strong>Problem 1:</strong></p><p>When we use a Fragment inside the Jetpack Compose navigation component while switching between Compose view and a fragment some fragment lifecycle gets messed up and the fragment not refreshing probably.</p><p>So we come with with workaround show loading or animation on 100 mils.</p><pre>@Composable<br>fun HelloGreetingMessage() {<br>  var show by remember { mutableStateOf(false) }<br>  LaunchedEffect(key1 = state.value.uiState) {<br>      show = false<br>      delay(100)<br>      show = true<br>  }<br>  if (show) {<br>      AndroidViewBinding(<br>          MapFragmentBinding::inflate,<br>          Modifier.fillMaxSize(),<br>      ) {}<br>  }<br>}</pre><p>This will solve the issue for time period it might not occur on latest Jetpack compose so test it and use it.</p><p><strong>Problem 2:</strong></p><p>Loading… 😉</p><p>If any new problem come it will listed here make sure bookmark this thread.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*efmDX5ASdQA4ghD-" /><figcaption>Photo by <a href="https://unsplash.com/@humakabakci?utm_source=medium&amp;utm_medium=referral">Huma Kabakci</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Conclusion</h3><p>Jetpack Compose and Fragments may seem like an unlikely pair, but they can work harmoniously. Whether you’re gradually migrating or just experimenting, these steps make integration straightforward and enjoyable.</p><p>So, what are you waiting for? Go sprinkle some Compose magic in your Fragment-based app and share your experiences. And remember, a little humor (and maybe a GIF) makes coding even better! 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae7077a9a160" width="1" height="1" alt=""><hr><p><a href="https://proandroiddev.com/jetpack-compose-with-android-fragment-ui-data-sharing-ae7077a9a160">Jetpack Compose with Android Fragment | UI &amp; Data Sharing</a> was originally published in <a href="https://proandroiddev.com/">ProAndroidDev</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Change APK name in Android Gradle 8.1+ kts | AGP 8.1]]></title>
            <link>https://medium.com/geekculture/change-apk-name-in-android-gradle-8-1-kts-97c55fcaaa27?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/97c55fcaaa27</guid>
            <category><![CDATA[gradle-kotlin-dsl]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Fri, 02 Feb 2024 03:27:43 GMT</pubDate>
            <atom:updated>2024-09-13T04:30:20.188Z</atom:updated>
            <content:encoded><![CDATA[<p>Changing the APK name whenever AGP changes is tiresome work so I&#39;m gonna jot down all the gradle versions and their way to change the APK name in it.</p><p>Fella android devs feel free to add more in the comments section. ;)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GeTsjlCdHIP7625S" /><figcaption>Photo by <a href="https://unsplash.com/@louis993546?utm_source=medium&amp;utm_medium=referral">Louis Tsai</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Gradle 8.1.4 kts</h4><p>The following snippets work in KMP as well.</p><pre>android {<br>...<br>applicationVariants.all {<br>    this.outputs<br>        .map { it as com.android.build.gradle.internal.api.ApkVariantOutputImpl }<br>        .forEach { output -&gt;<br>            val variant = this.buildType.name<br>            var apkName =<br>                this.flavorName[0].uppercase() + this.flavorName.substring(1) + &quot;_&quot; + this.versionName<br>            if (variant.isNotEmpty()) apkName += &quot;_$variant&quot;<br>            apkName += &quot;.apk&quot;<br>            println(&quot;ApkName=$apkName ${this.buildType.name}&quot;)<br>            output.outputFileName = apkName<br>        }<br>}<br>...</pre><h4>Gradle 8.1+ kts</h4><p>The following snippets work in KMM as well.</p><pre>android {<br>...<br>  productFlavors {<br>      create(&quot;free&quot;) {<br>          dimension = &quot;app&quot;<br>          val appName = &quot;Free App 2.0&quot;<br>          manifestPlaceholders[&quot;appName&quot;] = appName<br>          applicationIdSuffix = &quot;.demo&quot;<br>          versionName = &quot;1.0.0&quot;<br>          versionNameSuffix = &quot;.3&quot;<br>          versionCode = (versionName + versionNameSuffix).replace(&quot;.&quot;, &quot;&quot;).toInt()<br>          val apkName = &quot;${appName}_$versionName$versionNameSuffix($versionCode).apk&quot;<br>  <br>          // change app name block below<br>          buildOutputs.all {<br>              val variantOutputImpl = this as com.android.build.gradle.internal.api.BaseVariantOutputImpl<br>              variantOutputImpl.outputFileName =  apkName<br>          }<br>      }<br>  }<br>}</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97c55fcaaa27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/change-apk-name-in-android-gradle-8-1-kts-97c55fcaaa27">Change APK name in Android Gradle 8.1+ kts | AGP 8.1</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[Jetpack Compose CLI | NPM Package | Boilerplate generator]]></title>
            <link>https://medium.com/geekculture/jetpack-compose-cli-npm-package-boilerplate-generator-cf761a047785?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf761a047785</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[command-line-interface]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[jetpack-compose]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Sat, 13 Jan 2024 10:35:34 GMT</pubDate>
            <atom:updated>2024-01-13T10:35:34.392Z</atom:updated>
            <content:encoded><![CDATA[<p>Since moving forward in app development we create new applications from scratch which time is taken the process of setup architecture, DI, DB config, and Network configuration so I decided to create an npm package that is helping create the Android Compose app in seconds.</p><p>Here you go, Presenting you a <strong>Jetpack-compose-cli</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a9k-Ae4vIT6HhIjM" /><figcaption>Photo by <a href="https://unsplash.com/@nullplus?utm_source=medium&amp;utm_medium=referral">Razvan Chisu</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3><strong>Let’s get down to business</strong></h3><p>—</p><blockquote>Note: Before starting, you have to install <strong>node</strong> npm in your system follow the link to install node <a href="https://nodejs.org/en/download/">https://nodejs.org/en/download/</a></blockquote><p>Step1: Install the Npm package using the following cmd</p><pre>npm install -g jetpack-compose-cli</pre><p>Step 2: Run the Generator from anywhere in the terminal.</p><pre>jetpack-compose-cli create-compose-app</pre><p>Step 3: Enter the project details in the terminal</p><pre><em>? Select version</em>: <strong>1.0.1</strong><br><em>? Enter application name: </em><strong><em>NewsApp</em></strong><em><br>? Enter package Id: </em><strong><em>com.mycompany.newsapp</em></strong><em><br>? Enter application Id: </em><strong><em>com.mycompany.newsapp</em></strong><em><br>? Enter application version Id: </em><strong><em>1.0.0</em></strong><em><br>? Do you want to add google service(Y/N)? </em><strong><em>Y</em></strong><em><br>? Select google-service.json: file /../google.json<br>? Do you want to add firebase(Y?N)? </em><strong><em>Y</em></strong><em><br>? Choose networking lib: </em><strong><em>Retrofit</em></strong><em><br>? Enter the Base URL for networking: </em><a href="https://192.168.1.12:8080/"><strong><em>https://192.168.1.12:8080</em></strong></a><em><br>? Choose database lib: </em><strong><em>Room</em></strong></pre><pre>Project successfully created loc <strong>/home/arul/JC-Projects/NewsApp</strong></pre><p>And BOOOOOOM !!!!!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CWe-MJkSJtrED0ON" /><figcaption>Photo by <a href="https://unsplash.com/@jentheodore?utm_source=medium&amp;utm_medium=referral">Jen Theodore</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The project has been created at a particular location. Just open the project in Android Studio and start working.</p><p>The project will be configured with MVM architecture.</p><h3>Next,</h3><p>Behind the scenes how it works will be jotted down soon.</p><p>Leave star ;)</p><p><a href="https://github.com/arulwastaken/Jetpack-Compose-CLI">https://github.com/arulwastaken/Jetpack-Compose-CLI</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf761a047785" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/jetpack-compose-cli-npm-package-boilerplate-generator-cf761a047785">Jetpack Compose CLI | NPM Package | Boilerplate generator</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[Simple Flutter rating bar | DIY: NoPlugin | Flutter Begineer]]></title>
            <link>https://codingwitharul.medium.com/simple-flutter-rating-bar-diy-noplugin-flutter-begineer-56a043283d5e?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/56a043283d5e</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[androiddev]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Thu, 24 Jun 2021 19:12:13 GMT</pubDate>
            <atom:updated>2021-06-24T19:12:13.850Z</atom:updated>
            <content:encoded><![CDATA[<h3>Simple Flutter rating bar | DIY: NoPlugin | Flutter Beginner</h3><p>Hy, It&#39;s my First article in DIY (Do It Yourself), What we going to archive is the Flutter rating bar without using any library.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4owUJrl-9g2s93Km" /><figcaption>Photo by <a href="https://unsplash.com/@mymyc?utm_source=medium&amp;utm_medium=referral">Myrlene NUMA</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Take scissors and paper, ahh Just kidding…</p><p>Let&#39;s see the code.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5a0d619e281e49c13ecd32ef2570ab56/href">https://medium.com/media/5a0d619e281e49c13ecd32ef2570ab56/href</a></iframe><p>Simple as that,</p><p><strong>H</strong>ere comes DIY part:</p><ol><li>First, we generate 5 widgets using List&lt;XXX&gt;.generate method.</li><li>Inside each Widget, we configure two-section firstly <strong>Show Rating only </strong>and <strong>Modifying</strong> <strong>Rating widget.</strong></li><li>For show rating, There are two case have to see<br>(i) <strong>Icon</strong>(Full, Half, empty) <br>(ii) <strong>Color</strong>(Filled, Empty color)</li></ol><blockquote>rating.ceil() == (index + 1) &amp;&amp; rating != rating.<strong>ceil</strong>() ? <em>Icons</em><strong><em>.star_half_outlined</em> </strong>:<strong> </strong><em>Icons</em><strong><em>.star</em></strong></blockquote><p>Let&#39;s take an example as Rating 3.5,</p><p>When the rating[3.5] is equal to <strong>index +1 [</strong>index start from 0<strong>] </strong>and <strong>rating.ceil() [</strong>3.5 ceil =&gt; 4<strong>]</strong> is not equal to the rating[3.5] then we show <strong>Full star </strong>or else <strong>Half star</strong>.</p><p>&amp; Same time for colour</p><p>rating[3.5] &gt; index if true then its Fill Colored or Empty Colored.</p><p>That&#39;s all, Put all index value from 0 to 5 we can get a working rating bar.</p><p>For <strong>choosable rating</strong> just update the <strong>index</strong> in <strong>rating</strong> whenever a click happen using setState({}) method ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56a043283d5e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MVVM Android to Flutter | For Android Developer]]></title>
            <link>https://medium.com/geekculture/mvvm-android-to-flutter-for-android-developer-b1fe82d6af60?source=rss-6a5e42cee40f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1fe82d6af60</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[geek]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[mvvm]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Arul mani]]></dc:creator>
            <pubDate>Fri, 07 May 2021 16:01:46 GMT</pubDate>
            <atom:updated>2021-05-09T11:37:56.968Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi all,</p><p>Me my self an android developer and we know that most of the developer usually work on an android platform with <strong>architecture</strong> for better code maintenance and reliability. Mostly used architectures are MVVM, MVI or anything done by our own :P.</p><p>So here what we gonna see much about MVVM in flutter which is helpful for an android developer who wanna do code in Flutter.</p><p>Let&#39;s see,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XDRSC8jVtm8qdWIA" /><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><p>Before start, those who have a question “what the heck is MVVM?“ let us see the answer.</p><blockquote>The Model-View-ViewModel <strong>Pattern</strong></blockquote><blockquote>The main players in the <strong>MVVM pattern</strong> are: The <strong>View</strong> — that informs the ViewModel about the user’s actions. The <a href="https://medium.com/upday-devs/android-architecture-patterns-part-3-model-view-viewmodel-e7eeee76b73b"><strong>ViewModel</strong></a> — exposes streams of data relevant to the View. The Data<strong>Model</strong> — abstracts the data source. The ViewModel works with the DataModel to get and save the data.</blockquote><p><a href="https://medium.com/upday-devs/android-architecture-patterns-part-3-model-view-viewmodel-e7eeee76b73b">Android Architecture Patterns Part 3:
Model-View-ViewModel</a></p><p>To be simple it is just a way of coding which follows the SOLID principle, (a standard).</p><p>View — Responsible for handle UI events</p><p>ViewModel —ViewModel — Responsibility is to process UI events and send a callback to <strong>VIEW</strong> when the process complete.</p><p>DataModel — ViewModel uses Data Model to fetch data from network/storage and send it to <strong>ViewModel</strong>.</p><p>The theory part ends here, Let’s <strong><em>dig</em></strong> into <strong>F</strong>lutter</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BDBNvyOMRzvM3ju-" /><figcaption>Photo by <a href="https://unsplash.com/@yellowteapot?utm_source=medium&amp;utm_medium=referral">Meghan Holmes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Flutter is Google’s UI toolkit for building beautiful, natively compiled applications for mobile, web, and desktop from a single codebase.</p><p>Yup, it’s elegant.</p><h3>View</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fcfc5c17d942e82432a9504abb81ebfd/href">https://medium.com/media/fcfc5c17d942e82432a9504abb81ebfd/href</a></iframe><h3>ViewModel</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c6aeedc8907954cfb9939baa147a7673/href">https://medium.com/media/c6aeedc8907954cfb9939baa147a7673/href</a></iframe><h3>Model — Repository</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e650466ac8ed31237ebc65a247b9d3a2/href">https://medium.com/media/e650466ac8ed31237ebc65a247b9d3a2/href</a></iframe><p>The coding part is done here. Don&#39;t worry about the implementation let&#39;s see the usages.</p><p>By the above example, you can see we use,</p><h3><strong>1. Change Notifier</strong></h3><blockquote><strong>ChangeNotifier</strong> is a simple class included in the <strong>Flutter</strong> SDK which provides change notification to its listeners. In other words, if something is a <strong>ChangeNotifier</strong> , you can subscribe to its changes.</blockquote><h3><strong>2. Provider</strong></h3><blockquote>A wrapper around <a href="https://api.flutter.dev/flutter/widgets/InheritedWidget-class.html">InheritedWidget</a> to make them easier to use and more reusable.</blockquote><blockquote>1. simplified allocation/disposal of resources</blockquote><blockquote>2. lazy-loading</blockquote><blockquote>3. a largely reduced boilerplate over making a new class every time</blockquote><p>From an android developer perspective,</p><p>The <strong>Change Notifier</strong> is More like <strong>LiveData, </strong>But it subscribe the data(i.e welcomeText, …etc) in view and when <strong>notifyListener() </strong>calls it will trigger all data events if it has changes and intimate the UI for changes.</p><p>And</p><p>The Provider is just a way of using inherited widget i.e we can use the <strong><em>instance of the object</em></strong> whenever we need it by just simply calling “<strong>Provider.Of()” </strong>method. So it&#39;s more like a miniature of <strong>DI</strong>.</p><p>Here, we use an external library called provider.</p><p><a href="https://pub.dev/packages/provider">provider | Flutter package</a></p><p>It&#39;s beautiful indeed…</p><p>Now see the above Example,</p><ol><li>The <a href="https://pub.dev/packages/provider"><strong>View</strong></a> gets the instance of ViewModel from the provider</li><li>View bind the data using a variable inside <strong>ViewModel</strong>.</li><li>When the provider create an instance ViewModel call Repository(<strong>Model</strong>) to get the data.</li><li>Finnaly, ViewModel <em>Trigger</em> assign the value to the variable(welcomeText) and trigger notifyListener() help of <em>ChangeNotifier</em>.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FJLtQeoVXD5yKI%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FJLtQeoVXD5yKI%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FJLtQeoVXD5yKI%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="327" frameborder="0" scrolling="no"><a href="https://medium.com/media/81b51dc50d50715a6041cfd345157980/href">https://medium.com/media/81b51dc50d50715a6041cfd345157980/href</a></iframe><p>Understanding Flutter Mvvm from the android developer. ;)</p><p>Any questions or improvement or suggestion feel free to comment below.</p><p>It&#39;s a free world B)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1fe82d6af60" width="1" height="1" alt=""><hr><p><a href="https://medium.com/geekculture/mvvm-android-to-flutter-for-android-developer-b1fe82d6af60">MVVM Android to Flutter | For Android Developer</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>
    </channel>
</rss>