# Mobile and home screen

> Every app works on phones; Pro apps install to the home screen. The honest answer on app stores.

"Will it work on phones?" is usually asked before the first prompt, so here is the whole answer up front: yes, every Vaulter app works in every phone's browser; on Pro it can be installed to the home screen like an app; and it cannot be listed in the App Store or Google Play today.

## Every app is a responsive web app

Vaulter builds responsive layouts by default: pages adapt to the screen instead of assuming a desktop. The preview has a device toggle so you can check the phone layout as you build, and phone behavior is promptable like everything else:

> On phones, the sidebar becomes a bottom tab bar with Home, Orders, and Settings, and the tables scroll sideways instead of shrinking.

Test on a real phone before launch: open the published URL on your own device and walk the main flow with a thumb, not a mouse. Real hardware surfaces what emulation misses, like touch target sizes and keyboard behavior in forms.

## Install to home screen (Pro)

With the [PWA card](/docs/publish/publishing-extras) configured, visitors' browsers offer to install your app: your icon on their home screen, opening full-screen in its own window. For most "I want my app on their phone" goals, this is the answer, and it ships in minutes, with no store review and no waiting.

## The honest boundary: app stores

Vaulter apps are not packaged for the App Store or Google Play. If a store listing is genuinely a requirement, Vaulter is not the whole path today; see [Known limitations](/docs/reference/limitations). Worth asking first, though, whether the store is the requirement or the home screen icon is; the second one you can have today.

## Frequently asked

#### Does the installed app work offline?

Assume no. Vaulter apps are live web apps; they need a connection to load data and sign users in.

#### Can my app send push notifications to phones?

Not today. For "notify my users", email through the [Resend connector](/docs/integrations/resend) is the reliable pattern.

#### The phone layout of one page looks cramped

Point at it specifically: "on phones, the products page shows one column and the filters collapse behind a button". Page-by-page phone instructions land better than "make it mobile friendly".