App Clips

RSS for tag

Provide a way to quickly access and experience what your app has to offer. An app clip is a small part of your app that lets users start and finish an experience in seconds, even before downloading your app.

Posts under App Clips tag

64 Posts
Sort by:

Post

Replies

Boosts

Views

Activity

Can't distribute appclip from XCode
Hello, I am creating an app which includes an AppClip. I added the Clip in the build phases (as an Embed AppClip), I use everywhere the good BundleID (either the parent app, or the clip) but when I'm archiving the app, and then I distribute it, i'm still getting this error: IDEFoundation.AssociatedAppClipIdentifiersFilterErrors error 1 I can't figure why this happen, it's the first Clip I do and deploy so it's all new to me.
2
5
969
Jul ’23
App Clip - Remove Banner Popover on Load
In December 2020, I launched my first app that uses app clips. Since that time, I've had to reluctantly explain over 60 times that the notification-like banner, which appears when an app clip loads, cannot be removed. This banner, to which I'm referring, appears as the app clip fills the screen and persists for about 5 seconds. iPhone users, conditioned to click notifications, often mistake this banner as something that needs to be tapped to proceed. This misstep inadvertently takes them away from the app clip. The fact that this banner appears during the initial in-flight API calls exacerbates the number of users who incorrectly end up on the app store download page. App clips offer a full-screen, engaging native iOS experience without the need for a cumbersome app store download. However, if 5-10% of customers end up on the app store download page, it undermines the benefits for the remaining 90-95%, and brings into question whether a webpage would be a more optimal solution. App clips are designed to address use-cases where downloading an app is an unrealistic expectation. In the scenarios I service, the idea of downloading a full app stops the customer interaction immediately. If a customer ends up at the app store download page, they often won't download the app just to look at a menu, but rather complain to the server and request a paper menu. One of my initial customers was a restaurant in my hometown. At the peak of summer, they were receiving over 500 scans a night. Invariably, a subset of customers would ask the staff why they needed to download an app to see the menu. This daily occurrence led the restaurant to remove my QR menus from their tables. Another downside of the 'Powered by …' popover banner is that it deprives the owner of the advanced app clip experience of their branding. The larger the brand, the more off-putting it is for them to see what looks like us trying to advertise our own brand to their customers. When customers reach a point in their app clip journey where they need to download our full app, we have SKOverlay to prompt them. The default popover is redundant and limits our strategic approach to asking them to transition. It’s similar to asking a user for push notification permissions at app startup, instead of the moment when they understand why they need them. I've been one of the biggest advocates of app clips since their inception and have had hundreds of ground-level conversations about their implementation in the real-world. The popover is detrimental to our efforts. Please consider removing it and let us show the upgrade option when the user understands why they’re doing it. Thanks for your consideration.
1
3
568
Jul ’23
App Clip invoking from NFC Tag - only one NDEF record allowed?
Good day everyone, We have an app containing App Clip which should appear after scanning an URL from an NFC tag. Now if the tag contains ONLY one NDEF URL Record, the App Clip appears. But if there are more fields (as in our case), while URL record being still the first. App Clip is not started, iOS tries to open URL in safari. Is there might be official statement from Apple on this? Could not find any reference in the docs.
0
0
420
Jul ’23
App Clip running Firestore from React Native
I got the following error in XCode running a piece of Firestore from React Native (0.72.0): [FirebaseFirestore][I-FST000001] WatchStream (104f05718) Stream error: 'Unavailable: failed to connect to all addresses; last error: UNKNOWN: No route to host' Interestingly, this error only appears on a real decice running the App Clip (iPhone 12 mini - iOS 16.5.1). The thing that bugs me is that the same code runs well on the iPhone simulator, even with an App Clip too! Also note that the full app has the same piece of code and runs well on both simulator and real device. No problem there. What is happening hete and why is Firestore on App Clip failing only on a real device? PD: I am awate that Firestore SDK is not working for native iOS apps with App Clips. And this could be esentially the same, but why it works on the simulator then?
0
1
612
Jun ’23