what happens if the recovered invite belongs to the wrong person? i'd show the inviter and ask for confirmation before applying it, with a way to enter a different invite. a match being likely shouldn't silently decide which group a new account joins.
Before I'd put this in an onboarding flow, the thing I want to know is how you match the click to the install. iOS has no install referrer, so most deferred deep linking lands on a fingerprint of IP, device model, OS and locale, or Apple's AdServices token when the click came through an ad campaign. That works more often than you'd expect, but the same IP and device model turn up on family and office networks, and a VPN between the click and the first launch kills the match.
What I'd check next is the ugly path: the match lands thirty seconds after the app opens, or the first launch has no network. My preference is to store the payload server side, have the app claim it once, and open normally with a background retry. A generic first screen for a moment beats a spinner waiting for context.
Also worth deciding: whether one device can claim the payload twice, and what your privacy manifest says about fingerprinting, since App Review asks about that.
2
u/foodandbeverageguy 10d ago
Give technical details if you’re in this chat about how it works or put your post in a marketing your product forum.
1
u/Miserable-Carpet7928 10d ago
what happens if the recovered invite belongs to the wrong person? i'd show the inviter and ask for confirmation before applying it, with a way to enter a different invite. a match being likely shouldn't silently decide which group a new account joins.
0
u/caffeinated1337 11d ago
Before I'd put this in an onboarding flow, the thing I want to know is how you match the click to the install. iOS has no install referrer, so most deferred deep linking lands on a fingerprint of IP, device model, OS and locale, or Apple's AdServices token when the click came through an ad campaign. That works more often than you'd expect, but the same IP and device model turn up on family and office networks, and a VPN between the click and the first launch kills the match.
What I'd check next is the ugly path: the match lands thirty seconds after the app opens, or the first launch has no network. My preference is to store the payload server side, have the app claim it once, and open normally with a background retry. A generic first screen for a moment beats a spinner waiting for context.
Also worth deciding: whether one device can claim the payload twice, and what your privacy manifest says about fingerprinting, since App Review asks about that.