The fundamental decision.
WHAT NATIVE MEANS
Separate applications, each written in that platform's language and tools.
What it provides: best performance, full platform access, correct platform conventions, immediate access to new features.
What it costs: two codebases, two skill sets, two sets of work for every change.
WHAT CROSS-PLATFORM MEANS
One codebase producing applications for both.
What it provides: one team, one codebase, faster delivery, consistent behaviour.
What it costs: larger applications, some platform limitations, dependence on a framework.
WHAT TO ASK FIRST
Does this need to be an application at all?
WHY
Many applications are websites with an icon, and a web application avoids stores, downloads and approval entirely.
WHAT TO CHOOSE NATIVE FOR
Heavy device integration Performance-critical graphics or processing Applications where platform conventions matter greatly
WHAT TO CHOOSE CROSS-PLATFORM FOR
Limited resources and both platforms required Content and form-driven applications Products where speed to market matters
WHAT TO WEIGH LOCALLY
Download size, which is a genuine barrier on metered connections.
