PPPHP
Mobile & responsive

Responsive, mobile-first web apps — without writing front-end code

For many users, a business app now starts on a phone. Here is how PPPHP turns a database app into a responsive site on laptops — and into a fast, installable, offline-capable app on phones — with one switch.

PPPHP Team6 min read—reads

"Responsive" used to mean the page doesn't break on a phone. Users now expect more: an app that feels native, opens from the home screen, keeps working on a weak connection and taps them on the shoulder when something needs attention. Building all of that by hand means media queries, a service worker, a web app manifest, an offline queue, a push server and a lot of testing.

PPPHP RAD Studio generates it. This guide explains what responsive and mobile-first mean in a generated PPPHP app, what changes when you switch on the Mobile layer, and how progressive web app features — install, offline, push — work under the hood.

Key takeaways

  • Every generated page is responsive by default — lists, forms, dashboards and menus adapt from desktop to phone.
  • One switch adds a native-style phone UI, and a visual Mobile designer lets you shape it — tab bar, app bar, tap effects, per-page exceptions — while the desktop layout stays exactly the same.
  • Mobile-enabled builds are installable PWAs with an offline write queue and pure-PHP web push, with no third-party service.
  • Design tokens give every theme a light and dark mode, and apps translate into any language.

Responsive by default: what adapts, and how

A generated app is built mobile-friendly from the first build. Lists, add and edit forms, view pages, dashboards and navigation all re-flow for narrow screens: multi-column forms stack, wide grids become scrollable, toolbars condense, and menus collapse. Because PPPHP's themes are built on design tokens rather than hard-coded styles, spacing, type and colours stay consistent at every breakpoint.

In the visual Designer you can go further and decide per device: show a detailed chart on desktop but hide it on phones, or give a phone a simpler summary card. Images and embeds load lazily so long pages stay quick on mobile data, and lists are paged on the server, so a phone never downloads ten thousand rows to show twenty.

From responsive to native-feeling: the Mobile layer

Responsive is the floor. Open your project's Mobile page and turn on the master switch, and phones get a native app skin:

An app bar you arrangeBurger, logo, search, language, bell, theme, account — drag them into the order you want, switch off what you don't.
Bottom tab barAutomatic from your menu, or drag your own tabs into it — plus a More menu, roles per tab and twelve tap effects.
Card-style listsList rows become elevated, tappable cards instead of tiny table cells.
Floating + buttonThe primary "add" action sits where the thumb expects it.
Grouped, inset formsTouch-friendly fields with room to tap, the way settings screens look on a phone.
Three dozen behavioursEvery phone touch is a switch with an explanation — swipe actions, bottom sheets, instant navigation, scroll memory — on a live phone preview.

None of this is code you write. The Mobile page is a designer, the way the page designer is: you drag tabs into the bar, reorder the app bar, pick a shape, an indicator and a tap effect, and a phone preview beside you plays it back as you go. Pages that should be the exception get their own rule — a full-screen dashboard with no tab bar, a wide reference table left as a table — and a rule can name one page or every page of a table, the more specific one winning. For a single component, the page designer adds the last bit of control: Size & layout › On a phone lifts it to the top or drops it to the bottom of the one-column phone layout, leaving the desktop exactly as drawn.

The important engineering detail: every mobile rule lives inside a max-width media query. Your desktop layout stays byte-identical — laptop users see nothing change — and there is no second codebase, no React Native project and no app store review.

Installable: your app as a progressive web app

Every mobile-enabled build ships as an installable progressive web app (PWA). At build time PPPHP generates the three things a PWA needs:

  1. A web app manifest — your app's name, colours (taken from your theme) and display mode, so it launches standalone without browser chrome.
  2. A service worker — the background script that caches pages, serves them offline and handles push messages.
  3. App icons — generated from the icon you upload (or created automatically), with no PPPHP branding on your app.

On Android and Chrome, users get an Add to Home Screen prompt; on iPhone and iPad it is Share → Add to Home Screen. Once installed, your app opens full-screen from its own icon — indistinguishable, for most users, from a store app.

Offline-first: work that survives a dead connection

Field staff, warehouses, basements and rural roads all have one thing in common: patchy signal. With the Mobile layer on, a PPPHP app becomes offline-tolerant:

  • Reads keep working. The service worker serves cached pages so browsing continues, with an inline offline fallback page for anything not yet cached.
  • Writes are never lost. A form submitted while offline is stored in a durable queue in the browser's IndexedDB, then replayed automatically when the connection returns — through the Background Sync API, with an "online" fallback on iOS.
  • Users can see it. An offline banner shows a live count of pending submissions, so nobody wonders whether their work was saved.

File uploads are deliberately left out of the queue (they need a live connection), and the whole offline layer is on by default once the Mobile switch is enabled.

Web push notifications — no third-party service

Push notifications usually mean signing up for a messaging service. PPPHP includes a pure-PHP Web Push engine using the open standards (VAPID keys and encrypted payloads). Generate your keys from the Mobile page in one click, turn push on, rebuild — then send a notification from any event or scheduled task:

pp_push([
    'title' => 'New order',
    'body'  => '#1042 · $1,240',
    'url'   => '/orders',
]);

Subscriptions are stored in your own app, and expired ones are pruned automatically. One platform note: on iOS, web push works for apps installed to the home screen.

Dark mode, themes and brand consistency

Users expect dark mode, and brands expect their colours. PPPHP ships 16 ready-made themes, each with a light and a dark variant, including macOS-, Windows 11- and HarmonyOS-inspired looks. Because everything — buttons, cards, tables, charts, forms — reads the same design tokens, one change re-skins the entire app consistently. Duplicate any theme to make your own brand palette, and pick a navigation layout (classic, horizontal, sidebar, rail, boxed or hero) that suits your audience.

Multilingual apps: speak every user's language

A mobile audience is a global audience. The app's chrome — menus, buttons, page titles, field labels — is already routed through a translation layer, so adding a language is a matter of supplying the words. A built-in auto-translate pass fills empty strings as a first draft, the content you design on the canvas translates too, and a language switcher appears for users. With live translation editing on, an admin can correct wording inside the running app with no rebuild. Nepali ships ready, alongside a Bikram Sambat date picker. See the languages guide.

Fast on mobile networks

Speed is part of mobile UX — and of search ranking. Production builds compress JavaScript and CSS and version assets so browsers cache them aggressively but always fetch fresh files after a new release. Lists, searches and filters run as paged SQL on the server; CSV and Excel exports stream in batches; images load lazily. The result is a lean page on a 4G connection, not a heavy single-page bundle.

A mobile launch checklist

  1. Turn on the Mobile layer and review the live phone preview.
  2. Upload an app icon so the installed PWA carries your brand.
  3. Decide per-device visibility for heavy dashboard widgets in the Designer.
  4. Enable push if users need alerts, and send from a "record added" event.
  5. Serve over HTTPS — service workers, install prompts and push all require it.
  6. Test offline: switch the phone to airplane mode, submit a form, reconnect and watch it sync.

New to PPPHP? Start with the complete 0-to-100 guide, or watch the Mobile demo in the live capability theatre.

Frequently asked questions

Are PPPHP apps responsive without extra work?

Yes. Every generated page adapts from desktop to phone by default. The optional Mobile layer adds a native-style phone interface without changing the desktop layout.

Can users install a PPPHP app on their phone?

Yes. Mobile-enabled builds are progressive web apps with a manifest, a service worker and app icons, so users can add them to the home screen and launch them full-screen — no app store needed.

Does the app work offline?

Cached pages keep working offline, and forms submitted offline are queued in IndexedDB and synced automatically when the connection returns. File uploads need a live connection.

Do push notifications need Firebase or another service?

No. PPPHP includes a pure-PHP Web Push engine using VAPID keys. On iOS, push works for apps installed to the home screen.

Does every theme support dark mode?

Yes. Each of the 16 built-in themes has light and dark variants, and themes you duplicate inherit both.

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.

Keep reading

Complete guide

PPPHP RAD Studio, 0 to 100: the complete guide to building database web apps

Step-by-step guide to PPPHP RAD Studio: connect any SQL database, generate CRUD pages and dashboards, then secure, build and deploy a PHP web app you own.

7 October 2026 · 7 min read—Read
For developers

The modern web stack in one studio: APIs, real-time, security and deployment

What ships in every PPPHP app: REST API, OAuth2, GraphQL, webhooks, real-time SSE, passkeys, row-level security, payments, cloud storage and AI.

7 October 2026 · 5 min read—Read
Mobile & responsive

Design the mobile app — don’t build a second one

Give a database app a real phone experience without a second codebase: a bottom tab bar you drag into shape, an arrangeable app bar, tap effects, per-page rules, installable PWA, offline writes and web push — from one build that still serves desktop.

15 October 2026 · 7 min read—Read
Getting started

From nothing installed to a live app on a phone

A free, portable PHP 8.5 + MariaDB + Caddy stack that runs from one folder on Windows, macOS and Linux — no installer, no admin password, no port 80 fight — and a visual studio that turns that database into a web app, a REST API and an installable mobile app from a single build.

17 October 2026 · 8 min read—Read
Security

A critical PHP flaw landed. Here is where you actually stand.

Two critical remote-code-execution flaws in PHP — CVE-2026-109618 and CVE-2026-109619, CVSS 9.2 — were fixed in PHP 8.5.12, and nothing is left outstanding. A plain-English explanation of what they are, a two-minute way to check whether your server is exposed, and how PPServer shipped the patched build within days.

25 October 2026 · 8 min read—Read
Product

Build forms that react to what people type. No JavaScript required.

Conditional field visibility, star & pill filters, one-click date presets, and type-ahead suggestions from your own data — the field-control upgrades in PPPHP RAD Studio that make a generated app feel hand-built, configured once and compiled into clean PHP you own.

12 November 2026 · 5 min read—Read