Turning a Drupal Site Into an App for Universities and Public Bodies
Short answer
A Drupal site can be published as an iOS and Android app by wrapping it in a native shell, which works well for news, events and service pages. The hard parts are single sign-on, which identity providers increasingly block inside embedded web views, deep content navigation and accessibility. If the app needs offline data or campus-style native features, a headless native app on Drupal's JSON:API is often the better choice.
Why Drupal sites are different
Drupal powers many university, government and NGO websites. These sites are large: thousands of nodes, several menus, multilingual content, and often an authenticated area for students, staff or citizens. A wrapper app can reuse all of it, but the decisions are less about the shell and more about login, navigation and accessibility.
Single sign-on inside an app
Institutions rarely use Drupal's own user accounts. Logins typically go through SAML (for example via the samlauth or SimpleSAMLphp modules), OpenID Connect or CAS, backed by Microsoft Entra ID, Shibboleth or a federation. Inside an app this needs care:
- Embedded web views are discouraged for sign-in. Google blocks them outright, and current OAuth guidance for native apps recommends the system browser. Some institutional identity providers also apply device or browser checks that fail in an embedded view.
- The system browser does not share cookies with your web view. If sign-in happens in a secure browser sheet, you need a handoff: the identity provider redirects back to the app, and the app passes a one-time token to Drupal to create a session in the web view.
- Multi-factor prompts switch to an authenticator app and back. Test that the app returns to the right page without losing the login state.
If only a small part of the site is behind login, a pragmatic option is to keep the authenticated area in the system browser and make the public parts the core of the app.
Navigating content-heavy sites on a phone
A desktop mega menu with five levels does not work in an app. Users of an institutional app usually want a handful of top tasks: news, events, contacts, opening hours, a service directory, sometimes a canteen menu or timetable. Put those in a native tab bar or start screen and route the rest through Drupal's search. Practical steps:
- Analyze which pages mobile visitors actually open today.
- Create a dedicated app menu in Drupal and hide the main header when the page is loaded in the app.
- Make sure search works well on phones; it becomes the main navigation for everything outside the tabs.
- Decide how external links (other faculty sites, PDFs, third-party portals) open, and keep that consistent.
Accessibility in a wrapped app
Public bodies in the EU must meet accessibility requirements for websites and apps, generally measured against WCAG and EN 301 549. A wrapper inherits the web content's accessibility: semantic headings, alt texts and form labels from a well-built Drupal theme are read by VoiceOver and TalkBack. Two gaps to close yourself: native elements such as tab bars, offline screens and push permission dialogs need proper labels, and text should scale with the user's system font size, which requires relative units in your theme. Check both with a screen reader on real devices. This is general information, not legal advice.
When a headless native app is better
A wrapper is the fast, low-maintenance route. A native app on top of Drupal's JSON:API, which is part of Drupal core, makes more sense when the app must work offline, combine data from campus management or other systems, use background location or wallet passes, or deliver a fully native accessibility experience. It costs more to build and maintain, so be sure the use case justifies it.
How jocapps can help
For the wrapper route, WebViewGold converts your Drupal site into native iOS and Android apps with push notifications, offline support and more than 40 native APIs, as a one-time purchase. WeSetupYourWebViewApp does the setup for you and delivers store-ready apps with full source code within 72 hours. For SSO handoffs, headless apps and long-term operation, OnlineAppCreator is our ISO-certified B2B and B2G delivery team with long-term SLAs. To discuss your situation, book a free 30-minute call via the meeting planner.
Frequently asked questions
Can students log in with our university SSO inside the app?
Usually yes, but not reliably inside an embedded web view. The robust approach is to sign in through the system browser and hand the session over to the app with a one-time token.
Does a wrapped Drupal app meet accessibility requirements?
It inherits the accessibility of your Drupal theme, plus whatever the native parts add. You still need to test with screen readers and document the result; a wrapper does not make a site compliant on its own.
Do we need a Drupal module for the app?
Not for a wrapper. For a headless native app, Drupal core's JSON:API module exposes content to the app, often combined with modules for authentication.
How do we keep content editors' workflow unchanged?
With a wrapper nothing changes: editors keep publishing in Drupal and the app shows the live pages. Push messages can be triggered from the same publishing workflow.
Guides on this topic
Related solutions
- Website and web app to mobile appPublish a Bubble App to the App Store and Google Play
- Website and web app to mobile appTurn a Django Web App Into iOS and Android Apps
- Website and web app to mobile appPush Notifications for Online Shops: Permission, Segments and Consent
- Website and web app to mobile appTurn a Joomla Website Into an App for Members, Parents and Citizens
Talk to us about your project
Honest advice on your idea, prototype or app.
- 30 minutes
- Free
- No obligation
