Troubleshoot the most common reason a Glide PWA won't install on iPhone: the Add to Home Screen option missing, opening in the wrong browser, or installing as a plain bookmark.
You share your published Glide app, and a user reports they cannot install it. Either the Add to Home Screen option is missing, or the app opens as a normal browser tab instead of full-screen.
This is one of the most common Glide-on-iPhone complaints, and it is almost never a bug in your app. It is usually about how the link was opened.
Because Glide apps are web-based PWAs, the install path depends entirely on the iOS Add to Home Screen flow. If any part of that flow is off, installation fails.
The good news is that the fixes are quick once you know the cause. Let's work through them in order of likelihood.
Before you start, gather two details from the user: which app they tapped the link in, and whether they see the address bar after opening. Those two answers alone point to the right cause most of the time.
The number one cause is opening the link in something other than Safari. On iPhone, the full PWA Add to Home Screen experience is tied to Safari.
If a user opens the link in Chrome or another browser, the option may be missing or behave differently. In-app browsers inside messaging and social apps are the worst offenders.
The fix: instruct users to open the app URL directly in Safari. If they received the link inside another app, they should choose to open it in Safari from that app's menu.
A reliable trick is a QR code pointing to your app. Scanning it with the iPhone camera opens the link in Safari, avoiding the in-app browser trap entirely.
When a user is stuck inside an in-app browser, look for a share or overflow menu with an Open in Safari option. Copying the URL and pasting it into Safari manually works just as well.
Make Safari the assumed default in every instruction you write. Simply saying open the link and leaving the browser unspecified is what produces most of these reports in the first place.
Sometimes the icon gets added but the app opens with Safari's address bar visible, behaving like a bookmark rather than a standalone app.
This usually means it was added from a non-Safari context or the page had not fully loaded when Add to Home Screen was tapped.
The fix: remove the existing icon, open the app URL fresh in Safari, wait for it to fully load, then use Share and Add to Home Screen again.
After reinstalling, tap the icon and confirm it opens full-screen without the address bar. That confirms it registered as a proper PWA.
The order of operations matters here. Removing the old icon first prevents confusion between the broken bookmark and the correctly installed app, since two similar icons are easy to mix up.
If it still opens with the address bar after a clean reinstall, verify the original link is the real Glide app URL and not a shortened or redirected link, because some redirects strip the metadata iOS needs for a standalone install.
If the app fails to load at all, no install will succeed. A common reason is that the project was never published, so only your editor can see it.
Another is a link error, such as a typo in the shared URL or an outdated link from a previous version.
The fix: confirm the app is published in Glide, copy the current live URL directly from Glide, and test it yourself in Safari on a device before sharing.
Also check any access settings. If the app requires sign-in and a user cannot authenticate, they may perceive it as broken even though the install mechanism is fine.
Test the link on a device that is not signed into your Glide account. Something that loads fine for you as the owner can be blocked or invisible to an outside user, which is exactly the experience your audience gets.
If you recently republished or changed the app's URL, re-share the current link. Users holding an old link will keep hitting a dead end no matter how many times they retry the install steps.
Occasionally the device itself is the problem. A very outdated iOS version, an overloaded Safari, or restrictive settings can interfere with PWA installation.
Start simple: have the user close all Safari tabs, then reopen the link in a single fresh tab. A cluttered browser sometimes misbehaves.
Ensure the device is on a reasonably current iOS version, since PWA behavior has evolved across releases. Encourage updating if they are far behind.
Check Screen Time or content restrictions if installs are blocked entirely, especially on managed or family-configured devices.
A private browsing tab can also change behavior, so make sure the user is in a normal Safari window rather than a private one when they attempt the install.
On corporate or school devices, a mobile device management profile may restrict adding home-screen apps. If you suspect that, the device's administrator is the right person to confirm and adjust the policy.
Run through these in order and you will resolve the vast majority of cases. First, is the link open in Safari specifically, not another browser or an in-app browser?
Second, did the page fully load before tapping Share and Add to Home Screen? A half-loaded page produces a bookmark-like result.
Third, is the app actually published, and does the URL work when you test it yourself on a device?
Fourth, can the user sign in if authentication is required, and is their iOS reasonably current? If all four check out, the install will normally succeed.
Work the list in order rather than jumping around, because the earlier items are both the most common and the fastest to check. Skipping ahead usually wastes time on rare causes.
Keep this checklist somewhere you can paste it into a support reply. Handing a user four concrete questions is far more effective than a vague suggestion to try again.
The best fix is documentation that stops the problem before it starts. Provide a short, explicit install guide with the exact three steps: open in Safari, tap Share, choose Add to Home Screen.
Include screenshots, because the Share button and the Add to Home Screen row are easy to miss for non-technical users.
Distribute a QR code alongside the link. It funnels users straight into Safari and removes the single most common failure mode.
Finally, set expectations that this app installs from a link, not the App Store. That one sentence prevents a surprising number of confused support messages.
If you have a landing page, put the instructions and the QR code there so every new user meets the same clear guidance at the moment they arrive.
Where you can, detect the browser and show a gentle hint when someone opens the link outside Safari. Even a simple line telling them to open in Safari heads off the most frequent install failure before it happens.
If your real requirement is a store-installed native app, no amount of PWA troubleshooting will deliver that. The PWA route tops out at home-screen install.
App Store presence requires wrapping the web app natively, which brings in Xcode, an Apple Developer Program membership, and real rejection risk for thin wrappers.
Before going down that road, be sure the PWA truly does not meet your needs. For most internal tools and MVPs, a well-documented install flow is entirely sufficient.
If you do need the store, treat it as a separate project with its own budget and timeline, not as a fix for an install prompt that never appeared.
Be honest about the distinction between an install bug and a distribution-model limit. A missing Add to Home Screen option is a fixable flow problem; wanting App Store discoverability is a different requirement altogether.
Once you have separated those two, the right next step is usually clear. Either finish hardening the PWA install experience, or scope the native wrapper effort deliberately, but do not confuse one for the other.
Almost always because the link was opened in a browser other than Safari, or in an in-app browser. Open the URL directly in Safari on iPhone and the option should appear.
It likely registered as a bookmark rather than a PWA, often because the page hadn't fully loaded. Remove it, open fresh in Safari, wait for full load, then add again.
Yes. If the app isn't published or the link is wrong, it won't load and can't install. Confirm the app is published and test the live URL yourself in Safari.
Usually not. These install issues are about the iOS Add to Home Screen flow and browser choice, not your app's data or design.