BUILDING
Cross-platform product workflows
Keeping web and mobile in one stack and one team, while treating backend as a separate system with a clear contract.
reactcross-platformproduct
Back to the WorkbenchKeeping web and mobile in one stack and one team, while treating backend as a separate system with a clear contract.
Running one product across web, mobile, and an administration interface becomes much easier when these clients are treated as one stack, not as separate products.
For me, monorepo fits this model well. Web, mobile, and admin can live close to each other and share domain logic, types, validation, API clients, and other code that should behave the same everywhere. Platform-specific UI still stays separate where it needs to.
Important part is not sharing everything. It is having one source for things that should not be implemented three times.
I also like the idea of web and mobile being owned by the same team. When stack and domain are similar, splitting ownership by platform creates extra boundaries without much benefit.
One team can move between web, mobile, and admin work, review the same shared code, and keep product behavior more consistent. Monorepo supports this because changes to shared logic and platform code can happen together.
Backend is different. In this setup it is owned by another in-house team and lives in another repository. I would not try to bring it into the frontend monorepo only to make repository structure look unified.
The important boundary is API contract. Frontend can share everything internally, while backend stays an external dependency with its own release cycle and ownership.
This makes me think about architecture in two levels: keep related frontend platforms close, but keep clear boundaries between teams that own different systems.