<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Api-First on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/api-first/</link><description>Recent content in Api-First on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Apr 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/api-first/index.xml" rel="self" type="application/rss+xml"/><item><title>The New Front Door</title><link>https://drlongnecker.com/blog/2026/04/agent-facing-product-design-api-first-interface/</link><pubDate>Wed, 29 Apr 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/04/agent-facing-product-design-api-first-interface/</guid><description>&lt;p&gt;When mobile emerged as a serious product surface, a lot of teams, my own included, responded by making their web app text smaller. It wasn&amp;rsquo;t laziness; &amp;ldquo;Mobile&amp;rdquo; just felt like a variant of what already existed, not a different interface. That misread cost some teams years.&lt;/p&gt;
&lt;p&gt;Agents are the next version of that mistake.&lt;/p&gt;
&lt;p&gt;The transition from web to mobile required rethinking interaction from scratch. Touch instead of hover. Persistent context instead of long sessions. Teams treating mobile as &amp;ldquo;the web, but smaller&amp;rdquo; shipped products that technically worked and practically failed. The teams that asked &amp;ldquo;how does a mobile user actually behave?&amp;rdquo; built something different.&lt;/p&gt;</description></item></channel></rss>