Start with your users
Use evidence about the target audience rather than assuming the platforms have equal importance. A limited first release can help validate demand if the excluded audience is clearly understood. An internal app may have a known device fleet. Document the platform and operating-system support expected at launch.
Compare native and shared development
Separate native apps provide platform-specific implementation, while a shared framework can reduce duplicated product work. Integration and quality assurance still need attention on each platform. Prototype specialised hardware or performance requirements before choosing the architecture. The recommendation should follow the product, not only the team’s preferred framework.
Plan both release pipelines
Store assets, review requirements, device testing and monitoring remain part of delivery. Keep account ownership with the organisation running the product. Include platform updates in maintenance planning, and make the supported device range visible in the scope. A shared codebase does not remove the need to validate the actual user experience on both systems.