<?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: Maksym Yergiyev</title>
    <description>The latest articles on DEV Community by Maksym Yergiyev (@maksym-yergiyev).</description>
    <link>https://dev.to/maksym-yergiyev</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%2F4004652%2F0a5a31a8-f574-4d7f-8039-6a78cd186dfd.jpg</url>
      <title>DEV Community: Maksym Yergiyev</title>
      <link>https://dev.to/maksym-yergiyev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/maksym-yergiyev"/>
    <language>en</language>
    <item>
      <title>Before You Print That App Download QR Code, Test Where It Goes</title>
      <dc:creator>Maksym Yergiyev</dc:creator>
      <pubDate>Tue, 17 Nov 2026 21:01:04 +0000</pubDate>
      <link>https://dev.to/maksym-yergiyev/before-you-print-that-app-download-qr-code-test-where-it-goes-4p7e</link>
      <guid>https://dev.to/maksym-yergiyev/before-you-print-that-app-download-qr-code-test-where-it-goes-4p7e</guid>
      <description>&lt;p&gt;Your designer sends over a QR code for an upcoming app launch.&lt;/p&gt;

&lt;p&gt;Someone scans it on an iPhone. The App Store opens. Looks good.&lt;/p&gt;

&lt;p&gt;But what happens on Android? What does a laptop visitor see? And if someone changes the destination after the artwork has gone to print, will the same QR code still work?&lt;/p&gt;

&lt;p&gt;A QR code that scans successfully isn't necessarily ready to print. Once it's on 2,000 flyers, correcting a mistake becomes a lot less convenient.&lt;/p&gt;

&lt;h2&gt;
  
  
  QR is only the beginning
&lt;/h2&gt;

&lt;p&gt;Let's say your app is available in the App Store and on Google Play. You could print two QR codes, but then you're asking people to figure out which one they need before they even reach the app.&lt;/p&gt;

&lt;p&gt;Another option is a single public URL with device-aware routing. The QR code contains that URL; the routing service decides where to send the request.&lt;/p&gt;

&lt;p&gt;For example, a link like &lt;a href="https://go.example.com/get-app" rel="noopener noreferrer"&gt;https://go.example.com/get-app&lt;/a&gt; could route iPhone visitors to an App Store listing, Android visitors to Google Play, and desktop visitors to an app website. You need to configure the desktop fallback; it shouldn't be assumed.&lt;/p&gt;

&lt;p&gt;This doesn't detect whether an app is installed, open a particular in-app screen, or measure actual installations. It's a simpler job: get a visitor to the intended download destination.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4x9v9jupmpwfndxpyywb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4x9v9jupmpwfndxpyywb.png" alt=" " width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd check before printing
&lt;/h2&gt;

&lt;p&gt;I'd spend less time comparing QR generator designs and more time following the actual link on the devices people will use.&lt;/p&gt;

&lt;p&gt;First, open both store destinations directly. Make sure they lead to the right app—not an outdated listing, an unrelated app with a similar name, or an unavailable store page.&lt;/p&gt;

&lt;p&gt;Then scan the final QR code and follow the full journey:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Test&lt;/th&gt;
&lt;th&gt;What I want to see&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;iPhone, Safari&lt;/td&gt;
&lt;td&gt;Correct App Store listing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Android, Chrome&lt;/td&gt;
&lt;td&gt;Correct Google Play listing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Desktop browser&lt;/td&gt;
&lt;td&gt;Intended website or fallback&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;iPhone Camera&lt;/td&gt;
&lt;td&gt;Correct destination after scanning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Android QR scanner&lt;/td&gt;
&lt;td&gt;Correct destination after scanning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Relevant in-app browser&lt;/td&gt;
&lt;td&gt;Acceptable behavior in that channel&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;That last row is easy to miss. If your campaign mainly runs in Instagram, email, or a messaging app, check it there too. A link behaving correctly in Safari doesn't establish what will happen in every embedded browser.&lt;/p&gt;

&lt;p&gt;And don't overlook region availability. A valid App Store URL isn't proof that the app can be downloaded in every market.&lt;/p&gt;

&lt;h2&gt;
  
  
  One detail from working on an app-routing product
&lt;/h2&gt;

&lt;p&gt;While working on a mobile app-routing product, we distinguished between inspecting the configured destinations and testing the live redirect.&lt;/p&gt;

&lt;p&gt;A preview can show which iOS, Android, and web URLs are saved, without triggering the redirect or recording another visit. That's useful for checking setup.&lt;/p&gt;

&lt;p&gt;But a configuration preview cannot prove the end-to-end journey. It won't tell you whether a particular mobile browser or QR scanner reaches the correct store listing.&lt;/p&gt;

&lt;p&gt;I think of these as two different tests: Is the link configured correctly? And does it work correctly for the visitor?&lt;/p&gt;

&lt;p&gt;Both matter before printing something you can't easily change.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try changing a destination without replacing the QR
&lt;/h2&gt;

&lt;p&gt;Here's the check I'd do before relying on an editable link for printed material:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Create a test public URL with destinations you control.&lt;/li&gt;
&lt;li&gt;Generate and save a QR code for that URL.&lt;/li&gt;
&lt;li&gt;Scan it on iPhone and Android.&lt;/li&gt;
&lt;li&gt;Change one destination behind the same public URL.&lt;/li&gt;
&lt;li&gt;Scan the original QR code again.
If you're using an editable managed URL, the printed QR should still contain the same URL while the service uses the updated destination.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you encoded a direct App Store listing instead, changing that listing's URL won't magically update the printed code. It's an easy difference to miss until a campaign is already out in the world.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2mvsyuj64uh4gzdpmk6q.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2mvsyuj64uh4gzdpmk6q.png" alt=" " width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Use a test link rather than experimenting on a live campaign.&lt;/p&gt;

&lt;h2&gt;
  
  
  Don't forget the physical print
&lt;/h2&gt;

&lt;p&gt;A QR image that looks fine on a large monitor may be hard to scan on a small sticker or a glossy poster.&lt;/p&gt;

&lt;p&gt;Print a proof at the actual size. Check the contrast and the blank space around the code. Try it at the distance people will stand from it, in roughly the lighting they will have.&lt;/p&gt;

&lt;p&gt;I'd also scan the proof with both iPhone and Android. A laptop preview is not a substitute for testing the printed thing.&lt;/p&gt;

&lt;h2&gt;
  
  
  And please don't call clicks installs
&lt;/h2&gt;

&lt;p&gt;If a link reports 200 clicks, it reports 200 recorded clicks under that service's counting rules. That isn't the same as 200 app installs—or even proof that every visitor successfully reached the store.&lt;/p&gt;

&lt;p&gt;If you're trying to measure installs, you'll need separate measurement and an appropriate attribution setup. For a basic QR distribution campaign, first make sure the link takes people where you intended.&lt;/p&gt;

&lt;h2&gt;
  
  
  The five-minute release check
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsbdya9kernu0hfz8t2t3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsbdya9kernu0hfz8t2t3.png" alt=" " width="800" height="600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Before the artwork goes to print, I'd want answers to these questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Are the iOS and Android store listings correct and accessible where the campaign will run?&lt;/li&gt;
&lt;li&gt;Does the shared URL work on actual iPhone and Android devices?&lt;/li&gt;
&lt;li&gt;What happens on desktop or when a platform destination is missing?&lt;/li&gt;
&lt;li&gt;Does a physical proof of the final QR artwork scan reliably?&lt;/li&gt;
&lt;li&gt;If destinations are editable, does the same QR survive a destination change?&lt;/li&gt;
&lt;li&gt;Are we reporting clicks separately from installs?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's not complicated testing. It's just a lot cheaper to do it before the flyers arrive.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>mobile</category>
      <category>qr</category>
      <category>testing</category>
    </item>
    <item>
      <title>App install links vs deep links: the practical difference</title>
      <dc:creator>Maksym Yergiyev</dc:creator>
      <pubDate>Sat, 27 Jun 2026 00:00:37 +0000</pubDate>
      <link>https://dev.to/maksym-yergiyev/app-install-links-vs-deep-links-the-practical-difference-2bi2</link>
      <guid>https://dev.to/maksym-yergiyev/app-install-links-vs-deep-links-the-practical-difference-2bi2</guid>
      <description>&lt;p&gt;When people talk about mobile links, the terms often get mixed together: app install links, deep links, deferred deep links, attribution, SDK-based tooling, and native app links all get pulled into one conversation.&lt;/p&gt;

&lt;p&gt;That makes the problem feel bigger than it is.&lt;/p&gt;

&lt;p&gt;For many teams, the actual requirement is much simpler:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;send iPhone users to the App Store&lt;/li&gt;
&lt;li&gt;send Android users to Google Play&lt;/li&gt;
&lt;li&gt;send desktop visitors to a web fallback&lt;/li&gt;
&lt;li&gt;keep one public URL stable across campaigns, QR codes, and support docs&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If that is the job, you do not need to solve every mobile-link problem at once. You need a routing link.&lt;/p&gt;

&lt;h2&gt;
  
  
  App install links are about routing
&lt;/h2&gt;

&lt;p&gt;An app install link is a public URL that routes a visitor to the right place for their device. The link can stay stable even if the destination changes later.&lt;/p&gt;

&lt;p&gt;That means the link works as a distribution asset:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;in a launch post&lt;/li&gt;
&lt;li&gt;in a QR code&lt;/li&gt;
&lt;li&gt;in a support reply&lt;/li&gt;
&lt;li&gt;in a printed handout&lt;/li&gt;
&lt;li&gt;in a campaign email&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The key property is simple: the link routes people to the right place for the device they are using.&lt;/p&gt;

&lt;p&gt;For example, a routing link can send:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;iPhone users to the App Store&lt;/li&gt;
&lt;li&gt;Android users to Google Play&lt;/li&gt;
&lt;li&gt;desktop visitors to a web fallback&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is routing, not deep linking.&lt;/p&gt;

&lt;h2&gt;
  
  
  Deep links solve a different problem
&lt;/h2&gt;

&lt;p&gt;Deep links are for opening specific content inside an installed app.&lt;/p&gt;

&lt;p&gt;That is useful when you already know the exact in-app destination you want to open.&lt;/p&gt;

&lt;p&gt;But deep links are not the same as app install routing. They solve a different job:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;install routing answers: where should this visitor go?&lt;/li&gt;
&lt;li&gt;deep linking answers: what in-app screen should open?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Those are not interchangeable.&lt;/p&gt;

&lt;p&gt;If your team only needs install routing, calling the problem a deep-linking problem creates unnecessary complexity.&lt;/p&gt;

&lt;h2&gt;
  
  
  Deferred deep links add another layer
&lt;/h2&gt;

&lt;p&gt;Deferred deep links are a separate category again.&lt;/p&gt;

&lt;p&gt;They try to carry context through the install flow so the first app open can continue a specific path.&lt;/p&gt;

&lt;p&gt;That is a different workflow from simple install routing.&lt;/p&gt;

&lt;p&gt;If you do not need to carry context through install, you probably do not need deferred deep linking.&lt;/p&gt;

&lt;p&gt;This is where teams often overbuy tooling:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;they start with a link-routing problem&lt;/li&gt;
&lt;li&gt;they move into attribution terminology&lt;/li&gt;
&lt;li&gt;then they end up evaluating SDK-heavy platforms before they actually need them&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your goal is just to route people to the right store or fallback, keep the scope narrow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Attribution and MMP tooling are different again
&lt;/h2&gt;

&lt;p&gt;Attribution is about measurement. MMP tooling is typically used when teams need postbacks, measurement workflows, cohort views, or ROAS/LTV reporting.&lt;/p&gt;

&lt;p&gt;That can be the right choice for some teams.&lt;/p&gt;

&lt;p&gt;It is not the same thing as app install routing.&lt;/p&gt;

&lt;p&gt;If you need:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;install attribution&lt;/li&gt;
&lt;li&gt;postbacks&lt;/li&gt;
&lt;li&gt;cohorts&lt;/li&gt;
&lt;li&gt;ROAS/LTV reporting&lt;/li&gt;
&lt;li&gt;SDK-based measurement&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;then a routing-only tool is not enough.&lt;/p&gt;

&lt;p&gt;That is a product boundary, not a flaw.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to decide what you actually need
&lt;/h2&gt;

&lt;p&gt;Here is the simplest way to choose:&lt;/p&gt;

&lt;h3&gt;
  
  
  Use app install routing when
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;you need one stable public URL&lt;/li&gt;
&lt;li&gt;you want App Store, Google Play, and web fallback routing&lt;/li&gt;
&lt;li&gt;you want the URL to stay the same across campaigns or QR codes&lt;/li&gt;
&lt;li&gt;you want editable destinations later&lt;/li&gt;
&lt;li&gt;you only need basic aggregate clicks&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Use deeper tooling when
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;you need native app screen opening&lt;/li&gt;
&lt;li&gt;you need deferred deep linking&lt;/li&gt;
&lt;li&gt;you need attribution or postbacks&lt;/li&gt;
&lt;li&gt;you need SDK-based measurement&lt;/li&gt;
&lt;li&gt;you need reporting beyond simple routing&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you are still deciding, start by naming the job, not the tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical examples
&lt;/h2&gt;

&lt;p&gt;Routing-only examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a launch card with one public link&lt;/li&gt;
&lt;li&gt;a QR code for an event booth&lt;/li&gt;
&lt;li&gt;a support email that sends people to the right store&lt;/li&gt;
&lt;li&gt;a packaging insert that needs one stable link&lt;/li&gt;
&lt;li&gt;a campaign landing page that should route by device&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Not routing-only examples:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a flow that must open a specific screen inside the app&lt;/li&gt;
&lt;li&gt;a flow that must carry context through install&lt;/li&gt;
&lt;li&gt;a flow that depends on attribution or partner postbacks&lt;/li&gt;
&lt;li&gt;a flow that needs a mobile measurement partner&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why the distinction matters
&lt;/h2&gt;

&lt;p&gt;If you collapse all mobile links into one bucket, you end up comparing tools that do not actually solve the same problem.&lt;/p&gt;

&lt;p&gt;That is how teams end up asking the wrong question:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"Which platform is best?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;when the better question is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"What job does this link need to do?"&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That question usually leads to a smaller, clearer solution.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where Smart Linker fits
&lt;/h2&gt;

&lt;p&gt;Smart Linker is the routing example here.&lt;/p&gt;

&lt;p&gt;It is designed for teams that need one app link for App Store, Google Play, and web fallback, plus editable destinations, QR-ready links, custom domains, and basic or aggregate clicks.&lt;/p&gt;

&lt;p&gt;It does not claim:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;deferred deep linking&lt;/li&gt;
&lt;li&gt;install attribution&lt;/li&gt;
&lt;li&gt;MMP replacement&lt;/li&gt;
&lt;li&gt;Branch / AppsFlyer / Firebase parity&lt;/li&gt;
&lt;li&gt;SDK-based routing&lt;/li&gt;
&lt;li&gt;native app screen opening&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want the narrower boundary and the tradeoffs in one place, the reference guide is here:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://smartlinker.info/resources/app-install-links-vs-deep-links" rel="noopener noreferrer"&gt;App install links vs deep links&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Closing thought
&lt;/h2&gt;

&lt;p&gt;Mobile links are easier to reason about when you keep routing, deep linking, and attribution separate.&lt;/p&gt;

&lt;p&gt;If the job is routing, keep the tool simple.&lt;br&gt;
If the job is measurement or native app behavior, use the tool built for that job.&lt;/p&gt;

&lt;p&gt;That separation saves time, keeps claims honest, and makes the implementation decision clearer for everyone involved.&lt;/p&gt;

</description>
      <category>mobile</category>
      <category>android</category>
      <category>ios</category>
    </item>
  </channel>
</rss>
