<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>FitKind Blog</title>
    <description>Insights on workout tracking, serious training, and the product decisions behind FitKind.</description>
    <link>https://fitkind.app/blog/</link>
    <language>en-GB</language>
  <item>
    <title>Why Training Load Needs Context, Not Theatre</title>
    <link>https://fitkind.app/blog/why-training-load-needs-context-not-theatre/</link>
    <guid>https://fitkind.app/blog/why-training-load-needs-context-not-theatre/</guid>
    <pubDate>Sat, 04 Apr 2026 00:00:00 GMT</pubDate>
    <description>A single load number is only useful when it helps you decide what to do next. FitKind treats training load as a decision aid, not a dashboard prop.</description>
  </item>
  <item>
    <title>What FitKind Beta Testers Are Actually Shaping</title>
    <link>https://fitkind.app/blog/what-beta-testers-are-actually-shaping/</link>
    <guid>https://fitkind.app/blog/what-beta-testers-are-actually-shaping/</guid>
    <pubDate>Fri, 03 Apr 2026 00:00:00 GMT</pubDate>
    <description>The beta is not a vanity waitlist. It is where we pressure-test the details that decide whether FitKind feels sharp or forgettable in daily training.</description>
  </item>
  <item>
    <title>Why FitKind Starts Offline-First</title>
    <link>https://fitkind.app/blog/why-fitkind-starts-offline-first/</link>
    <guid>https://fitkind.app/blog/why-fitkind-starts-offline-first/</guid>
    <pubDate>Thu, 02 Apr 2026 00:00:00 GMT</pubDate>
    <description>Most workout apps assume perfect signal and casual use. FitKind starts from the opposite assumption: serious training, patchy gym reception, and zero patience for lost logs.</description>
  </item>
  </channel>
</rss>