A deep link has two different jobs. First, it needs to get a visitor to the right destination for their device. Second, if the person installs the app along the way, the app needs a way to recover the original destination. In LinkHopp, those jobs are handled separately.
Device routing at the edge
Cloudflare Workers handle the short-link request and select the relevant store or web destination. If the app is installed and the domain association is verified, iOS Universal Links or Android App Links can open the installed app. Its SDK then resolves the incoming short URL to the original in-app destination, such as an invitation. That is the direct-link flow; it doesn't require an installation token.
Carrying the invitation through installation (beta)
- Android: The Play Store URL carries a token that the SDK reads through Google Play Install Referrer after installation. For an Expo app, this Android path needs a development build, not Expo Go.
- iOS: The visitor copies the token on the landing page. The app only asks to read the clipboard after a deliberate user action, for example tapping Accept invitation.
- No token or no match: The app should use its normal entry screen. Current post-install matching has no device-fingerprint fallback and is not guaranteed.
An installed-app test doesn't prove that the store path works. On Android, test the latter from a Google Play test track with the app absent, then check the intended route after first launch. Also test an installation without a token to make sure the normal entry screen still works.
Implementation references
- Flutter:
linkhopp1.1.0 and the Flutter quickstart. - React Native:
linkhopp-react-native1.1.0 and the React Native quickstart. - See current pricing in euros for plans and limits.
Business users can register online and create a Free project. Paid plans are available from the dashboard.
I built and maintain LinkHopp. This update describes the current routing and SDK behavior; it does not make latency or match-rate promises.
Top comments (0)