Bhumil Soni

AI is making native mobile development cheaper, weakening one of the biggest reasons teams chose cross-platform in the first place: budget. With early signs of teams moving back toward native as that cost equation changes, why would cross-platform still be relevant when writing native code is no longer the expensive part? That changes the question from whether cross-platform still has value to what kind of cross-platform architecture makes sense if native migration is part of the future. Flutter, React Native, and Compose Multiplatform all solve the same starting problem differently, but those differences matter much more when the framework itself is not assumed to be permanent, since each comes with a different exit tax. At the centre of the talk is the mental model adopted across our production apps built with Compose Multiplatform: build cross-platform apps as if migration to native is inevitable. That assumption has shaped the architecture from day one to help us move from shared UI to native UI more easily, along with providing a cleaner roadmap toward fully native apps. The result is a migration-first approach of thinking about cross-platform development and selecting a model that leaves the right to change your mind open without paying too much exit tax when the product demands it.

Track

Builder track

Format

talk

Target level

Intermediate

Date

Saturday, 17 October 2026

Venue

QUT Gardens Point P Block, Brisbane City