For Drupal teams

Turn your Drupal site into a mobile app

Your members get an iOS and Android app that loads the pages your theme already renders. No decoupled or headless build; Views, roles and translations stay on your server.

  • No account or card to preview
  • Pay once per platform
  • The app listing is yours

Before you paste: Use your public production URL. Staging behind HTTP auth or an IP allowlist will not load.

See how it works
Illustration: an example Drupal website shown as a phone app with a native header, bottom tabs and a push notification.

Comes with you

  • Content types, Views and workflow
  • Roles and permissions, server-side
  • Translations and Webforms, as rendered
In the app

What your members and staff get

Publish once, in Drupal

Editors keep their workflow. A node published in Drupal is in the app the next time a page loads.

Four tabs replace the mega menu

Point tabs at News, Events, Library and Account. The rest of your menu goes in the side menu, grouped one level deep.

Push for closures and deadlines

Send a title, text, image and link from the dashboard, through your own Firebase project. Sent to everyone who opted in.

One header, pop-ups hidden

AI writes scripts that hide your site header and pop-ups inside the app only. Your theme and page cache stay untouched.

How it works

From your URL to an app on your phone

  1. Paste your Drupal URL

    We fill in your name and icon. AI sorts your links into a header, side menu and tabs, and writes the script that hides your site’s own header and pop-ups. You adjust the rest.

  2. Open it on your phone

    Scan a code and use your real site as an app, before you pay.

    You may be asked to install our preview app first.

  3. Build and publish

    We build in the cloud, so you need no Mac or Xcode. iOS lands in TestFlight in your Apple account; Android downloads as an AAB or APK. You submit for review from your own accounts.

Setup tips

  • Build tab links from path aliases you expect to keep through upgrades.
  • Create a demo account with a representative role for Apple and Google reviewers.
One system of record

Does a Drupal app need a decoupled build?

The usual route to a Drupal app is a decoupled build on JSON:API, with a second codebase to fund and maintain.

SiteTo.AppYour live site in a native shell

What users open
Your Drupal theme in a native shell
Access rules
Run on your server, as today
What you maintain
One Drupal site
Best for
Content, accounts and forms your site already has
Price
$29-$99 once, plus Apple and Google developer accounts

Other routeA decoupled app on JSON:API

What users open
Screens coded for the app
Access rules
Rebuilt against the API
What you maintain
A second codebase and releases
Best for
Offline use, Bluetooth, app-only screens
Price
A quoted development project

Good fit

  • Member and association portals
  • Council, nonprofit and university sites
  • News and resource libraries on Views

Choose the other route if

You need heavy offline use, Bluetooth, background processing or app-only screens your theme cannot render.

Also weighed: a responsive site alone or a PWA (no App Store listing).

How website-to-app conversion works
Drupal features in the app

How do Drupal logins, permissions and private files behave in the app?

The app shows your site in a WebView, which behaves like a mobile browser with a few differences worth checking.

Loads as on mobile web

Views, content types and permissions

Drupal renders each page and checks access on your server, as on the web.

Try it: Open a role-restricted page signed in and signed out.

Test in the preview

SSO sign-in: SAML, OpenID Connect, CAS

Sign-in leaves for your identity provider, and some providers restrict embedded browsers.

Try it: Sign in your usual way, including the MFA step.

More about SSO sign-in: SAML, OpenID Connect, CAS

The standard Drupal login form at /user/login is the dependable path. Sites that sign in through SAML, OpenID Connect or CAS send the user to an identity provider and back, and some providers restrict embedded browsers. Google can block its sign-in screen inside in-app browsers, and an enterprise policy that requires a managed device or an approved browser can have the same effect. Run a complete sign-in with a real account, including the MFA prompt.

Test in the preview

Staying signed in

Default Drupal settings can clear an idle session after about two days.

Try it: Reopen the app tomorrow and check the session.

More about Staying signed in

Drupal keeps users signed in with a session cookie. The default cookie lasts about 23 days, but Drupal’s default settings can also clear a session left unused for a little over two days, and your organization may have changed both. Sign in, close the app fully, reopen it the next day and see whether you are still signed in.

Test in the preview

Private files and PDFs

A file handed to another app loses the session, so Drupal refuses it.

Try it: Open a restricted PDF while signed in.

More about Private files and PDFs

Minutes, forms, reports and course material often sit in Drupal’s private file system, where each download is checked against the signed-in user. Open a restricted PDF from inside the app, then go back to the page you came from. If the file is handed to another app or browser that does not hold the session, Drupal treats the request as anonymous and refuses it.

Needs setup

Cookie banners and the admin toolbar

Scripts hide your site header and pop-ups, but editors still see the admin toolbar.

Do this: Accept the cookie banner, then check the tabs.

More about Cookie banners and the admin toolbar

A cookie banner from EU Cookie Compliance or Klaro, a newsletter modal or a sticky site header can sit on top of the app’s native header and bottom tabs. SiteTo.App can hide your site’s own header and pop-ups with scripts that run in the app, so the theme and your page cache stay as they are. Staff who sign in will still see the admin toolbar, so test with an editor account as well as a member account.

Needs setup

Languages and domains

The app opens one start URL, so choose the language prefix it starts on.

Do this: Switch language and tap every tab again.

More about Languages and domains

The app opens one start URL, for example yoursite.org/fr. If Drupal detects language from a path prefix or a domain, decide which one the app starts on and keep the language switcher reachable. If detection follows the browser language, check what a phone set to each language receives. Tab links point at fixed paths, so check them after switching language.

These are a starting point for your free preview, not a claim that every site setup or integration has been tested. Not for apps that need Bluetooth, AR, heavy offline use or background processing.

Planning the build?Setup walkthroughReadiness checklist

Pricing

Drupal app pricing: preview free, pay once

Website changes show up in the app without a rebuild. No subscription, and the price doesn’t change as your app gains users.

Androidone time
$29
iOSone time
$79
iOS + Androidone time
$99

Paid to Apple and Google

  • Apple Developer Program $99 a year
  • Google Play $25 once

Later rebuilds, such as a new icon, are included.

Questions, answered

Know exactly what you’re getting

Still unsure? Talk to our team
Can I convert a Drupal site into a mobile app?

Yes, you can turn a Drupal site into an iOS and Android app with SiteTo.App without rebuilding it. The app loads your live Drupal site, adds your branding and menus, and costs $29 for Android, $79 for iOS or $99 for both, paid once per platform. Apple and Google developer accounts are separate.

Do we need a Drupal module, an API or a specific version?

No. SiteTo.App loads the pages your theme already renders from the public URL, so there is nothing to install and no JSON:API to expose. It does not depend on the Drupal version, so Drupal 10, Drupal 11 and Drupal CMS sites can all be previewed, including a decoupled front end with a public URL.

Is my Drupal site a web app or a mobile app?

Your Drupal site already works as a web app in any phone browser. SiteTo.App adds an iOS and Android app around it: a native shell with your icon, tabs and push that loads your live site, which you submit to the App Store and Google Play from your own accounts.

What happens when I update my Drupal site?

People see the latest version of your website when they open or refresh the app, so ordinary content and page updates do not need a new app build. A new app icon, app name or launch screen needs a new build.

Will Apple approve my Drupal app?

Apple decides, so nobody can guarantee it. Apple can reject apps that add nothing beyond a website (Guideline 4.2), so plan for real app features such as native navigation and push, and test your key journeys in the preview first.

Can I preview the app before paying?

Yes. Paste your URL and open the preview on your own phone. You don’t need an account or a card to preview, though you may be asked to install our preview app first. You only pay when you choose a build.

Test your Drupal login in the app today

Paste your site URL and open the preview on your phone. Pay only when you build.

No account or card to preview.