Every team hits the same wall. The web app works; people start opening it on a phone; and the feedback is not "it is broken" — it is "it feels like a website". Buttons are small, the menu is behind a hamburger, a table scrolls sideways, and the thing you came to do is below forty rows. The usual answers are both expensive: live with it, or start a second project in React Native or Flutter and keep two things in step forever.
There is a third answer, and it is the one this guide is about: design the phone experience inside the same builder that made the web app, and ship it in the same single build.
Key takeaways
- Responsive is the floor, not the goal. What people mean by "feels like an app" is furniture and feedback — a bottom tab bar, sheets, swipe actions, and a response before the page moves.
- The phone layer is designed visually, not coded: drag tabs into the bar, arrange the top bar, pick how a tap feels, make one page the exception — on a live phone preview.
- One build serves every screen. Every phone rule lives inside a width media query, so the desktop layout is untouched and there is no second codebase.
- It installs to the home screen as a PWA, keeps a durable offline write queue, and sends web push — no app store, no third-party service.
What "feels like an app" actually means
It is worth being precise, because "make it mobile-friendly" is not a specification. When people call something an app rather than a website, they are usually reacting to five concrete things:
None of that is exotic. All of it is tedious to build by hand, which is why most internal tools never get it.
Designed, not coded
In PPPHP RAD Studio this is a page in the builder, not a stylesheet you maintain. A live phone preview sits beside you and follows every change.
- The bottom tab bar. Leave it automatic and the first items of your menu become tabs. Or choose each one: drag it into place, give it an icon, a label and a destination — a table's list page, a designed page, or any address. Five is the ceiling, because a sixth makes every target too narrow for a thumb, so the last one becomes a More that opens either the full drawer or a bottom sheet of just the items you pick.
- Who sees which tab. A tab can be limited to roles or groups, and that is decided on the server for the person asking — a tab someone may not use never reaches their phone.
- How it looks. Edge-to-edge or floating; frosted or solid; the active tab marked by a pill, a dot, a line or just colour; labels below, beside, or gone. Hide while scrolling down tucks the bar away as someone reads and brings it straight back — the single biggest way to buy back screen on a small phone.
- How a tap feels. Twelve effects to choose from, previewed as you hover each one. Anyone whose phone asks for reduced motion gets the colour change and none of the movement, automatically.
- The top bar. Burger, logo, search, language, notification bell, theme switch, account menu — each has a switch and a drag handle, and the order in the list is the order on the bar.
- The exceptions. A full-screen dashboard with no tab bar. A report with no Add button. A wide reference table that genuinely reads better as a table. A rule can name one page or every page of a table, and the more specific one wins.
For a single component, the page designer adds the last piece: Size & layout › On a phone lifts it to the top or drops it to the bottom of the one-column phone layout. That is how a total, a search box or the Save button gets above a wide table on a phone while the desktop stays exactly as drawn.
Three dozen behaviours, each a switch
Under the surface are the small things, grouped so you can read a family at once rather than hunt a list: getting around (edge-swipe back, filter tabs as a segmented control, tap the open tab to jump to the top), touch (swipe a row, press and hold, skeletons, haptics), the signature ones (instant navigation, scroll memory, pull-to-refresh, KPI carousels, a record opening in a sheet, autosaved drafts), controls (tables restacked as cards or list rows, the right keyboard per field, instant search, tap-to-dial) and the platform ones (offline, push, the share sheet, the install prompt, the unread badge).
Two are worth knowing by name:
Everything sits on a sensible default, so the honest advice is to leave the section alone until the day you want one particular thing to stop happening.
Installable, offline, and push — without an app store
Switch on Install as an app and the build writes the three things a phone needs: a web app manifest with your name and colours, a service worker, and icons. Then the two platforms differ, and it pays to know which is which:
| Android / Chrome | iPhone / iPad | |
|---|---|---|
| Installing | The browser offers it, and your app can prompt too | No prompt exists — the person uses Share → Add to Home Screen, and the app says so rather than showing a button that would do nothing |
| Push notifications | Work in the browser and installed | Only once the app is installed — Apple's rule, so getting people to install is step one, not a nice-to-have |
| Requirement | HTTPS. A phone will not install or push from a plain http:// address. | |
On offline, the precise answer matters more than the feature name. A submitted form that cannot reach the server is queued on the phone in durable storage and replayed when the connection returns — including after the browser is closed and reopened. Autosaved drafts keep what has been typed into a form that has not been submitted. What is not kept is your data: pages and records are never stored on the phone, deliberately, because a stale record shown confidently is worse than an honest "no connection", and a lost phone should not be carrying a copy of your database. So: writes survive a dead connection, reads need one — which, for warehouse and field work, is the shape you want.
Web push is pure PHP with VAPID keys — no Firebase account, no third-party service, nothing phoning home.
Why one build matters more than it sounds
Every phone rule lives inside a max-width media query, so the desktop layout is byte-identical and the same files serve both. That is not an implementation detail; it is the whole economic argument:
- No divergence. A field added to a form is on the phone the moment it is on the desktop, because it is the same form.
- No second review cycle. You ship a fix by deploying, not by waiting for an app store.
- No second skill set. Nobody has to learn a mobile framework to change a label.
- No caching headache. There is one URL and one deployment, not a web build and a binary at different versions.
The honest limit: this is an excellent web app that installs and behaves like an app — not a native binary. There is no App Store listing, and it cannot reach APIs that only a native app can. For the overwhelming majority of business software, that trade is the right way round.
Where to start
Turn the master switch on, open your app on a real phone with the QR code the builder shows, and change one thing: make the tab bar hide while scrolling. A real thumb on real glass tells you things a desktop browser narrowed to 375 px never will. Then read the mobile documentation, or see the rest of what ships in the box in the modern stack guide and the complete guide.
Frequently asked questions
Do I need a second codebase for mobile?
No. The phone layer is part of the same project and ships in the same build; every mobile rule lives inside a width media query, so the desktop layout is unchanged. There is no React Native or Flutter project to keep in step.
Is this a native app or a progressive web app?
A progressive web app. It installs to the home screen with its own icon, runs without browser bars, works offline for writes and receives push notifications — but it is not a native binary and there is no app store listing.
Can I change the bottom tab bar?
Yes. Leave it automatic and it follows your menu, or choose each tab and drag it into place with its own icon, label and destination. Five tabs is the ceiling; the last can be a More that opens the full menu or a bottom sheet of items you pick. Tabs can be limited by role or group, enforced on the server.
What happens if someone loses signal mid-form?
A submitted form is queued on the phone in durable storage and replayed when the connection returns, even after the browser is closed. Unsubmitted typing is kept as a draft. Records themselves are not stored on the phone, so reads still need a connection.
Does web push work on iPhone?
Yes, but only once the app has been added to the home screen — that is Apple’s rule, not a limitation of the builder. On Android it works in the browser as well as installed. Both need HTTPS.
Can one page look different from the rest on a phone?
Yes. Per-page rules switch the tab bar, the floating add button and the page-actions control on or off for one page or for every page of a table, and the more specific rule wins. A page can also carry a shorter title for phones.
Build your first app today
Point PPPHP RAD Studio at a database — or start on the built-in one — and have a secure, responsive web app running before lunch.