You want to share business logic across iOS and Android.
The first question is what belongs in shared code and how the existing apps will use it. I work through the boundaries, platform dependencies, and migration order before moving implementation.
Development / Kotlin Multiplatform
Share the code. Keep both platforms working.
I help teams migrate iOS and Android business logic to Kotlin Multiplatform. I define the architecture, carry out the migration, and work through the iOS integration, CI, and release process with the people shipping the apps.
When to bring me in
A concrete problem to work through.
The shared code works on Android, but iOS is difficult.
I bring the iOS constraints into the architecture: how the shared layer fits the native app, how developers build and debug it, and what has to work in CI and releases.
You are deciding whether to share UI as well.
Sharing business logic and sharing UI are separate decisions. I help define the next stage around the existing product and team, rather than making a full UI rewrite a condition of sharing code.
Relevant work
The experience behind this work.
I’m Alex Severianov, founder of X91 Tech. These cases describe my own contribution in existing product teams.
Explore →
Architecture and business-logic migration
I defined the architecture and migrated business logic for iOS and Android to Kotlin Multiplatform, then started moving UI into shared Compose code.
Explore →Architecture and delivery guidance
I helped a large company adapt its shared-code approach for iOS, CI, releases, and everyday development, and recommended the next steps.
Working together
From the starting point to the implementation.
Review the starting point
We look at the existing iOS and Android architecture, the code you want to share, platform-specific behavior, and the way your team builds and releases.
Agree the boundaries and sequence
I define the shared layer and its integration with both apps, identify migration risks, and agree a first area that can be implemented and checked.
Implement and make it usable
Depending on the agreed scope, I migrate the logic, integrate it into the apps, add appropriate checks, and work through CI and the everyday development workflow.
What you get
An agreed architecture and migration sequence, implemented changes for the scoped area, and the integration and delivery work needed to use those changes. We agree the scope and price before paid work; the size of the existing apps determines the work involved.
Before we start
Questions about the work.
Can you implement the migration, or only advise?
Both are possible. In one engagement I defined the architecture and migrated the business logic. In another I helped shape the architecture and delivery approach. We agree which responsibility you need me to take.
Do we need to replace our native UI?
No. A migration can focus on shared business logic while retaining native UI. Whether to share UI with Compose is a separate decision based on the product and team.
What should I send first?
Tell me how the apps are built, what you want to share, what has already been tried, and where the team is stuck. We can start with that context before arranging code access.
Let’s talkBring me
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 ↗[email protected]You bring the context. I take the work seriously.
Not sure what you’d get? See sample reports →