Tag: Compose Multiplatform
All the articles with the tag "Compose Multiplatform".
-
Torque Spec: Shared Form State and Validation in KMP
The spec says 120 Nm and you already knew that. Knowing the number was never the hard part. My validation rules were already shared. The sixty lines of state around them were not.
-
Lights Out: Automatic Skeleton Loading in Compose Multiplatform
Five ligths go out and every car reacts to the same signal at once. My shimmer effect wasn't doing that. Every skeleton on screen was running its own private clock.
-
Same Car, Every Time: Deterministic Feature Module Generation in KMP
AI generation adapts to anything you ask. A bash script adapts to nothing. After a few months of scaffolding KMP feature modules both ways, I know which one I trust.
-
Warm Tyres: Image Loading and Caching in Compose Multiplatform with Coil 3
Tyre warmers keep rubber at temperature so the car has grip the instant it leaves the box. Coil 3's memory and disk cache do the same for images — and the same code now runs on Android and iOS from commonMain.
-
Through the Lens: Barcode Scanning in Compose Multiplatform
expect/actual isn't just for business logic. Here's how to build a shared barcode scanner Composable that reads through any platform's lens.
-
The Pit Crew: Advanced Ktor Client Configuration for KMP
The pit crew doesn't wait to be asked. They intercept the car, do their work, and the driver rejoins the race. Ktor plugins work the same way: auth, logging, and retry all happen before your business logic sees a thing.
-
KMP Splash: How I Stopped Opening Xcode for Splash Screens
The pit crew was always there. I just had to build it: a Gradle plugin that automates iOS and Android splash screen setup from a single config block.
-
Drop the Clutch: Three Metro DI Patterns Every KMP Developer Should Know
Metro drops the clutch on runtime DI errors. Three patterns in a real KMP app: binding contributions, platform graphs, and child scopes.
-
Clean Lap: UI Testing in Compose Multiplatform
Before the car hits the grid, telemetry confirms every sector. Before your UI ships, runComposeUiTest confirms every composable.
-
Smooth Handoff
Navigation 3 supports shared element transitions. It always did. LocalNavAnimatedContentScope was the piece the docs never mentioned.