<?xml version="1.0" encoding="utf-8" standalone="yes"?> <?xml-stylesheet href="https://maik.io/pretty-feed-v3.xsl" type="text/xsl"?>

<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>friction on maik.io</title>
    <link>https://maik.io/tags/friction/</link>
    <description>Recent content in friction on maik.io</description>
    <generator>maik.io</generator>
    <language>de-de</language>
    <lastBuildDate>Fri, 14 Nov 2025 11:48:32 +0100</lastBuildDate>
    <atom:link href="https://maik.io/tags/friction/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>~20%</title>
      <link>https://maik.io/notes/2025-11-14-circa-20-percent/</link>
      <pubDate>Fri, 14 Nov 2025 11:48:32 +0100</pubDate>
      <guid>https://maik.io/notes/2025-11-14-circa-20-percent/</guid>
      <description>&lt;p&gt;Lea Verou schreibt in »&lt;a href=&#34;https://lea.verou.me/blog/2025/user-effort/&#34; title=&#34;In the economy of user effort, be a bargain, not a scam • Lea Verou&#34; target=&#34;_blank&#34; &gt;In the economy of user effort, be a bargain, not a scam&lt;/a&gt;« auf ihrem Blog&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;This distinction hinges on the distribution of use cases. Products often cut scope by identifying the ~20% of use cases that drive ~80% of usage — aka the Pareto Principle. Some products, however, have such diverse use cases that Pareto doesn’t meaningfully apply to the product as a whole. There are common use cases and niche use cases, but no clean 20-80 split. The tail of niche use cases is so long, it becomes significant in aggregate. For lack of a better term, I’ll call these long‑tail UIs.&lt;/p&gt;</description>
      <content:encoded>
      <![CDATA[<p>Lea Verou schreibt in »<a href="https://lea.verou.me/blog/2025/user-effort/" title="In the economy of user effort, be a bargain, not a scam • Lea Verou" target="_blank" >In the economy of user effort, be a bargain, not a scam</a>« auf ihrem Blog</p>
<blockquote>
<p>This distinction hinges on the distribution of use cases. Products often cut scope by identifying the ~20% of use cases that drive ~80% of usage — aka the Pareto Principle. Some products, however, have such diverse use cases that Pareto doesn’t meaningfully apply to the product as a whole. There are common use cases and niche use cases, but no clean 20-80 split. The tail of niche use cases is so long, it becomes significant in aggregate. For lack of a better term, I’ll call these long‑tail UIs.</p>
</blockquote>
<p>Der Beitrag bündelt wichtiges Wissen. Für alle, die Software entwickeln, lohnt sich die Lektüre.</p>
]]>    
      <![CDATA[<br><br><hr><br><small><p>Vielen Dank fürs Lesen! Wenn du Lust auf noch mehr Gedanken, Updates und ab und zu einen Blick hinter die Kulissen hast, folge mir doch gern auf <a href="https://maik.io/mastodon">Mastodon</a> oder <a href="https://maik.io/instagram">Instagram</a>.</p><p>Hast du Fragen oder Feedback? Schreib mir gern eine <a href="https://maik.io/email">E-Mail</a>.</p></small>]]>
      </content:encoded>  
    </item>      
  </channel>
</rss>