Overflow explored App Clips very quickly after Apple’s announcement of the feature, but ultimately chose not to support them because they introduce friction for guests and limit what churches can do with Tap. Our goal is to ensure the simplest, most flexible, cross-platform tap experience for every person in the room - without exceptions.
Here are the core reasons:
1. App Clips create a split experience between iOS and Android
App Clips are an Apple-only technology.
If Tap relied on App Clips:
• iPhone users would see one experience
• Android users would be routed somewhere else entirely
This instantly breaks the unified, predictable moment churches want - especially during worship, giving, or guest connection.
Overflow Tap was intentionally built to be platform-agnostic, ensuring every person, on every device, gets the same simple, instant pathway.
2. App Clips limit the ability to redirect dynamically
A key benefit of Overflow Tap is the ability to change your destination URL in real time - even mid-service.
App Clips, however:
• Do not support dynamic redirect logic
• Do not allow you to instantly point an NFC tag to a changing link
• Require a fixed App Clip experience that can’t adapt on the fly
Churches need flexibility: a giving moment in worship, a QR replacement during announcements, a guest form for a special Sunday.
App Clips simply can’t support that level of agility.
3. App Clips constrain the kinds of content and flows churches can use
App Clips
• Restrict what you can show on screen
• Limit customization
• Don’t support rich, multi-step, or branded experiences
• Cannot deliver the same flexibility as a standard Overflow dynamic link
Overflow Tap is built to support any ministry moment, not a narrow App Clip template.
4. App Clips introduce friction - especially for first-time guests
One of the most important design goals for Overflow Tap is zero hesitation.
App Clips can:
• Ask for permission modals
• Take longer to load
• Present an unfamiliar Apple UI shell
• Feel more like an app download than a simple next step
In worship moments, that hesitation matters. Overflow chose the experience where the fewest things can go wrong - and the most people can participate.
5. App Clips cannot interact cleanly with ProPresenter flows
Many churches integrate Overflow Tap into their service flow using ProPresenter.
Because App Clips are controlled by iOS and can’t be influenced by external systems, they can:
• Interrupt service-driven transitions
• Fail to open consistently from ProPresenter’s controlled environment
• Break synchronization between the screen moment and the tap moment
Dynamic URLs from Overflow, by contrast, always work, regardless of device, OS, or display environment.
6. Overflow Tap is built for ministry use cases that App Clips weren’t designed for
App Clips work best for:
• Micro product demos
• Small app previews
• Simple one-off utilities
They were not built for:
• Generosity workflows
• Conversion tracking
• Cross-platform guest pathways
• Multi-use ministry moments
• Instant link changes
Overflow Tap needs to serve giving, next steps, registrations, guest connection, and more. App Clips cannot support that mission.
Why Overflow Doesn’t Use App Clips
In short:
• They only work on iOS
• They cannot support dynamic redirection
• They limit customization and future flexibility
• They introduce friction into spiritual moments
• They don’t play well with ProPresenter
• They weren’t designed for generosity or next-step engagement
Overflow Tap was built to ensure that everyone can take a next step instantly, no app download, no delays, no surprises.
It’s the simplest path for people - and the most flexible tool for churches.
