<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>QuickStyle Blog</title>
    <link>http://localhost:4323/blog</link>
    <atom:link href="http://localhost:4323/rss.xml" rel="self" type="application/rss+xml" />
    <description>Field notes on AI product photography, virtual try-on, and the unglamorous work behind making rendered images sell.</description>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 12:36:38 GMT</lastBuildDate>
    <item>
      <title>AI vs photo studio — the real cost breakdown</title>
      <link>http://localhost:4323/blog/ai-vs-photo-studio-real-cost-breakdown</link>
      <guid isPermaLink="true">http://localhost:4323/blog/ai-vs-photo-studio-real-cost-breakdown</guid>
      <description>We priced 100 SKUs through three production paths: a Brooklyn studio shoot, a freelance photographer, and a QuickStyle render. The rendered numbers will surprise you. The studio numbers won&apos;t.</description>
      <pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate>
      <author>noreply@quickstyle.ai (Adrian Lisko)</author>
      <category>pricing</category>
      <category>ecommerce</category>
      <category>operations</category>
    </item>
    <item>
      <title>How we render scenes in 2.3 seconds</title>
      <link>http://localhost:4323/blog/how-we-render-scenes-in-2-3-seconds</link>
      <guid isPermaLink="true">http://localhost:4323/blog/how-we-render-scenes-in-2-3-seconds</guid>
      <description>Six engineering decisions that took our P50 render time from 11.4 seconds at launch to 2.3 seconds today. None of them are about a faster GPU.</description>
      <pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate>
      <author>noreply@quickstyle.ai (Adrian Lisko)</author>
      <category>engineering</category>
      <category>performance</category>
      <category>rendering</category>
    </item>
    <item>
      <title>Why we don&apos;t watermark free outputs</title>
      <link>http://localhost:4323/blog/why-we-dont-watermark-free-outputs</link>
      <guid isPermaLink="true">http://localhost:4323/blog/why-we-dont-watermark-free-outputs</guid>
      <description>Watermarks tank shareability, train users to perceive your tool as cheap, and push the savvy ones to a competitor in 90 seconds. Three reasons we made the call differently.</description>
      <pubDate>Thu, 19 Mar 2026 00:00:00 GMT</pubDate>
      <author>noreply@quickstyle.ai (Adrian Lisko)</author>
      <category>product</category>
      <category>pricing</category>
      <category>ethics</category>
    </item>
    <item>
      <title>847 stores in 30 days — what we learned</title>
      <link>http://localhost:4323/blog/847-stores-in-30-days-what-we-learned</link>
      <guid isPermaLink="true">http://localhost:4323/blog/847-stores-in-30-days-what-we-learned</guid>
      <description>We onboarded 847 paying stores in our first 30 days post-launch. The data revealed five patterns that completely rearranged what we thought we knew about who buys this category.</description>
      <pubDate>Wed, 04 Mar 2026 00:00:00 GMT</pubDate>
      <author>noreply@quickstyle.ai (Adrian Lisko)</author>
      <category>growth</category>
      <category>research</category>
      <category>ecommerce</category>
    </item>
    <item>
      <title>Why try-on still misses fabric drape (and what to do about it)</title>
      <link>http://localhost:4323/blog/why-tryon-misses-fabric-drape</link>
      <guid isPermaLink="true">http://localhost:4323/blog/why-tryon-misses-fabric-drape</guid>
      <description>The hardest unsolved problem in virtual try-on isn&apos;t pose, fit, or lighting. It&apos;s drape — the way fabric falls under gravity. Here&apos;s why current models can&apos;t render it, and the four workarounds that actually ship.</description>
      <pubDate>Thu, 12 Feb 2026 00:00:00 GMT</pubDate>
      <author>noreply@quickstyle.ai (Adrian Lisko)</author>
      <category>virtual-try-on</category>
      <category>engineering</category>
      <category>research</category>
    </item>
  </channel>
</rss>