Consider capabilities and experience
Native development provides a direct path to platform-specific APIs and conventions. Cross-platform frameworks share substantial product work while still allowing specialised integration. List the hardware, background behaviour, offline use and performance requirements that may influence the choice. Validate uncertain features with a focused prototype.
Compare maintainability and team fit
A shared codebase can reduce duplicated changes, but dependencies and native modules still need maintenance. Separate apps may require more coordination to keep behaviour aligned. Consider the team available now and the people likely to maintain the product later. Document platform-specific decisions and build procedures.
Make the decision reviewable
Ask the team to connect its recommendation to specific requirements, risks and operating costs. Avoid claiming that one approach is always faster or cheaper. Include testing on both platforms and a realistic release plan. A good architecture choice leaves the product understandable and capable of evolving as user needs become clearer.