Guillaume Laforge<p>When we talk about <a href="https://uwyn.net/tags/GenerativeAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenerativeAI</span></a>, it's easy to get fixated on <a href="https://uwyn.net/tags/chatbots" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chatbots</span></a>. But in my experience, they're just one interface for <a href="https://uwyn.net/tags/LLMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLMs</span></a>. </p><p>My latest article argues for a more seamless and unobtrusive <a href="https://uwyn.net/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> integration.</p><p>We're seeing a lot of "AI sparkle" buttons ✨ pop up in apps <a href="https://uwyn.net/tags/UI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UI</span></a>, and while they signal <a href="https://uwyn.net/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AI</span></a> is there, they often break a user's flow and the <a href="https://uwyn.net/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UX</span></a>. </p><p>True <a href="https://uwyn.net/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LLM</span></a> augmentation shouldn't require an explicit click or a separate chat 💬</p>