#DCBerlin18 Mobile Oriented Architecture
summary
Argues that sharing native business logic, not UI, is the safest path: uses Kotlin multiplatform and earlier Doppel (J2ObjC) to compile shared code to native iOS/Android with smooth native interop. Describes building two fully functional ordering apps for the Pytops Pizza Hut campaign in about a month by keeping UIs thin and sharing core architecture; it ships and works. Notes pitfalls of React Native’s bridge and extra environment, and announces SQL/DB tooling coming for Kotlin multiplatform.
AI-written summary · about
chapters (31)
- 0:00Introduction and speaker background
- 1:24What is Mobile Oriented Architecture?
- 2:50Mobile should lead development
- 5:14Crossplatform shifts in 2018
- 6:19Tech trends over the past decade
- 8:10Risk and tech decisions in enterprise
- 9:12Code sharing on mobile first
- 10:17Android and iOS similarities
- 11:42J2ObjC and Doppel for crossplatform
- 12:03Pizza Hut case study with Doppel
- 13:07Why Java and Kotlin are good choices
- 13:48Airbnb dropping React Native
- 15:55Developer community response to solutions
- 17:21Enterprise challenges with crossplatform
- 18:22Kotlin Multiplatform and SQLDelight
- 19:03Kotlin Multiplatform future outlook
- 20:08Web vs hybrid apps explained
- 21:13Web progress and PWA support
- 22:19Mobile and web architecture challenges
- 23:20Kotlin and WebAssembly potential
- 24:03Future of JavaScript and web standards
- 25:51Mobile influence on web standards
- 26:13Two native apps vs one crossplatform app
- 27:58Product iteration and development costs
- 29:01Product differentiation and tech choices
- 30:04Pizza Hut case study with Flutter
- 31:48Flutter risks and native advantages
- 32:08Retraining backend devs for mobile
- 33:315G and server logic misconceptions
- 34:33Summary and key takeaways
- 35:17Q&A and closing remarks
