CASE№ 013·Kotlin MultiplatformArchitectureDelivery

Shared code had to work for iOS, and for the people shipping it.

I helped a large company adapt its shared-code architecture for both mobile platforms, CI, releases, and everyday development, and recommended how to expand it.

Product typeMobile app at a large company
Context checkedKotlin Multiplatform · CI · Release process
SurfaceiOS + Android
01 · The starting point

The shared-code work had started from Android.

At a large company, an Android developer had started the move toward shared mobile code. The initial approach did not yet account for the limitations on iOS.

02 · My contribution

Shape an architecture that works for both platforms.

I worked with the developer to prepare a better architecture for iOS and Android. I brought the iOS constraints into the decisions and helped make the shared-code approach work for both platforms.

03 · Beyond the code

Make it fit the way the team ships.

The architecture also needed to work with CI, the release process, and everyday development. I helped shape the approach around those requirements so regular developers could work with it.

04 · The next steps

Decide what to do first and when to expand.

I recommended the next steps: what the team should tackle first and when the solution could be expanded. My contribution here was architecture and migration guidance, rather than carrying out the full migration.

Have a related problem?

Kotlin Multiplatform migration →
Let’s talk

Bring me
the problem.

An app that needs building. A migration that needs someone to own it. Numbers that don’t make sense. A product decision your team can’t resolve. Tell me what’s happening. I’ll tell you whether I’m the right person, how I’d approach it, and what the work would cost.

Email Alex ↗alex@x91tech.com
You bring the context. I take the work seriously.
Not sure what you’d get? See sample reports →