# Mobile

## Purpose

Android/iOS specifics.

## Decisions

### Mobile

- **Targets:** phone browsers, installed web apps (PWAs) and a **native Android app**.
- **Android approach:** wherever possible the app shows the **web version inside it**, so it uses the same CSS and looks identical. Where that is not applicable or appropriate, the same tokens are rebuilt as native Android resources and components are redrawn natively. Web inside the app is the default.
- **Sizes:** on mobile each control moves up one size, and navigation is a burger-menu drawer (see [Sizing](../foundations/sizing.md) and [Navigation](../components/navigation.md)).
- **Hover content** (tooltips and the like) must also appear on tap.
