Doppl Code Sharing

on YouTube ↗43m

" summary

Doppl claims to let teams share business logic by converting Java/Kotlin to Objective‑C using a J2ObjC-based build tool plus a Gradle plugin and tested library set (Room, Retrofit, RxJava, Dagger, etc.). Android stays native — Android side 100% native — while iOS links generated Objective‑C into native Swift UIs. A real droidcon app prototype exists, a technical preview is shipping, runtime increases on iOS sit around adds 10–15MB to iOS app, and Xcode integration and memory-cycle handling are the main rough edges.

AI-written summary · about

" chapters (12)

1. 0:00Start
2. 3:31Android Centric Code Sharing
3. 11:32Shared Native Interface
4. 15:21Business Case
5. 19:03Which Platform Takes Longer To Build for
6. 21:55Sharing Code Is Optional
7. 25:17Sharing Is Optional
8. 27:14Ios
9. 28:21Droidcon Nyc Ios
10. 30:14Technical Preview
11. 32:57Memory Cycles
12. 39:00Fonts

" related talks

• 34mDoppl Code SharingKevin Galligan · droidcon San Francisco 2017
• 39mAnd That, Folks, is How We Shared Code Between Android, iOS and the BackendMarco Gomiero · droidcon Italy 2021
• 34mCode Sharing is caring - Cross-Plattform DevelopmentTobias Heine, Said Tahsin Dane · droidcon Berlin 2018
• 52mBuilding apps using Kotlin NativeJeremy Rempel · droidcon NYC 2019
• 43mThe Triumphs and Tribulations of Kotlin-Native in PracticeEllen Shapiro · droidcon Italy 2019
• 33mThe (not so) hidden cost of sharing code between iOS and AndroidEyal Guthmann · droidcon SF 2019
• 22mIntegrate Multiple Kotlin/Native Libraries into Your Android/iOS Apps, Vincent Nicolle Coyote SystemVincent Nicolle · Android Makers 2020
• 48mKotlin for Android, iOS & the mobile webSalomon Brys · Mobilization 8