Every mobile project I have seen go sideways had the same origin story: the framework was chosen in the first meeting, before anyone had written down what the app actually needed to do. Someone had a favourite stack, someone else had read a benchmark thread, and the decision was locked in before the requirements existed.
This post is the opposite approach. It treats "native or cross-platform?" as an engineering decision that falls out of your requirements, not a preference you defend. It is aimed at developers and technical founders planning an app that has to live on both iOS and Android, with a bias toward marketplace and transactional products where payments, real-time state and integrations dominate the work.
The short version, borrowed from the original Journeyhorizon guide: the technology should follow the product requirements, not the other way around.
Step 0: Confirm you actually need both platforms on day one
Before comparing stacks, check the premise.β¦