<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: OBHOLZ SOLUTIONS</title>
    <description>The latest articles on DEV Community by OBHOLZ SOLUTIONS (@stefanobholz).</description>
    <link>https://dev.to/stefanobholz</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3838927%2F5e1bdb48-cb48-491f-a984-74e722a71b5e.png</url>
      <title>DEV Community: OBHOLZ SOLUTIONS</title>
      <link>https://dev.to/stefanobholz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/stefanobholz"/>
    <language>en</language>
    <item>
      <title>How LinkHopp routes app links on Cloudflare Workers</title>
      <dc:creator>OBHOLZ SOLUTIONS</dc:creator>
      <pubDate>Mon, 06 Apr 2026 18:14:29 +0000</pubDate>
      <link>https://dev.to/stefanobholz/how-i-built-a-deep-linking-service-that-resolves-in-under-10ms-and-why-you-might-need-one-12o8</link>
      <guid>https://dev.to/stefanobholz/how-i-built-a-deep-linking-service-that-resolves-in-under-10ms-and-why-you-might-need-one-12o8</guid>
      <description>&lt;p&gt;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 &lt;a href="https://linkhopp.com/en" rel="noopener noreferrer"&gt;LinkHopp&lt;/a&gt;, those jobs are handled separately.&lt;/p&gt;

&lt;h2&gt;
  
  
  Device routing at the edge
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Carrying the invitation through installation (beta)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Android:&lt;/strong&gt; 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;iOS:&lt;/strong&gt; 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 &lt;strong&gt;Accept invitation&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No token or no match:&lt;/strong&gt; The app should use its normal entry screen. Current post-install matching has no device-fingerprint fallback and is not guaranteed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Implementation references
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Flutter: &lt;a href="https://pub.dev/packages/linkhopp/versions/1.1.0" rel="noopener noreferrer"&gt;&lt;code&gt;linkhopp&lt;/code&gt; 1.1.0&lt;/a&gt; and the &lt;a href="https://linkhopp.com/en/docs/flutter" rel="noopener noreferrer"&gt;Flutter quickstart&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;React Native: &lt;a href="https://www.npmjs.com/package/linkhopp-react-native/v/1.1.0" rel="noopener noreferrer"&gt;&lt;code&gt;linkhopp-react-native&lt;/code&gt; 1.1.0&lt;/a&gt; and the &lt;a href="https://linkhopp.com/en/docs/react-native" rel="noopener noreferrer"&gt;React Native quickstart&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;See &lt;a href="https://linkhopp.com/en/pricing" rel="noopener noreferrer"&gt;current pricing in euros&lt;/a&gt; for plans and limits.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Business users can &lt;a href="https://linkhopp.com/en/register" rel="noopener noreferrer"&gt;register online&lt;/a&gt; and create a Free project. Paid plans are available from the dashboard.&lt;/p&gt;

&lt;p&gt;I built and maintain LinkHopp. This update describes the current routing and SDK behavior; it does not make latency or match-rate promises.&lt;/p&gt;

</description>
      <category>deeplink</category>
      <category>mobile</category>
      <category>flutter</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Why I built a deep linking service for Flutter and React Native</title>
      <dc:creator>OBHOLZ SOLUTIONS</dc:creator>
      <pubDate>Sun, 22 Mar 2026 21:11:08 +0000</pubDate>
      <link>https://dev.to/stefanobholz/i-built-a-branchio-alternative-for-79mo-instead-of-499-50oe</link>
      <guid>https://dev.to/stefanobholz/i-built-a-branchio-alternative-for-79mo-instead-of-499-50oe</guid>
      <description>&lt;p&gt;Firebase Dynamic Links shut down in August 2025. I was building a Flutter app and needed a specific flow: a shared invitation should open the right screen, even if the person first has to install the app. That's why I built &lt;a href="https://linkhopp.com/en" rel="noopener noreferrer"&gt;LinkHopp&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  An invitation is more useful than an app-store link
&lt;/h2&gt;

&lt;p&gt;If the app is already installed, an iOS Universal Link or Android App Link can route the person to the invitation screen. On desktop, the link can take them to a web destination. If the app is missing, the link can send them to the relevant store instead. Opening the invitation after installation is a separate step: deferred deep linking.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happens after installation
&lt;/h2&gt;

&lt;p&gt;LinkHopp's post-install matching is in beta and uses a token, not a device fingerprint. On Android, the SDK reads the token through the Google Play Install Referrer. On iOS, the user copies the token on the landing page and explicitly triggers the app's clipboard action, for example by tapping &lt;strong&gt;Accept invitation&lt;/strong&gt;. If the token is missing, cannot be read, or cannot be resolved, show the app's usual entry screen. The store redirect alone does not guarantee a match.&lt;/p&gt;

&lt;p&gt;When testing, cover both cases: open a link with the app already installed, then start with the app absent and try the store-to-first-open flow. Test a normal install too, so you know the fallback works.&lt;/p&gt;

&lt;h2&gt;
  
  
  SDKs and pricing
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Flutter: &lt;a href="https://pub.dev/packages/linkhopp/versions/1.1.0" rel="noopener noreferrer"&gt;&lt;code&gt;linkhopp&lt;/code&gt; 1.1.0&lt;/a&gt; and the &lt;a href="https://linkhopp.com/en/docs/flutter" rel="noopener noreferrer"&gt;Flutter quickstart&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;React Native: &lt;a href="https://www.npmjs.com/package/linkhopp-react-native/v/1.1.0" rel="noopener noreferrer"&gt;&lt;code&gt;linkhopp-react-native&lt;/code&gt; 1.1.0&lt;/a&gt; and the &lt;a href="https://linkhopp.com/en/docs/react-native" rel="noopener noreferrer"&gt;React Native quickstart&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;For current plans, limits and per-app pricing in euros, see &lt;a href="https://linkhopp.com/en/pricing" rel="noopener noreferrer"&gt;LinkHopp pricing&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Business users can &lt;a href="https://linkhopp.com/en/register" rel="noopener noreferrer"&gt;register online&lt;/a&gt; and create a Free project. Paid plans are available from the dashboard.&lt;/p&gt;

&lt;p&gt;I maintain LinkHopp. I've updated this post to reflect the current SDK and pricing, rather than quoting historical competitor prices.&lt;/p&gt;

</description>
      <category>deeplink</category>
      <category>mobile</category>
      <category>flutter</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
