Mobile briefing / 6 references
A deliberately short set of useful references for Android, Kotlin Multiplatform and iOS. Each note explains what the source covers and why it is worth an engineer’s time.
2 essential references
Android
A practical baseline for layered Android systems, unidirectional data flow, state holders and clear module boundaries.
Use it to align a team on responsibilities and dependency direction before debating frameworks.
Android
Explains how critical user journeys can be precompiled so startup, navigation and scrolling perform well from first launch.
A useful bridge between performance measurement, release engineering and user-visible outcomes.
2 essential references
Kotlin Multiplatform
Shows how common source sets, hierarchical sharing and expect/actual declarations create deliberate cross-platform boundaries.
Read this before deciding what should be shared and what should remain native.
Kotlin Multiplatform
A concrete migration path for moving reusable business logic into a shared module while connecting it to an iOS application.
Useful for incremental adoption where a rewrite would create more risk than value.
2 essential references
iOS & SwiftUI
Connects SwiftUI views to observable model data while preserving a clear separation between presentation and application state.
A concise reference for keeping state ownership legible as SwiftUI screens grow.
iOS & SwiftUI
Uses Instruments to identify expensive view updates, excessive dependencies and layout work that causes hitches.
Turns vague UI-performance concerns into a repeatable measurement and diagnosis workflow.