I can speak to some of the pros and cons of two codebases for ios and android that share a common api service on a semi-large production app with 6k to 10k cons

I can speak to some of the pros and cons of two codebases for ios and android that share a common api service on a semi-large production app with 6k to 10k constant users. Pros: - Native performance and API exposure for both, without a wrapper/glue layer. That's it. Cons: Feature implementation complexity and nuanced differences that leads to one version having a bug the other doesn't, or they both have the bug but for different reasons. - dependency updates, testing workflows, build and deployment tool chains, actually all tooling - is different for both. - syncing development between teams is a nightmare. - delivery time on releases becomes two deadlines, and stakeholders don't understand why both versions can't always be complete on the same exact day. - ui implementation, and organization of graphical assets are just plane different. - device support, and user support in general, must account for basically any supported ios or android vendor hardware/os