<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>FlowDrop Blog</title>
		<description>Updates, tutorials, and deep-dives from the FlowDrop team.</description>
		<link>https://flowdrop.io/blog</link>
		<atom:link href="https://flowdrop.io/rss.xml" rel="self" type="application/rss+xml"/>
		<language>en-us</language>
		<lastBuildDate>Fri, 12 Jun 2026 20:20:20 GMT</lastBuildDate>
		
		<item>
			<title><![CDATA[Introducing FlowDrop 1.0]]></title>
			<description><![CDATA[A visual workflow editor that your backend can own. Today we're releasing FlowDrop 1.0 — a drop-in, backend-agnostic component for building AI workflow UIs.]]></description>
			<link>https://flowdrop.io/blog/introducing-flowdrop-1-0</link>
			<guid isPermaLink="true">https://flowdrop.io/blog/introducing-flowdrop-1-0</guid>
			<pubDate>Wed, 11 Mar 2026 00:00:00 GMT</pubDate>
			<category>release</category>
			<category>announcement</category>
		</item>

		<item>
			<title><![CDATA[Why Your AI Workflow Tool Should Be Backend-Agnostic]]></title>
			<description><![CDATA[Most AI workflow tools ship with their own cloud backend. Here's why that's a problem — and what a better approach looks like.]]></description>
			<link>https://flowdrop.io/blog/building-ai-workflows-backend-agnostic</link>
			<guid isPermaLink="true">https://flowdrop.io/blog/building-ai-workflows-backend-agnostic</guid>
			<pubDate>Mon, 09 Mar 2026 00:00:00 GMT</pubDate>
			<category>architecture</category>
			<category>ai</category>
			<category>opinion</category>
		</item>
	</channel>
</rss>