<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Mobile - Discussions				            </title>
            <link>https://iteventsbook.com/discussions/tech-mobile/</link>
            <description>Talk with other IT professionals about the technologies you work with.</description>
            <language>en-US</language>
            <lastBuildDate>Mon, 28 Sep 2026 02:54:34 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Kotlin Multiplatform vs React Native for native iOS and Android UI</title>
                        <link>https://iteventsbook.com/discussions/tech-mobile/kotlin-multiplatform-vs-react-native/</link>
                        <pubDate>Sun, 06 Sep 2026 17:23:01 +0000</pubDate>
                        <description><![CDATA[We want to share networking, models and business rules but keep SwiftUI on iOS and Compose on Android. Kotlin Multiplatform sounds perfect on paper. React Native would share more, but the de...]]></description>
                        <content:encoded><![CDATA[<p>We want to share networking, models and business rules but keep SwiftUI on iOS and Compose on Android. Kotlin Multiplatform sounds perfect on paper. React Native would share more, but the designers care about platform behavior. Anyone running KMP in production with a mixed iOS and Android team?</p>]]></content:encoded>
						                            <category domain="https://iteventsbook.com/discussions/tech-mobile/">Mobile</category>                        <dc:creator>swift_side</dc:creator>
                        <guid isPermaLink="true">https://iteventsbook.com/discussions/tech-mobile/kotlin-multiplatform-vs-react-native/</guid>
                    </item>
				                    <item>
                        <title>On device LLM for mobile apps, privacy win or battery killer?</title>
                        <link>https://iteventsbook.com/discussions/tech-mobile/on-device-llm-mobile-app/</link>
                        <pubDate>Wed, 02 Sep 2026 20:48:30 +0000</pubDate>
                        <description><![CDATA[product wants text summarization to run on device so user notes never leave the phone, using Apple&#039;s Foundation Models framework on ios and Gemini Nano through AICore on android. The model f...]]></description>
                        <content:encoded><![CDATA[<p>product wants text summarization to run on device so user notes never leave the phone, using Apple's Foundation Models framework on ios and Gemini Nano through AICore on android. The model fits on newer devices, but startup time, memory and battery are rough on older ones. How are apps deciding when to run locally and when to fall back to cloud?</p>]]></content:encoded>
						                            <category domain="https://iteventsbook.com/discussions/tech-mobile/">Mobile</category>                        <dc:creator>terminal_person</dc:creator>
                        <guid isPermaLink="true">https://iteventsbook.com/discussions/tech-mobile/on-device-llm-mobile-app/</guid>
                    </item>
				                    <item>
                        <title>SwiftUI vs Jetpack Compose state management, why are state bugs still hard?</title>
                        <link>https://iteventsbook.com/discussions/tech-mobile/swiftui-vs-jetpack-compose-state-management/</link>
                        <pubDate>Wed, 02 Sep 2026 06:52:52 +0000</pubDate>
                        <description><![CDATA[Both frameworks are now the default choice on our teams, but bugs around navigation, background restore and duplicated events still eat time. The UI code looks simple until state is spread a...]]></description>
                        <content:encoded><![CDATA[<p>Both frameworks are now the default choice on our teams, but bugs around navigation, background restore and duplicated events still eat time. The UI code looks simple until state is spread across views, view models and persistence. What rules have actually reduced this?</p>]]></content:encoded>
						                            <category domain="https://iteventsbook.com/discussions/tech-mobile/">Mobile</category>                        <dc:creator>compose_casey</dc:creator>
                        <guid isPermaLink="true">https://iteventsbook.com/discussions/tech-mobile/swiftui-vs-jetpack-compose-state-management/</guid>
                    </item>
							        </channel>
        </rss>
		