You have three options.
Optimise for user experience (go native)
Optimise for cost (whatever the cheapest developers, or a cross platform solution, like phonegap/pwa/react native)
Optimise for developer experience (use whatever your developers know, maybe native, maybe react native)
In my personal opinion, always optimise for user experience.
Shared code should be in the backend, not in your mobile app. Your mobile app (ignoring camera filters & games, as they should use an engine; unity etc) should just be a JSON viewer, with a small bit of data entry.
80-90% of your efforts should be on UI and user experience, but obviously architecture requirements scales up with the team size.
Anything else is over-engineering, generally.
The amount of leads I get in for mobile apps, that eventually transpire to the client not knowing the app was built in react native, because they heard “native” and assumed Swift/Kotlin, is increasing by the day.
They can’t find enough good developers that know react native, and they don’t have the funds to rewrite.
They’re stuck.
Obviously I, as a native developer, only hear the horror stories from these experiences and not the times it works out.
But in the last 2-3 years, it has killed 2 startups that I know of, and cost 3 a lot of money to rewrite (two of them made that decision before they contacted me, one after they spoke to me, and they were shocked to find out that they didn’t have a Swift app).
I am now having to rescue more clients from react native, than from clients that outsourced to the cheapest agency on Fiverr. Wild!
Side note: why has every app got to expand until it adds messaging? Let a calculator be a calculator, it doesn’t need venture capital and network effects to sell.