# Mobile and offline

URL: /products/app/mobile-and-offline · Id: `page:products/app/mobile-and-offline`

> How an App works on a phone, installs from the browser, and keeps working where there is no signal.

Every [App](/business/nouns/app) works on a phone from its first publish. It installs from the browser, and its screens render as JSON for native clients on the same records.

## On a phone
Every screen fits a phone's width with no second design. Leaseline's residents never install anything: a renewal notice links to their lease, and they answer in two taps.

A manager who opens the App every day installs it from the browser to the home screen. It opens full screen and receives push notices by her [notice](/products/app/notifications) choices.

## Native clients
Each screen also renders as JSON, so a native client on a phone, a watch or a TV draws it without a second API. The JSON carries the record and each [Verb](/business/nouns/verb) the reader may call.

## Offline
Status `planned`. A field worker's lists and records stay readable with no signal, and calls made offline queue on the device. Each runs in order when the signal returns, under the same rules as any other call, and a refusal comes back with its reason.

## Next
[Sell](/products/app/sell) covers plans and billing inside the App.