Publish once, in Drupal
Editors keep their workflow. A node published in Drupal is in the app the next time a page loads.
For Drupal teams
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.
Before you paste: Use your public production URL. Staging behind HTTP auth or an IP allowlist will not load.
See how it worksComes with you
Editors keep their workflow. A node published in Drupal is in the app the next time a page loads.
Point tabs at News, Events, Library and Account. The rest of your menu goes in the side menu, grouped one level deep.
Send a title, text, image and link from the dashboard, through your own Firebase project. Sent to everyone who opted in.
AI writes scripts that hide your site header and pop-ups inside the app only. Your theme and page cache stay untouched.
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.
Scan a code and use your real site as an app, before you pay.
You may be asked to install our preview app first.
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.
The usual route to a Drupal app is a decoupled build on JSON:API, with a second codebase to fund and maintain.
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).
The app shows your site in a WebView, which behaves like a mobile browser with a few differences worth checking.
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.
Sign-in leaves for your identity provider, and some providers restrict embedded browsers.
Try it: Sign in your usual way, including the MFA step.
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.
Default Drupal settings can clear an idle session after about two days.
Try it: Reopen the app tomorrow and check the session.
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.
A file handed to another app loses the session, so Drupal refuses it.
Try it: Open a restricted PDF while signed in.
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.
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.
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.
The app opens one start URL, so choose the language prefix it starts on.
Do this: Switch language and tap every tab again.
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
Website changes show up in the app without a rebuild. No subscription, and the price doesn’t change as your app gains users.
Paid to Apple and Google
Later rebuilds, such as a new icon, are included.
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.
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.
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.
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.
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.
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.
Paste your site URL and open the preview on your phone. Pay only when you build.
No account or card to preview.