---
title: "Native or cross-platform? Three questions decide it"
updated: "2026-11-17"
url: "https://www.etheon.com/company/news/native-or-cross-platform"
authors: "Etheon"
published: "2026-11-17"
type: "news"
---

# Native or cross-platform? Three questions decide it

Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through.

Deep device features point to native; one team and a close store date point to cross-platform; otherwise either fits, and we talk it through. Here are the three questions, what each answer means, and what you receive either way.

## What are the three questions?

1. Does the app need deep device features, like background tasks, Bluetooth or full camera control?
2. Do you want one team for iOS, Android and the web?
3. Is the store launch date fixed and close?

## What do the answers point to?

| Your answer | What fits |
| --- | --- |
| The app needs deep device features | Native: two apps, each built to its platform, with the device features you need. |
| You want one team for iOS, Android and the web, or the store date is fixed and close | Cross-platform: one code base, with native modules where the device needs them. |
| Neither points one way | Either fits. Both would serve you; we talk it through and choose with you. |

## What does native give you?

Two apps, each built to its platform's guidelines. Native development builds a separate app for iOS and for Android, each with its platform's own tools and design rules. It gives you the platform's full features and the best performance, at the cost of two code bases to maintain.

- How we build it: each app follows its platform's own design rules, and is built and tested on real devices for that platform.
- What you receive: two apps and their source code in your repository, and a release build for each store.

## What does cross-platform give you?

One code base for iOS, Android and the web. One team ships to both stores at once, with native modules wherever the app needs the device's own features: one team, one release train.

- How we build it: the code is shared across iOS, Android and the web, and goes native where the app needs the device.
- What you receive: one code base and its source in your repository, and a release build for each store.

Kuest AI, an AI tutor Etheon built for a client, is a cross-platform app. Its screens are on our [Mobile page](https://www.etheon.com/services/mobile#apps).

## What if we already have an app?

Then we start by checking it, on both platforms, check by check, and fix what the checks find, highest risk first.

## How does the app reach the stores?

In stages, each one reversible:

1. Build: every change built and tested on both platforms.
2. Internal testing: your team installs it before anyone else.
3. Store review: we prepare the listing and answer the reviewers.
4. Phased release: a small share of users first.
5. Updates: fixes without a store release, where the stores allow it.

We prepare the store listings, submit each release and answer the stores' reviewers, under your own developer accounts.

The chooser is on our [Mobile page](https://www.etheon.com/services/mobile#platform), with [native](https://www.etheon.com/services/mobile#ios-android), [cross-platform](https://www.etheon.com/services/mobile#cross-platform) and [modernization](https://www.etheon.com/services/mobile#modernization) side by side. Tell us your use case and timeline. We reply within one business day.