---
title: "Mobile"
updated: "2026-11-16"
url: "https://www.etheon.com/services/mobile"
---

# Mobile app development

Mobile app development for iOS and Android. We build native and cross-platform apps, and modernize the ones you have.

- [Kuest AI, an AI tutor that teaches step by step](https://www.etheon.com/work/kuest-ai) · Cross-platform · The teaching board, solving an equation step by step.
- [Kuest AI, an AI tutor that teaches step by step](https://www.etheon.com/work/kuest-ai) · Cross-platform · A quiz that asks to put four numbers in order.
- [Kuest AI, an AI tutor that teaches step by step](https://www.etheon.com/work/kuest-ai) · Cross-platform · An exam plan for a cell biology unit test.

## Native or cross-platform.

Three questions decide it.

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

### Native.

Two apps, each built to its platform's guidelines.

- The platform's full features
- The best performance
- Two code bases to run

### Cross-platform.

One code base for iOS, Android and the web.

- Both stores at once
- Native modules where needed
- One team, one release train

Answer the three questions.

- Native fits. Two apps, each built to its platform, with the device features you need.
- Cross-platform fits. One code base, native modules where the device needs them.
- Either fits. Both would serve you; we talk it through and choose with you.

[Contact Us](https://www.etheon.com/services/mobile?start=1&service=mobile&tab=platform)

### iOS and Android. Native apps, each built to its platform.

#### What it is

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.

#### What we do

- Two apps, each built to its platform's guidelines.
- The platform's full features.
- Testing on real devices for each platform.

#### How we do it

1. Design for each platform: Each app follows its platform's own design rules.
2. Build and test: Built and tested on real devices for each platform.

#### Questions

**Native or cross-platform: which do we need?**

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.

#### What you get

- Two apps and their source code in your repository
- A release build for each store

#### Stack and tools

- Native iOS tooling
- Native Android tooling
- Device testing
- Crash reporting

#### Related

- [Cross-platform](https://www.etheon.com/services/mobile?detail=cross-platform#cross-platform)

### Cross-platform. One code base for iOS, Android and the web.

#### What it is

Cross-platform development builds one code base that runs on 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.

#### What we do

- Both stores at once.
- Native modules where needed.
- One team, one release train.

#### How we do it

1. Share the code: One code base for iOS, Android and the web.
2. Go native where needed: Native modules where the app needs the device.

#### Questions

**Native or cross-platform: which do we need?**

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.

#### What you get

- One code base and its source in your repository
- A release build for each store

#### Stack and tools

- Cross-platform frameworks
- Native modules
- Device testing
- Crash reporting

#### Related

- [iOS and Android](https://www.etheon.com/services/mobile?detail=ios-android#ios-android)
- [Web apps](https://www.etheon.com/services/web?detail=web-apps#web-apps)

## Modernizing the app you have.

What we check, and what you receive.

### Stability

- We check: Crashes, and the flows that lead to them.
- You receive: A ranked list of fixes.

### OS and SDK versions

- We check: The system versions and toolkits the app is built against.
- You receive: An upgrade plan.

### Accessibility

- We check: Screen readers, text size and contrast on both platforms.
- You receive: An issue list against WCAG 2.2 AA.

### Speed and battery

- We check: Start-up time, heavy screens and background work.
- You receive: A baseline to measure against.

### Store policies

- We check: What the stores require now that the app may miss.
- You receive: What to change before the next release.

### Mobile modernization. The app you have, made stable, current and accessible.

#### What it is

Mobile modernization makes the app you already have stable, current and accessible. We check its crashes, its system and toolkit versions, its accessibility, its speed and battery use, and the store policies it must meet, then fix what the checks find, highest risk first.

#### What we do

- Stability: Crashes, and the flows that lead to them.
- OS and SDK versions: The system versions and toolkits the app is built against.
- Accessibility: Screen readers, text size and contrast on both platforms.
- Speed and battery: Start-up time, heavy screens and background work.
- Store policies: What the stores require now that the app may miss.

#### How we do it

1. Check: The app checked on both platforms, check by check.
2. Fix: The fixes made in the order of the list, highest risk first.

#### What you get

- Stability: A ranked list of fixes.
- OS and SDK versions: An upgrade plan.
- Accessibility: An issue list against WCAG 2.2 AA.
- Speed and battery: A baseline to measure against.
- Store policies: What to change before the next release.

#### Stack and tools

- Crash reporting
- Accessibility checkers
- Performance profiling
- Store policy checks

#### Related

- [Software modernization](https://www.etheon.com/services/software?detail=modernization#modernization)

## From build to the stores.

Released 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. (a few, more, everyone)
5. Updates: Fixes without a store release, where the stores allow it.

### Store release. Submitted, reviewed and released in stages.

#### What it is

A store release takes a build from your team to your users' phones. We test each build on both platforms, prepare the listing and answer the stores' reviewers, release to a small share of users first, and ship fixes without a store release where the stores allow it.

#### What we do

- Submission to both stores.
- Answers to the stores' reviewers.
- A phased release.
- Updates where the stores allow them.

#### How we do it

1. Build: Every change built and tested on both platforms.
2. Store review: We prepare the listing and answer the reviewers.
3. Phased release: A small share of users first.
4. Updates: Fixes without a store release, where the stores allow it.

#### Questions

**Do you publish to the stores for us?**

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

#### Stack and tools

- Build pipelines
- Store submission
- Phased release
- Over-the-air updates

#### Related

- [iOS and Android](https://www.etheon.com/services/mobile?detail=ios-android#ios-android)

- [Software](https://www.etheon.com/services/software): Custom software and products
- [Web](https://www.etheon.com/services/web): Web apps, SaaS and e-commerce