Three technology options for building native Android apps
summary
Builds a VG.no-backed newspaper article viewer three ways: native Android (Android Studio, Java/Kotlin, Retrofit, RecyclerView); React Native (Node, NPM, JavaScriptCore, hot reload, remote JS updates) and Xamarin (Visual Studio, Mono, C#, RestSharp/Newtonsoft). Demo parses production JSON into dynamic component lists, ships a working Android APK; React Native repo claims 100% code reuse (React Native demo repo) while Xamarin sample measures 33% code reuse (Xamarin example). Notes: Gradle builds are slow, Xamarin/MSBuild is faster, React Native adds ~8MB and ~3000 methods, and RN can hold screens in memory risking OOM with many images.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 8:48Pure Android baseline
- 14:54React Native overview
- 23:37React Native use cases
- 36:35Xamarin overview
- 41:35Xamarin use cases
- 47:39Comparison and conclusion
related talks
27mBuilding high quality mobile apps with React Native
01h 05mBuilding Native Android Apps using React Native
23mTeam × Technology
13mUsing multiplatform frameworks to target Android in emerging markets.
36mWhat I learnt by building the exact same app in Kotlin (Native Android), Nativescript and Flutter
31mUsing React Native to ship fast and navigate performance improvements
31mFrom React to Native
31mThe performance myths of React Native