<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>Kai Moreno — Journal</title><link>https://epicwebdesignstudio.com/demos/react-folio-pro/journal</link><description>Notes on design, front-end and motion from Kai Moreno.</description><language>en</language><atom:link href="https://epicwebdesignstudio.com/demos/react-folio-pro/feed.xml" rel="self" type="application/rss+xml" />
<item><title>Designing a calm checkout</title><link>https://epicwebdesignstudio.com/demos/react-folio-pro/journal/designing-a-calm-checkout</link><guid isPermaLink="true">https://epicwebdesignstudio.com/demos/react-folio-pro/journal/designing-a-calm-checkout</guid><pubDate>Fri, 12 Sep 2025 09:00:00 GMT</pubDate><description>Five steps became one page. What we removed, what we kept and how we measured it.</description><category>design</category><category>e-commerce</category><content:encoded><![CDATA[<p>A checkout is the one page where visitors are almost done, and where almost every shop loses them. For <a href="https://epicwebdesignstudio.com/demos/react-folio-pro/work/lumen-commerce">Lumen</a> we rebuilt it around one idea: <strong>nothing should ask a question the customer has already answered.</strong></p>
<h2 id="what-we-removed">What we removed</h2>
<ul><li>A separate login step. Guests check out in one go; an account is offered <em>after</em> the order.</li><li>Two address forms. Billing defaults to shipping.</li><li>The cart upsell carousel. It added clicks, not revenue.</li></ul>
<h2 id="what-we-kept">What we kept</h2>
<p>Delivery options stay visible before the address is complete, because surprise costs are the top reason people leave.</p>
<blockquote>Show the total early and keep it honest. Every later change should only ever make the page quieter.</blockquote>
<h2 id="how-we-measured-it">How we measured it</h2>
<p>We ran an A/B test for six weeks against the old five-step flow:</p>
<table><thead><tr><th>Metric</th><th>Old</th><th>New</th></tr></thead><tbody><tr><td>Completion</td><td>41%</td><td>58%</td></tr><tr><td>Median time</td><td>3m 40s</td><td>1m 55s</td></tr><tr><td>Support tickets</td><td>baseline</td><td>-34%</td></tr></tbody></table>
<h3 id="a-small-detail-that-mattered">A small detail that mattered</h3>
<p>Inline validation fires on blur, never while typing. In code it is a few lines:</p>
<pre><code class="language-ts">input.addEventListener(&quot;blur&quot;, () =&gt; validate(input));</code></pre>
<p>Calm is mostly the absence of noise. See the full <a href="https://epicwebdesignstudio.com/demos/react-folio-pro/work/lumen-commerce">case study</a> for the numbers.</p>]]></content:encoded></item>
<item><title>Motion tokens in practice</title><link>https://epicwebdesignstudio.com/demos/react-folio-pro/journal/motion-tokens-in-practice</link><guid isPermaLink="true">https://epicwebdesignstudio.com/demos/react-folio-pro/journal/motion-tokens-in-practice</guid><pubDate>Wed, 02 Jul 2025 09:00:00 GMT</pubDate><description>Duration, easing and distance as design tokens, each with a reduced-motion twin.</description><category>motion</category><category>design systems</category><content:encoded><![CDATA[<p>Colour and spacing have tokens. Motion usually does not, so every animation drifts. For <a href="https://epicwebdesignstudio.com/demos/react-folio-pro/work/orbit-motion">Orbit</a> we made motion a first-class token set.</p>
<h2 id="the-three-numbers">The three numbers</h2>
<p>Every transition is described by a <strong>duration</strong>, an <strong>easing</strong> and a <strong>distance</strong>. Four named combinations cover the whole app:</p>
<ol><li><code>quick</code>: 120 ms, ease-out, 8 px</li><li><code>smooth</code>: 240 ms, ease-in-out, 16 px</li><li><code>slow</code>: 480 ms, ease-in-out, 32 px</li><li><code>celebrate</code>: 700 ms, spring, 48 px</li></ol>
<h2 id="reduced-motion-is-part-of-the-token">Reduced motion is part of the token</h2>
<p>Each token has a twin that respects <code>prefers-reduced-motion</code>: the distance becomes zero and only opacity changes.</p>
<pre><code class="language-css">:root { --move-smooth: 240ms cubic-bezier(.4,0,.2,1); }
@media (prefers-reduced-motion: reduce) { :root { --move-smooth: 1ms linear; } }</code></pre>
<h2 id="test-on-the-oldest-phone-you-support">Test on the oldest phone you support</h2>
<p>If an animation drops frames on a five-year-old device, shorten it or remove it. Tokens make that a one-line change.</p>]]></content:encoded></item>
<item><title>Performance budgets in CI</title><link>https://epicwebdesignstudio.com/demos/react-folio-pro/journal/performance-budgets-in-ci</link><guid isPermaLink="true">https://epicwebdesignstudio.com/demos/react-folio-pro/journal/performance-budgets-in-ci</guid><pubDate>Fri, 18 Apr 2025 09:00:00 GMT</pubDate><description>A budget nobody enforces is a wish. How we made the build fail when a page got slower.</description><category>performance</category><category>front-end</category><content:encoded><![CDATA[<p>We set three budgets for every page: <strong>JavaScript</strong>, <strong>largest contentful paint</strong> and <strong>layout shift</strong>. They live in a file next to the code.</p>
<h2 id="the-budget-file">The budget file</h2>
<pre><code class="language-json">{ &quot;js&quot;: &quot;170kB&quot;, &quot;lcp&quot;: &quot;2.0s&quot;, &quot;cls&quot;: 0.05 }</code></pre>
<h2 id="make-it-fail-loudly">Make it fail loudly</h2>
<p>The pipeline runs Lighthouse on a throttled profile and compares each metric with the budget. A page over budget fails the build and prints which asset grew.</p>
<h2 id="rules-we-follow">Rules we follow</h2>
<ul><li>Images are sized and lazy-loaded below the fold.</li><li>Third-party scripts need a written reason.</li><li>A budget can be raised only in a pull request that says why.</li></ul>
<p>The result for <a href="https://epicwebdesignstudio.com/demos/react-folio-pro/work/verdant-site">Verdant</a> was a Lighthouse score of 100 that stayed 100 for a year.</p>]]></content:encoded></item>
<item><title>What I learned redesigning a bank app</title><link>https://epicwebdesignstudio.com/demos/react-folio-pro/journal/redesigning-a-bank-app</link><guid isPermaLink="true">https://epicwebdesignstudio.com/demos/react-folio-pro/journal/redesigning-a-bank-app</guid><pubDate>Thu, 20 Feb 2025 09:00:00 GMT</pubDate><description>Twelve navigation items to four, and the lessons that came with it.</description><category>product</category><category>design systems</category><content:encoded><![CDATA[<p>When two million people already use your app, every change is a negotiation with their habits. These are the notes I wish I had on day one of <a href="https://epicwebdesignstudio.com/demos/react-folio-pro/work/northwind-app">Northwind</a>.</p>
<h2 id="count-the-destinations">Count the destinations</h2>
<p>We listed every place a user could go. There were twelve. Card sorting with forty customers showed they thought in <strong>tasks</strong> (pay, save, borrow, get help), not in features.</p>
<h2 id="move-slowly-measure-every-step">Move slowly, measure every step</h2>
<p>We rolled out to 5%, then 25%, then everyone. At each step we tracked task completion, not satisfaction scores.</p>
<h2 id="build-the-system-alongside-the-screens">Build the system alongside the screens</h2>
<p>Tokens and components were built in Figma and React at the same time, so design and code never drifted.</p>
<p>Task completion rose 31% and new screens now ship in half the time.</p>]]></content:encoded></item>
</channel>
</rss>
