Your app on a phone
Every app you build already works on a phone — the layout reflows, the tables scroll. The Mobile page is where you make it feel like an app instead: a bottom tab bar you design, a top bar you arrange, lists that stack into cards, sheets that rise from the bottom, and an icon on the home screen that opens without a browser bar.
Finding a setting
The page is grouped into six tabs down the left side:
| Tab | What is in it |
|---|---|
| Start here | A flavour pack — a curated starting point for everything else. |
| Navigation | The bottom tab bar, the top app bar, the action button, and which tabs people actually use. |
| Feel | How a tap feels, how lists stack, how menus rise — the long list of small things. |
| Platform | Offline reading and writing, push notifications, the phone's own share sheet, and unlocking with a thumb. |
| Pages | The exceptions: one page that needs to be different from the rest. |
| Install | Appearance, the app icon, home-screen shortcuts and the installable app itself. |
The arrow keys move between tabs, and the one you are on is part of the page's address — so a link you send to someone opens on the same tab you were looking at. A small number next to a tab counts what you have set up there; it is hidden when there is nothing yet. The master switch sits above the tabs, because it governs all six.
Looking for one setting? Type it in the search box above the tabs — or press / from anywhere on the page. It searches all six groups at once and shows the matches together, each under its own heading, with a count beside the box. Press Esc, use the ×, or simply pick a group to go back to where you were.
The master switch
Native mobile experience at the top turns the whole layer on and off. With it off, the generated app simply uses its ordinary responsive layout on phones — which is a perfectly good answer for an app people only ever open at a desk.
Start from a flavour pack
Three dozen behaviours, all on sensible defaults, is powerful and slightly lonely — there is no obvious place to begin. The packs at the top of the page are that place: iOS-like, Material-like, Field work (big targets, no animation, offline and drafts on), Reading room (the bar tucks away, long text folds) and Showroom (everything turned up). Each tile tells you how many settings it would change before you touch it, and says in place once your app already matches it.
A pack sets taste, never content: it will not touch your tabs, your pages or your menu. Apply one and then change anything you like — and applying a different one afterwards is the way back.
The bottom tab bar
The single clearest signal that something is an app. Two ways to fill it:
| Mode | What you get |
|---|---|
| Auto | The first few items of your menu become tabs. Nothing to maintain — add a menu item and the bar follows. |
| Custom | You choose each tab: its icon, its label, and where it goes. Drag the handles to reorder. |
A tab can point at a table's list page, one of your designed pages, a custom page, or any address you type. Use the people icon on a tab to limit it to certain roles or groups — someone without them never sees that tab at all.
A number on a tab — badge counts
Any tab can carry a badge: a count on the tab, or just a dot for "there is something here". Choose
the table to count and, if you want, the rows that matter (status <> 'done') — unread
messages, open orders, today's jobs.
The “More” tab
Five tabs is the ceiling, so the last one can be a More. Give it your own label and icon, and choose what it opens: the full navigation drawer, or a bottom sheet listing just the items you pick. Sheet items can be limited by role exactly as tabs can.
How the bar looks
Edge to edge along the bottom, or floating as a rounded pill lifted off it; frosted so the page blurs through it, or solid. The tab you are on can be marked by a pill behind its icon, a dot under it, a line across the top, or nothing but colour. Height, icon size, label size and corner radius are sliders, and the two colours follow your app's theme until you set them.
Labels can sit below the icon, beside it, or be dropped altogether for an icons-only bar. A hairline above the bar separates it from the page — switch it off for a bar that floats. And Hide while scrolling down tucks the bar away as someone reads and brings it straight back the moment they scroll up, which is the single biggest way to buy back screen on a small phone.
What a tap feels like
A real app answers a tap before the page has gone anywhere. Tap effect is a list of twelve: a quick pop or bounce, a soft pulse or glow, a playful wiggle, jelly or swing, a lift, flip, beat or drop — or none. Each one is described in the picker as you hover it, and the phone preview plays it, so you can try all twelve in about ten seconds and keep the one that suits the app. Anyone whose phone is set to reduce motion gets the colour change and none of the movement.
The top bar
Every part of it — the menu button, your logo and name, quick find, the language picker, the notification bell, the theme switch and the account menu — has a switch and a drag handle. Whatever order the list is in is the order the bar will be in. A part you switch off is dimmed rather than removed, so you can always see what is available to put back.
Some parts only exist when the app actually has them: no bell unless notifications are on, no account menu unless people sign in. Those rows say so.
The language picker is the one part that starts switched off, and the only one that is not even listed until it can do something: it appears once the project has two or more languages in Misc → Project → Languages. With one language there is nothing to switch between, so the row is left out and a line under the list says when it will arrive. When you do have two or more, the row names them, and it warns you if Show language selector is off in Misc — because that switch hides the picker everywhere, including here.
Turned on, the bar shows it compactly: the language's flag if you have given it one, otherwise a globe. Where you have a flag it is the better of the two, because it says which language at a glance; a globe only says there is a choice. The preview wears whichever your project would actually show, and will not draw a picker your build would not render.
Behaviours: the long list of small things
Under Behaviours are the touches that separate an app from a website. Each is a switch with its own sentence saying what it does, grouped so you can read a whole family at once:
| Group | What lives there |
|---|---|
| Getting around | The tab bar itself, edge-swipe back and forward, filter tabs drawn as a segmented control, tapping the open tab to jump to the top, and the “…” page-actions button. |
| Touch | Swipe a row for Edit and Delete, press and hold for the same menu, a notification panel that folds with your finger, skeleton loaders while a page arrives, haptic taps, and page transitions. |
| Signature | The ones people notice without being able to name: the next page fetched as the finger lands, coming back to exactly where you were, pull-to-refresh, KPI tiles as a swipeable carousel, a calendar that opens as an agenda, a record that opens in a sheet instead of a new page, endless scrolling, and forms that keep a draft. |
| Controls | Wide tables restacked as cards or list rows, the right keyboard for each field, instant search, sticky headers, long descriptions folded to two lines, phone numbers and e-mails that dial and compose, proper empty states and native-looking toasts. |
| Phone & platform | Offline mode, push notifications, the phone's own share sheet, receiving shares from other apps, the install prompt, the unread badge on the icon, and staying signed in. |
Everything is on sensible defaults, so the honest answer for most apps is to leave this section alone. It is here for the day you want one particular thing to stop happening.
Long lists
Infinite scroll loads the next rows as somebody reaches the end, instead of making them find and tap a pager button. It is off by default — a list people navigate by page number, or print, is better with the pager — and it is built on that same pager underneath, so filters, sorting and who-can-see-what behave exactly as they do on page two. If a page fails to load it puts the ordinary pager back rather than stranding anyone at the bottom of a list that will not grow.
Pages that are different
Most pages should look the same, so Pages is for the exceptions — a full-screen dashboard with no tab bar, a report with no Add button, a wide reference table that reads better as a table than as stacked cards.
| Choice | Means |
|---|---|
| As the app | This page has no opinion. If you change the app-wide setting later, this page follows. |
| Always show / Always hide | This page overrules the app, now and later. |
A rule can name one page or every page of a table, and the more specific one wins — so you can switch the tab bar off across a table and back on for the single page inside it that needs it. A page can also carry a shorter title for phones; the full title still shows on a desktop.
Watching it as you work
The phone on the right is not a picture. It follows every change as you make it — the bar you are arranging, the tabs you are dragging, the colours, the shape, the folded description, and whether a list is stacked into cards or left as a table. Use Previewing underneath it to stand in for a page, and you will see what it looks like before you build: the picker lists every page your app makes, grouped, with the ones carrying a rule marked. The mock stands in for whatever you choose — a dashboard shows tiles and a chart, a record shows label-and-value rows, a form adds its save bar, a list asks the cards-or-table question — and takes that page's own name as its title unless a rule renames it for phones.
Pick iPhone or Android above the phone to change the frame it wears — the corner radius, the bezel, the notch or hole-punch camera, the strip the phone keeps at the top for its clock and signal icons, and the band it keeps at the bottom for its gesture bar. Your app's own bar starts below that strip and its tab bar stops above that band, exactly as it will on the device. Only the frame changes: one build serves both handsets, so the screen inside is deliberately identical. Your choice is remembered for you and is not saved into the project.
Installing it on a phone
Switch on Install as an app (PWA) and your app can be kept on a home screen: its own icon, its own name, no browser bars. Give it a square icon and a theme colour, or let the build make one from your logo. On Android the browser offers to install it; on an iPhone the person uses Share › Add to Home Screen, and the app tells them so rather than showing a button that would do nothing.
An installed app can also stay signed in, work offline, and receive push notifications — each its own switch under Platform & native bridge, with its own explanation on the page.
Long-press the app icon
Home-screen shortcuts put up to four jumping-off points on the installed icon — New order, Today's tasks, Scan. Give each a name, an optional second line and a destination. Android and desktop Chrome show them; an iPhone ignores them and simply shows its usual menu, so adding them costs nothing there.
Using the camera
Two field controls turn the phone's camera into data entry. Both are ordinary controls you pick in the Designer, so they work on any form and behave like any other field afterwards — validation, lists, export and the API all treat them normally.
| Control | What it does |
|---|---|
| Scan to fill | A text box with a scan button that reads a barcode or QR code straight into the field. Turn on Keep scanning to count a pallet instead of reading one label, and it ticks on each hit so a picker does not have to look at the screen. |
| Take a photo | The File & Image field offers the camera beside the file picker on a phone or tablet, through the device's own camera app — so you get full resolution and the flash. Switch it off for a field that only ever receives documents. |
Neither needs this module: a camera is hardware, not a phone skin, so a tablet in a warehouse can photograph a pallet whatever the plan. The scan button appears only where the browser can genuinely decode a code — today that is Chrome on Android. Everywhere else the field is simply a text box, rather than a button that opens a camera and then cannot read anything.
Reading when there is no signal
An app that is offline can already accept work — a form filled in a basement is queued and sent when the signal returns. Read offline is the other half: it keeps a small, recent copy of the tables you choose, so the list still has rows on it when there is nothing to load them from.
Pick up to six tables, say how many recent rows each should keep and how long a copy may be trusted. When the phone goes offline the list paints from that copy with a quiet line saying when it was taken; when the signal comes back it reloads for real. Nothing is editable from a copy — it is a reference, not a second source of truth.
The copy belongs to the person who is signed in: it is scoped to them, it expires on its own, and signing out erases it along with everything else the app cached.
Deciding one thing at a time
A phone is a bad place for a grid of twenty columns and a good place for one question. The Triage page type gives a table a queue: one record fills the screen, and a swipe right, a swipe left or a button writes one field and brings the next one up.
| Setting | What it does |
|---|---|
| Field | The one column a decision writes to — a status, a flag, an approval. |
| Right / Left | The value each direction writes, and the words on the two buttons. |
| Shown on the card | The few fields that are enough to decide. Resist the urge to add more: if a decision needs twelve fields it is not a triage, it is an edit. |
Every decision goes through exactly the same door as the Edit form — the same permissions, the same row-level security, the same validation rules and the same business events — so a rule you wrote once cannot be swiped past. A decision that is refused brings the card back with the reason on it, and Undo puts the last one back.
It is a page type like any other, so it also works with a mouse: the buttons are always there, and the arrow keys drive the queue on a desktop.
Which tabs people actually use
You will choose five tabs and be wrong about at least one of them. Tab use tells you which, by counting taps — and nothing else.
The Mobile page draws the last thirty days as a simple bar per tab. Read it for the shape, not the arithmetic: a tab nobody taps is a tab that should be behind More, and a tab buried in More that people keep digging for belongs in the bar.
Coming back without signing in again
A session that times out on a desktop is a small annoyance. On a phone, where the app is opened twenty times a day in ten-second bursts, it is the reason people stop using it. Resume with a thumb changes what an idle timeout does: instead of ending the session it locks it, and a fingerprint or a face opens it again.
This needs passkeys turned on in Security, and it only ever applies to someone who has already enrolled one — a lock nobody can open is just a worse sign-out.
In practice that means their face or their fingerprint. A passkey on a phone is held by the phone itself, so unlocking runs Face ID or Touch ID on an iPhone, the fingerprint sensor on Android, and Windows Hello on a laptop. There is nothing extra to set up and no face data ever reaches your app — the phone does the recognising and only tells the app “yes, it is them”.
| It does | It does not |
|---|---|
| Hold an idle session instead of ending it | Extend the absolute session lifetime — that ceiling still ends the session, locked or not |
| Expire the lock on its own clock | Stay unlocked for ever on a phone left behind |
| Show a lock screen with nothing on it | Leave a single record, menu or number readable behind the lock |
| Open for the person it was locked for | Open for somebody else's passkey, however valid |
Set how long a lock may be held — anything from a few minutes to a week. Shorter is safer; a working day is the usual answer.
Using the phone's own hardware: voice, NFC tags and location
Dictate instead of typing · tap an RFID/NFC asset tag · record where a job was signed off, where a delivery was made, where an inspection happened.
The camera is not the only thing a phone has that a desktop does not. Three more field controls reach the hardware, and all three follow the same rule as the scanner: the button only appears where the browser can actually do the job. Everywhere else the field is an ordinary box, so a mixed fleet of phones is never a problem.
| Control | What it does, and where it works |
|---|---|
| Speak to fill | A Dictate button that types what the person says — for the thirty words of fault description that get abandoned on a phone keyboard. Works on iPhone and on Chrome. Set it to keep listening for a long note, or to add to what is already there. |
| Tap an NFC tag | Hold the phone against a tag and the field fills. Better than a label for anything that lives outdoors, gets washed, or sits where a camera cannot get a clean line of sight. Android only today. |
| Where it was | The existing Address / Location field can now record where someone is with the accuracy of the fix, and optionally capture it the moment a form opens — for job sheets, deliveries and site visits. |
Stopping the screen going dark
Keep the screen awake holds the display on while a long job is open — a stocktake, a triage queue, a form being read off a clipboard. A phone dims after about thirty seconds of not being touched, which is exactly what happens while somebody reads a shelf label or talks to a customer.
It is off by default because it costs battery, and the phone takes the lock straight back the moment your app is not the thing on screen — so it cannot keep a phone awake in a pocket. Supported in every current browser, iPhone included.
Getting it in front of a real phone
Open on your phone shows a QR code for the built app. Point a camera at it and you are there — which is worth doing at least once, because a real thumb on real glass tells you things a desktop browser narrowed to 375px never will.