Deep Dive Into Deep Link. Part 3. OS shell, application
<p>We continue writing our cycle. Parts <a href="https://medium.com/metakratos-studio/deep-dive-into-deep-link-part-1-introduction-and-the-initial-problem-e1de15845fb3" rel="noopener">one</a> and <a href="https://medium.com/metakratos-studio/deep-dive-into-deep-link-part-2-issues-device-os-version-63930665e3c2" rel="noopener">two</a> are available on <a href="https://medium.com/metakratos-studio" rel="noopener">our Medium</a>. If you haven’t read this far, go ahead. This knowledge will help you deal with it with confidence. For those who are already know the cycle, let us remind you of the theses of the previous article:</p>
<ul>
<li><strong>We have considered the structure of experiments: the configuration table, the experiment table, the testing process itself</strong></li>
<li><strong>Described the chronology of problems</strong></li>
<li><strong>Analyzed the hypothesis about the influence of device hardware on deep link processing</strong></li>
</ul>
<blockquote>
<p><em>Hypothesis 1: Different devices — </em><strong><em>BUSTED</em></strong><em>.</em></p>
<p><em>The device (hardware part) does NOT affect Deep Link processing.</em></p>
</blockquote>
<p>We have examined in detail how the Android OS version affects deep link processing</p>
<blockquote>
<p><em>Hypothesis 2. Different Android versions is </em><strong><em>BUSTED</em></strong><em>.</em></p>
<p><em>Android OS version does NOT affect Deep Link processing.</em></p>
</blockquote>
<p>Today we are going to deal with two more issues related to OS shells and the application from which deeplink is opened.</p>
<p>At the end of the previous article, we formulated hypotheses 3 and 4:</p>
<blockquote>
<p><em>Hypothesis 3. Different OS shells.</em></p>
<p><em>Android OS shell affects the performance of Deep Link.</em></p>
<p><em>Hypothesis 4. Application.</em></p>
<p><em>The application from which the link is opened affects Deep Link.</em></p>
</blockquote>
<p>Today we’re going to break down some interesting examples that will set the stage. Let’s get started!</p>
<h1>Problem №3. Different shells</h1>
<blockquote>
<p><em>Different OS shells. Deep link processing was different on different Android shells</em></p>
</blockquote>
<p>Let’s describe the conditions under which the problem is reproduced:</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:770/1*SuTKaAEK4LVtJlhsgLFFqQ.png" style="height:78px; width:700px" /></p>
<p>Config X-1. One UI configuration</p>
<p><img alt="" src="https://miro.medium.com/v2/resize:fit:770/1*hk0wK_omTIV3stLiDsTx2A.png" style="height:78px; width:700px" /></p>
<p>Config Y-1. Vanila configuration</p>
<p>On both devices, open Gmail, send yourself an email with the link <em>domain1.domain2.ru/landing</em>, receive it, open it, click on it.</p>
<p><a href="https://medium.com/@valeryvpetrov.dev/deep-dive-into-deep-link-part-3-os-shell-application-bc3def843d27">Read More</a></p>