Native, cross-platform or web.
NATIVE
Separate applications per platform, in each platform's language.
What it provides: best performance, full platform access, correct conventions.
What it costs: two codebases and two skill sets.
CROSS-PLATFORM FRAMEWORKS
One codebase producing applications for both.
What they provide: one team, one codebase, faster delivery.
What they cost: larger applications, some platform limitations, framework dependence.
WEB APPLICATIONS
A website, possibly installable.
What they provide: one codebase, no store approval, instant updates, no download.
What they cost: limited device access, and no store presence.
WHAT TO ASK
Does this need to be an application at all?
WHY
Many applications are websites with an icon, and a web application serves better.
WHAT TO WEIGH LOCALLY
Download size, which is a real barrier on metered connections Device capability, since many users have modest devices Whether users will install anything at all
WHAT TO CONSIDER
An installable web application, which costs no download from a store.
WHAT TO DECIDE FIRST
The requirement, not the technology.
