Framer vs Rive

Agent ops

1. ai-native userAn agent can create or modify designs programmatically — through a write-capable API, plugin surface, or MCP tools — not just read them

   weight 2 · round drawn
   Framer✓fullclaimed8/10

   Framer documents a write-capable external agent connection (Claude Code, Cursor, Codex) that can create/update/delete CMS items and modify canvas/components, backed by branching for safe review, plus a plugin surface and Server API for programmatic site automation. Missing for 10: independent/hands-on verification of the external-agent write capability and no public OpenAPI/formal API schema was found by the probe.

   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”

   proof ↗⚑ flag

   Rive✓fullprobed8/10

   Rive documents an MCP integration letting AI tools create/modify complex View Models, State Machines, Layouts, and Shapes directly in the Editor, plus RML (a text-based file format) explicitly designed so coding agents can build/modify Rive files programmatically, and a CLI for agent-driven generation. This goes beyond read-only access into genuine write-capable agent tooling. Missing for 10: independent/hands-on verification of the MCP tools working in practice and more detail on the write-scope limits of the MCP server.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

2. ai-native userAn agent can render and export designs — screenshots, images, or production formats — through a documented programmatic surface

   weight 2 · round to Rive
   Framer—none0/10

   Evidence covers AI agents editing designs, CMS, and publishing via a Server API and external-agent connections, but nothing documents a programmatic render/export surface for screenshots, images, or production-format exports (no export/render API endpoints, and probes for OpenAPI specs all 404).

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Rive!disputedcontradicted4/10

   Rive's runtimes expose a documented programmatic Renderer interface (rive-gh-1/2/3) and RML lets code/agents construct .riv content (rive-docs-13/20/25), and export docs describe exporting to 'websites, mobile apps, games, videos' (rive-docs-7/8) — suggesting a programmatic render/export surface. However, hands-on community feedback directly contradicts image/video export capability: users report 'no way to export movie files' and ask 'can I export video assets with this!?' with no answer (rive-comm-3, rive-comm-10), indicating the actual exportable surface is limited to the .riv runtime format rather than screenshots/images/production video as the story requires. Missing for 10: documented API/CLI for agent-triggered screenshot or image/video export, and confirmation this gap has been resolved.

   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   proof ↗⚑ flag

3. ai-native userMy coding agent can pull real design context — frames, variables, screenshots, component mappings — through an MCP server or API to implement the design

   weight 3 · round to Framer
   Framer~partialclaimed7/10

   Framer explicitly markets a native 'External Agent' connection (explicitly positioned as replacing a separate MCP server) that gives coding agents like Claude Code, Cursor, and Codex direct access to canvas, components, CMS, and project context, including read/write CMS operations and branch-based change tracking. This closely matches the story's intent of pulling design context to implement changes, but the specific mention of 'screenshots' and 'variables' from the story isn't explicitly evidenced, and all evidence is first-party docs with no independent/hands-on corroboration of the external agent workflow. Missing for 10: explicit support for screenshots/variables extraction, independent developer confirmation of the external-agent integration working as described.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”

   proof ↗⚑ flag

   Rive~partialprobed5/10

   Rive documents an official MCP server connecting the Editor to AI tools, letting agents create/modify View Models (variable-like data), State Machines, Layouts, and Components (rive-docs-19, rive-docs-27, rive-docs-10, rive-docs-11). This covers some 'design context' elements (component mappings, variables via view models) but is framed as agents building/editing Rive content rather than pulling existing frames or screenshots for implementation elsewhere. Missing for 10: explicit screenshot/frame extraction capability, evidence of pulling existing design context (vs. generating new), and independent/hands-on confirmation of the MCP workflow.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Framer
   Framer✓fullprobed8/10

   A direct probe confirms Framer serves a live llms.txt file (HTTP 200) with structured content describing the product and linking to migration/agent docs, and Framer's own docs explicitly reference this file's content, giving concrete first-party evidence an AI agent can be pointed at it. missing for 10: independent/third-party confirmation that agents successfully consume this llms.txt in practice, and broader agent-oriented doc coverage beyond this single file.

   • [probe] “PROBE llms.txt: HTTP 200 at https://www.framer.com/llms.txt # Framer > Framer is an AI website builder for designers and teams. Generate ed…”
   • [claimed-docs] “Switch to Framer](https://www.framer.com/switch/?md): Migration from another builder.”
   • [claimed-docs] “Framer allows you to host static files directly on your site or custom domain. This feature is available on the **Pro**, **Enterprise**, and…”

   proof ↗⚑ flag

   Rive✓fullprobed7/10

   Rive's docs are served in agent-friendly markdown (docs/*.md return 200) and explicitly point agents to a documentation index at https://rive.app/docs/llms.txt for full-site context, satisfying the 'point an agent at llms.txt or agent-oriented docs' story even though the conventional root-level /llms.txt path 404s. Missing for 10: direct confirmation that /docs/llms.txt itself loads and contains a complete index, and no independent (non-vendor) corroboration of an agent successfully using it.

   • [probe] “PROBE llms.txt: HTTP 404 at https://rive.app/llms.txt”
   • [probe] “PROBE docs-md: HTTP 200 at https://rive.app/docs/getting-started/introduction.md > ## Documentation Index > Fetch the complete documentation…”
   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Rive
   Framer~partialprobed3/10

   Framer advertises a Server API to 'automate publishing' and integrate with external products/agents, which implies some programmatic/headless control, but there is no documented CLI, headless mode, or CI-specific workflow, and probes show no OpenAPI/API spec is publicly discoverable (404s). Missing for 10: concrete CI/headless setup docs, API reference/spec, and evidence of automated pipeline usage beyond marketing blurbs.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Rive~partialclaimed4/10

   Rive exposes open-source runtimes as libraries (rive-gh-1, rive-docs-21) and mentions a CLI for agent-driven generation and RML for text-based/coding-agent workflows (rive-docs-26, rive-docs-25, rive-docs-30), suggesting some scriptable/automatable path outside the interactive editor. However, there is no explicit documentation of headless rendering, CI pipeline integration, or automated test/build usage of the CLI or runtimes. Missing for 10: explicit headless/CI usage docs, CLI reference/flags, examples of automated pipeline integration, independent confirmation of non-interactive operation.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Rive
   Framer—none0/10

   Framer explicitly states it does not use or require MCP: 'Framer doesn't require a separate MCP server... without manual MCP setup' (framer-docs-34). Its actual capability runs in the opposite direction — external agents like Claude Code/Cursor connect INTO Framer to use Framer's canvas/CMS as their tool, not Framer consuming external MCP servers' tools. No evidence exists of Framer acting as an MCP client that plugs in third-party MCP servers.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”

   proof ↗⚑ flag

   Rive✓fullprobed7/10

   Rive documents a first-party MCP integration letting users connect the Rive Editor to AI tools via MCP so AI can perform tasks like creating View Models, State Machines, Layouts, and Shapes, confirmed by both docs and a dedicated probe. Missing for 10: independent/hands-on verification of the MCP integration working in practice and details on which MCP clients/servers are supported beyond the editor's own tools.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Rive
   Framer—none0/10

   Framer explicitly states it does not offer an MCP server, instead providing a proprietary 'External Agent connection' as an alternative to MCP (framer-docs-34). Since the story specifically asks for an official MCP server, and Framer's own docs assert this is unnecessary and unsupported by design, there is no evidence of an actual MCP server implementation.

   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”

   proof ↗⚑ flag

   Rive✓fullprobed8/10

   Rive's docs explicitly describe an official MCP server that connects the Rive Editor to AI agents/tools, letting AI handle View Models, State Machines, Layouts, Shapes, etc., and this is confirmed via a dedicated docs page and probe. Missing for 10: independent/hands-on third-party verification of the MCP server working in practice beyond first-party docs.

   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Rive
   Framer—none0/10

   Evidence shows Framer offers a Server API, plugins, and 'External Agent' connections for tools like Claude Code/Cursor/Codex, but nowhere does it mention an official Framer CLI tool for AI-native workflows.

   ⚑ flag

   Rive~partialclaimed3/10

   The Rive homepage claims users can 'let an agent generate them with the CLI' (rive-docs-26), indicating an official CLI exists for AI-agent workflows, but no other evidence pack item documents CLI installation, commands, or usage — most AI-agent tooling evidence instead centers on the MCP server and in-editor AI agent, not a standalone CLI. Missing for 10: dedicated CLI docs/reference, install instructions, command examples, and independent/hands-on corroboration of the CLI working.

   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”

   proof ↗⚑ flag

6. ai-native userDrive the product through a documented public API

   weight 3 · round to Rive
   Framer~partialprobed6/10

   Framer documents a Server API for automation/publishing and CMS API access, and explicitly supports external AI agents (Claude Code, Cursor, Codex) reading/writing CMS collections via a documented connection flow (framer-docs-5,17,30,39,40,18,24,34). However, probes could not locate any formal API reference/spec (openapi.json/swagger 404s) or detailed endpoint documentation, and there's no independent/community corroboration of developers actually using the Server API. Missing for 10: a discoverable formal API reference/spec, authentication/rate-limit details, and independent developer testimonials confirming API usability.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Rive✓fullprobed8/10

   Rive documents open-source runtime APIs (web, mobile, game engines) for loading and controlling animations programmatically (rive-docs-21, rive-gh-1, rive-docs-14/15), plus a text-based file format (RML) explicitly designed for coding agents and automated workflows (rive-docs-13, 20, 25, 30), and an official MCP server/AI agent integration for driving the Editor via AI tools (rive-docs-19, 27, rive-probe-4, rive-docs-9/18). Together these give an AI-native user multiple documented, agent-friendly ways to control the product beyond the GUI. Missing for 10: a formal REST/OpenAPI-style public API (probe shows 404s for openapi/swagger endpoints) and independent third-party corroboration of programmatic API usage.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Rive
   Framer~partialprobed6/10

   Framer documents a Server API, plugin SDK, code components/overrides, and an external agent connection for building integrations against official interfaces, but there's no discoverable OpenAPI spec (probe found 404s across candidate paths) and no independent/hands-on developer corroboration of building against these SDKs. missing for 10: publicly discoverable API reference/OpenAPI spec, independent developer corroboration, SDK versioning/language support details.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive documents open-source official runtimes (SDKs) for web, mobile, game engines, and other platforms, with a public GitHub repo (rive-runtime) implementing the loading/rendering API, plus explicit guidance on caching and using the same exported .riv file across supported runtimes. This directly satisfies 'build against official SDKs' for developers, including AI-native workflows via RML/MCP integration for programmatic file creation. Missing for 10: independent third-party corroboration of SDK quality/completeness across all listed platforms and more granular per-language SDK documentation (e.g., npm/Swift/Kotlin package specifics).

   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Framer—none0/10

   Evidence covers Framer's Server API, external agent connections, and plugins, but there is no mention of webhooks or event subscription mechanisms anywhere in the docs or probes; OpenAPI probe also returned 404s with no webhook spec found.

   ⚑ flag

   Rive—none0/10

   No evidence anywhere in the pack mentions webhooks, event subscriptions, or any push-notification API for Rive; the product is documented as a design/animation tool with editor, runtime, and MCP/AI-agent integrations, none of which reference webhook-based event delivery.

   ⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Framer
   Framer~partialclaimed4/10

   Framer offers a Server API to 'automate publishing' and lets external agents (Claude Code, Cursor, Codex) connect to read/write CMS and canvas content, which could be wired into autonomous workflows, but all documented agent interactions (framer-docs-6/7/26) are conversational/on-demand rather than scheduled or self-running background automations. There's no evidence of triggers, schedules, or persistent background jobs — only API/connection primitives a developer would need to build such automation themselves. missing for 10: evidence of scheduled/triggered background jobs, autonomous run history or logs, native workflow/automation builder distinct from on-demand AI agent editing.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project from the tools you already us…”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”

   proof ↗⚑ flag

   Rive—none0/10

   Rive's docs describe an AI agent, MCP integration, and CLI that generate animations/code when invoked by a user, but there is no evidence of scheduled, unattended, or continuously running background automations — all AI features described are user-triggered, session-based interactions within the Editor.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

2. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Rive
   Framer✓fullclaimed7/10

   Framer ships multiple built-in AI agents (design agent, CMS agent, AI website generator) that users can delegate tasks to directly inside the product via natural-language prompts (e.g. 'make responsive', 'switch to dark mode', CMS setup) as shown in framer-docs-6,7,8,26,42,43,44,45,46. Missing for 10: independent/hands-on user reports specifically validating the built-in AI assistant's reliability and quality (community evidence available only covers older, unrelated Framer features like animations).

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Manage more. Publish faster. The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content …”

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive documents a built-in AI agent inside the Editor that writes code, generates layouts, data models, view models, state machines, and animation, letting users delegate repetitive/complex tasks to it directly within the product. This is first-party documented with specific task examples, though there's no independent/hands-on corroboration of its real-world effectiveness. Missing for 10: independent verification of the AI agent's actual capability/reliability, more detail on scope/limits of delegation.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Framer
   Framer✓fullclaimed8/10

   Framer's docs show extensive natural-language operation: the built-in AI agent creates pages/sections/copy from prompts, restyles sites ('switch to dark mode', 'use Fraunces/Inter'), reorganizes layouts, and makes sites responsive purely from described intent, plus a CMS agent and external-agent integration (Claude Code/Cursor/Codex) that reads/writes CMS and canvas content via natural language, with branch-based safety for changes. missing for 10: independent/hands-on third-party corroboration of the AI/CMS agent actually working as described (community evidence only covers older non-AI Framer features).

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “The CMS agent sets up, organizes, and updates your entire CMS, connecting it directly to the canvas so content and design stay in sync.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Reorganize the homepage flow based on conversion best practices. Move social proof higher, put pricing before the FAQ”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”

   proof ↗⚑ flag

   Rive~partialprobed6/10

   Rive documents a built-in AI agent and MCP integration that let users describe tasks in natural language to generate ViewModels, state machines, layouts, and animation code, plus a CLI for agent-driven generation (rive-docs-9,10,18,19,26,27). However, this is entirely first-party documentation with no independent or hands-on confirmation that natural-language commands reliably drive the full editor experience, and community feedback focuses on pricing/licensing rather than the AI agent's real-world behavior. Missing for 10: independent/hands-on verification of the AI agent's natural-language command success, broader coverage beyond docs-based claims, and detail on command scope/limits.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Framer—none0/10

   Framer documents a Server API, Plugins API, and Code Components, but nothing shows an interactive API reference with runnable/try-it examples; probe evidence explicitly found no OpenAPI/swagger spec (404s at all candidate paths), suggesting no such interactive reference exists.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Rive—none0/10

   While Rive has extensive documentation (runtime parameters, data binding, RML), there is no evidence of an interactive API reference with runnable/live code examples, and the OpenAPI probe returned 404s with no playground or sandbox mentioned.

   • [claimed-docs] “Caching a Rive file: Load the .riv into memory once, use it multiple times.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Framer—none0/10

   Framer offers a Server API and llms.txt, but the probe explicitly found no OpenAPI/swagger spec at any standard location, and no docs mention a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”
   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”

   proof ↗⚑ flag

   Rive—none0/10

   A direct probe for OpenAPI/swagger spec endpoints (openapi.json, swagger.json, etc.) returned 404 for all candidates, and no docs mention a machine-readable API spec being downloadable.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Framer—none0/10

   No evidence of API versioning scheme or a documented deprecation policy; probes for OpenAPI specs returned 404s and the Server/Fetch API docs mention no versioning or deprecation terms.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Rive—none0/10

   No evidence of any versioned API scheme or documented deprecation policy for Rive's runtimes, editor APIs, or MCP integration; OpenAPI probes returned 404s and no changelog/versioning docs are cited.

   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”

   proof ↗⚑ flag

Ai

1. designerBuilt-in AI handles asset chores — image generation, background removal, content-aware fills, copy suggestions — inside the editor

   weight 1 · round to Framer
   Framer~partialclaimed3/10

   Framer's AI agent can generate pages, sections, copy, and visuals (framer-docs-6, framer-docs-26, framer-docs-42) and adjust layout/typography, which touches copy suggestions and some visual generation, but there is no evidence of dedicated asset-chore tools like image generation, background removal, or content-aware fill inside the editor. missing for 10: dedicated image generation tool, background removal feature, content-aware fill capability, hands-on/independent verification of these specific asset tools.

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”

   proof ↗⚑ flag

   Rive—none0/10

   Rive's AI agent/MCP tooling is focused on generating code, view models, state machines, layouts, and animation logic — not on image generation, background removal, content-aware fill, or copy suggestions for asset creation. No evidence names any of these specific asset-chore AI features; missing for 10: image generation, background removal, content-aware fill, copy/text suggestions.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

2. designerGenerate or edit designs from a natural-language prompt — first drafts, layouts, or full mockups the tool actually produces

   weight 2 · round to Framer
   Framer✓fullclaimed8/10

   Framer's docs describe a native AI agent that generates editable pages, sections, copy, and visuals from prompts, with examples of full mockup edits (typography, grid layouts, brand colors, dark mode, responsive breakpoints, image-based starting points), and lets designers keep refining in canvas after generation. This directly matches the story of prompt-driven first drafts/layouts/mockups, though evidence is entirely vendor-sourced with no independent hands-on verification of AI-generation quality — missing for 10: independent/hands-on confirmation that generated designs are production-quality, and any documented limitations of the AI design agent.

   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project.”
   • [claimed-docs] “Describe the look you want. The agent takes care of colors, fonts, component styles, motion and effects across your site.”
   • [claimed-docs] “Framer’s AI agent creates editable pages, sections, copy, and visuals directly in your project. Keep refining in the conversation, or take o…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”
   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Drop in images or share a URL and the agent uses it as a starting point. The layout, style, and feel of your reference, brought directly ont…”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “Reorganize the features section from a list layout to a 2x3 grid of feature cards.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”

   proof ↗⚑ flag

   Rive~partialprobed6/10

   Rive documents an AI agent/MCP integration that generates View Models, State Machines, Layouts, Shapes and animation from prompts or via coding-agent workflows, and even an 'agent generate them with the CLI' claim on the homepage — this matches the story's spirit of prompt-driven first drafts. However, all evidence is first-party docs describing 'the first set of tools' as handling repetitive tasks rather than full end-to-end mockup generation, and there's no independent/hands-on corroboration of output quality. Missing for 10: independent or hands-on validation of AI-generated designs, clearer evidence of full mockup/layout generation (not just repetitive sub-tasks) from a single prompt.

   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Framer~partialclaimed6/10

   Framer docs show AI-agent driven bulk operations such as site-wide typography/color/theme changes across all pages (framer-docs-19,27,37), CSV bulk import of CMS collections with row-level linking (framer-docs-9,21), and external agents able to create/update/delete many CMS items via API (framer-docs-18,24,35). This supports bulk operations across many items in CMS/design contexts, but there's no documentation of scale limits, batch API endpoints, or performance at large volumes. Missing for 10: explicit bulk/batch API documentation with scale guarantees, independent verification of bulk operations succeeding at scale, and rate-limit/performance details.

   • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”
   • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”

   proof ↗⚑ flag

   Rive~partialclaimed6/10

   Rive documents an AI agent/MCP integration explicitly designed to let AI 'handle repetitive tasks, like creating complex View Models, State Machines with hundreds of states/layers, Layouts, Shapes, and more,' and RML provides a text-based file format enabling coding agents to script bulk edits outside the Editor. Components/instances also let one source change propagate across many instances. However, there's no independent/hands-on evidence of actual bulk-operation performance at scale, no documented API for batch scripting beyond RML/MCP, and no benchmarks or examples of large-scale bulk edits succeeding. Missing for 10: independent verification of bulk-task performance, concrete examples/benchmarks of large-scale batch operations, and a documented API/CLI for scripted bulk edits beyond the AI agent's stated purpose.

   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Rive
   Framer—none0/10

   Evidence shows Framer's API, plugins, and AI agents that can be manually invoked to modify a site, and an API to 'automate publishing,' but nothing describes a rule engine or event-trigger system where a user defines 'when X happens, do Y' automation. missing for 10: any event-trigger/rule definition mechanism, conditional logic, or workflow automation builder within Framer.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”

   proof ↗⚑ flag

   Rive~partialclaimed4/10

   Rive's State Machines and data-binding docs imply event-driven behavior (inputs, user actions, and data changes automatically triggering animation/state updates), and its AI Agent/MCP tooling can generate these State Machines and scripting-based behaviors programmatically. However, there's no explicit documentation of a rule-authoring system (e.g., conditional 'if event then action' automation) framed for AI-native/automation use beyond interactive animation triggers. Missing for 10: explicit rule-definition API/interface for arbitrary automation, examples of AI-native users authoring trigger-action rules, and independent confirmation beyond first-party docs.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Use scripting to create custom interactions, procedural animation, and behaviors that go beyond the built-in tools.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”

   proof ↗⚑ flag

3. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Framer
   Framer✓fullclaimed8/10

   Framer documents automatic version history with instant rollback, plus branching that isolates every external-agent change so it can be reviewed, undone, or merged — directly matching version/review/rollback for automations run by AI agents. Missing for 10: independent/hands-on confirmation of rollback and branch-merge workflows in practice, and detail on granular diff/review UI beyond marketing docs.

   • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “Staging environments. Test changes securely on a framer.app domain before pushing live.”

   proof ↗⚑ flag

   Rive~partialclaimed4/10

   Rive's Revision History provides automatic tracking of changes, previewing of past revisions, and non-destructive rollback to prior versions of a file (rive-docs-12, rive-docs-17, rive-docs-29), which covers version/rollback for the design file itself. However, the story targets 'automations' (AI-agent/MCP-driven workflows), and there is no evidence of versioning, diffing, or review specifically for AI-generated scripts, MCP actions, or automation pipelines — only generic file revision history. Missing for 10: dedicated versioning/review/rollback for AI-agent or MCP-generated automations, audit trail of agent actions, diff/compare tooling, and any independent confirmation of this workflow in practice.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

Collaboration

1. product managerComment directly on designs, mention teammates, and resolve threads so review happens in the file, not in email

   weight 2 · round drawn
   Framer—none0/10

   Evidence covers branching, version history, AI agents, CMS, and plugins, but nothing about in-file commenting, @mentions of teammates, or resolving comment threads for design review. Missing for 10: any mention of a commenting feature, mention/notification system, or thread resolution workflow.

   ⚑ flag

   Rive—none0/10

   Evidence covers animation, data binding, revision history, AI/MCP tooling, and export, but there is no mention of commenting, @mentions, or thread resolution features in Rive's editor. Revision history tracks changes but is not a comment/review workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag

2. designerMy whole team can edit the same file simultaneously with live cursors and instant sync

   weight 3 · round to Rive
   Framer—none0/10

   The evidence pack includes docs on branching, version history, and staging (framer-docs-11, framer-docs-47) but contains no mention of real-time multiplayer editing, live cursors, or instant sync between simultaneous editors — the actual claim in the story. Missing for 10: any documentation of live cursors, simultaneous multi-user canvas editing, or real-time presence indicators.

   ⚑ flag

   Rive~partialclaimed4/10

   Docs confirm multiple people can work on the same file simultaneously with all changes tracked in Revision History, implying some multiplayer support, but there is no mention of live cursors, presence indicators, or real-time instant sync mechanics that the story specifically asks for. Missing for 10: explicit live cursor/presence UI, real-time sync latency claims, independent hands-on confirmation of simultaneous editing experience.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag

Design systems

1. designerManage design tokens or variables — colors, spacing, typography — with modes or themes applied across designs

   weight 2 · round drawn
   Framer—none0/10

   Evidence shows Framer's AI agent can restyle colors/typography/light-dark mode on request (framer-docs-27, framer-docs-37, framer-docs-19), but there is no documentation of an actual design-token or variables system with reusable modes/themes applied consistently across designs, akin to Figma variables. Missing for 10: token/variable definition, mode-based theme switching infrastructure, cross-file/theme propagation evidence.

   • [claimed-docs] “Switch the site from light mode to dark mode with dark backgrounds, light text, and updated component colors throughout.”
   • [claimed-docs] “Update the entire site to use our new brand colors: primary #1A1A2E, accent #E94560, and light background #F5F5F5.”
   • [claimed-docs] “Update the entire site’s typography. Use Fraunces for headings and Inter for body text.”

   proof ↗⚑ flag

   Rive—none0/10

   Rive is an animation/interactive-graphics tool with components, data binding, and view models, but there is no evidence of a design-tokens/variables system (colors, spacing, typography) with modes/themes applied across designs — the closest concepts (components, data binding) address reusability and runtime data, not token/theme management. Missing for 10: token or variable definitions, theme/mode switching, cross-design application of shared style values.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

2. designerBuild reusable components with variants and per-instance overrides that stay linked to their source

   weight 3 · round to Rive
   Framer~partialclaimed3/10

   Evidence only touches tangentially on component reuse — Code Components with visual controls and Code Overrides (HOCs to modify Layer/Component properties) hint at reusable, overridable components, but nothing explicitly describes variants or per-instance overrides that stay linked to a master component/source as in a design-system workflow. Missing for 10: explicit documentation of component 'variants', proof that per-instance overrides remain linked/syncable to the source component, and any hands-on/community confirmation of this specific workflow.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive's docs directly describe Components as reusable artboards where instances can be customized while changes to the source component propagate to all instances, matching the story's core requirement of variants/overrides linked to source. Missing for 10: no independent/hands-on corroboration of override behavior at scale, and no detail on variant-specific overrides beyond basic customization examples.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

3. designerShared libraries publish components and styles across files and projects, with controlled updates when the source changes

   weight 2 · round drawn
   Framer—none0/10

   Framer's evidence covers code components, plugins, branching, and CMS collections within a single project, but there is no documentation of a shared/team library mechanism that publishes components or styles across separate files or projects with controlled update propagation (the Figma-style library model). Missing for 10: any mention of a cross-project component/style library, library publishing workflow, or update-notification/accept-update mechanism.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”

   proof ↗⚑ flag

   Rive—none0/10

   Rive's docs describe components/instances reused within a single Rive file where changes to a source component propagate to instances (rive-docs-11, rive-docs-28), but there is no evidence of a shared-library system that publishes components/styles across separate files or projects with controlled update propagation, which is the core of this story. Missing for 10: cross-file/cross-project library publishing, subscribing to a library, and controlled update notifications when a source library changes.

   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”

   proof ↗⚑ flag

Handoff

1. developerDesigns map to production code — component-to-code mappings or direct design-to-code output I can actually ship

   weight 2 · round to Rive
   Framer~partialcommunity7/10

   Framer supports genuine dev-facing code integration: Code Components (custom React components with visual controls), Code Overrides (HOCs), a Server API, and native external-agent access letting Claude Code/Cursor/Codex read/write the live project and CMS with branch-based review before merge. Community evidence corroborates that Framer's React-based model lets designers hand off working code to developers. However this is not a classic 'export design to code' pipeline (no Figma-style code export or OpenAPI-documented flow was found), and independent verification is thin/dated. missing for 10: independent hands-on proof of shipping exported production code, more recent community validation of the external-agent/dev handoff workflow.

   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Connect Claude Code, Codex, or Cursor to update a Framer project.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, and decide when to merge …”
   • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”

   proof ↗⚑ flag

   Rive✓fullclaimed8/10

   Rive's core value prop is explicitly design-to-shippable-runtime: 'No mockups, no prototypes, no handoff... What you build in the editor is what ships in your app, game, or website' (rive-docs-23), backed by real runtime libraries that load .riv files directly into apps/games/web (rive-gh-1, rive-docs-21), reusable components/instances (rive-docs-11, rive-docs-28), and RML text representation enabling coding-agent-driven file construction (rive-docs-13, rive-docs-25, rive-docs-30). This is a genuine direct design-to-production path rather than a code-generation handoff, and MCP/AI agent tooling further bridges design and code workflows (rive-docs-9, rive-docs-19, rive-docs-27). Missing for 10: independent developer case studies confirming the 'no handoff' claim holds up in large production codebases, and clearer detail on how designers' Rive files integrate with existing component libraries/design systems in code.

   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “Create a component once, then use customized instances of it throughout your Rive file. Changes made to the source component are reflected a…”
   • [claimed-docs] “Components are reusable artboards. Create a component once, then use customized instances of it throughout your Rive file. Changes made to t…”
   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Framer
   Framer~partialprobed6/10

   Framer exposes a Server API, external-agent connections (Claude Code/Cursor/Codex) with read/write CMS access, branching for review, and a plugin system that covers many editor actions (framer-docs-5,17,18,24,34,35,36) — a real, substantive API surface for automation. But there's no evidence of full UI/API parity: no OpenAPI/spec discoverable (framer-probe-3 shows 404s across candidate spec paths), and the docs describe specific supported actions (CMS CRUD, canvas edits via agent, publishing) rather than a claim that literally everything achievable in the UI (e.g. fine-grained styling, animation editing, plugin marketplace management) is scriptable via API. Missing for 10: a documented comprehensive API/OpenAPI reference proving parity, explicit vendor claim of 'anything in UI = anything via API', and independent/hands-on verification of that parity.

   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Use the Server API to bring Framer into your product, or connect an external agent to work on a Framer project”
   • [claimed-docs] “Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items.”
   • [claimed-docs] “Framer doesn’t require a separate MCP server. If you’re searching for a Framer MCP, the native Framer External Agent connection gives Claude…”
   • [claimed-docs] “Yes. Once connected, the agent can read and write CMS collections, including creating, updating, and deleting items. You stay in control of …”
   • [claimed-docs] “Framer has branching, so every change made by an external agent automatically happens on a branch. You can undo changes, review the branch, …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.framer.com/openapi.json, https://www.framer.com/swagger.json, https://www.framer.com/api…”

   proof ↗⚑ flag

   Rive~partialprobed5/10

   Rive offers RML (text-based file format) and an MCP server that let AI/coding agents create View Models, State Machines, Layouts, and Shapes programmatically, plus open-source runtimes for playback/control — but the evidence pack does not confirm full parity with the Editor UI (e.g., no OpenAPI/REST API, no confirmation that timeline keyframing, revision history management, or component/instance authoring can be done entirely via API/CLI). missing for 10: a documented public REST/OpenAPI API surface, confirmation that all editor features (keyframe timelines, revision history, component instancing) are scriptable/API-accessible, and independent hands-on verification that AI/API workflows match UI capability.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol).”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “You can connect the Rive Editor to AI tools through MCP (Model Context Protocol). The first set of tools are designed to let AI handle repet…”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [probe] “official MCP server documented at https://rive.app/docs/editor/ai/mcp”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rive.app/openapi.json, https://rive.app/swagger.json, https://rive.app/api/openapi.json, htt…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Rive
   Framer—none0/10

   Evidence shows Framer offers a Server API, CMS API, and CSV import for content, but nothing indicates the ability to export a full site (design, code, CMS data) into open, portable formats for migration away from Framer; only 'migrate to Framer' flows are documented, not exit/export paths.

   • [claimed-docs] “Added two linked collections: 1. Articles — 39 CSV rows imported. 2. Categories — 10 rows added and linked to Articles as multi-select tags.”
   • [claimed-docs] “use-cases.csv to create Use Case Articles and Categories collections. Populate fields and match each article to a category.”
   • [claimed-docs] “Server API Connect your product and automate publishing with the Framer API.”
   • [claimed-docs] “Connect your product and automate publishing with the Framer API.”

   proof ↗⚑ flag

   Rive!disputedcontradicted4/10

   Rive documents an open, text-based file representation (RML/XML) and open-source runtimes, suggesting some data portability (rive-docs-13, rive-docs-20, rive-docs-25, rive-docs-21, rive-gh-1). However, community feedback directly contradicts a full 'export and leave' story: users report no way to export movie/video assets (rive-comm-3, rive-comm-10) and note the open-source license only covers a narrow rendering subset while the actual content-creation editor remains proprietary and subscription-locked (rive-comm-5, rive-comm-1, rive-comm-2), undermining claims of full open-format data portability. missing for 10: documented full-fidelity export to universal open formats (e.g. video/SVG/JSON), open-source editor or file-format spec, and independent confirmation that RML round-trips 100% of file data without proprietary lock-in.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Rive
   Framer—none0/10

   Framer is closed-source proprietary SaaS; no evidence pack item mentions an open-license source availability, and this is a mainstream commercial product with no indication of open-sourcing its codebase.

   ⚑ flag

   Rive~partialcommunity5/10

   Rive's runtimes are documented and confirmed on GitHub as open-source libraries (rive-docs-21, rive-gh-1, rive-gh-2), giving AI-native users real source access to the rendering/runtime layer, but community evidence notes the MIT license only covers a 'rendering abstraction layer, a subset of the Rive runtime' while the Editor itself (where files are authored) remains closed-source (rive-comm-5, rive-comm-1). missing for 10: full-product open license (editor/design tool source not published), independent confirmation of license file/terms, clarity on what runtime components are excluded from the OSS layer.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [github] “The built-in GPU renderer (RiveRenderer) has RenderContextImpl backends for Metal, Vulkan, D3D11, D3D12, and OpenGL/WebGL.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Framer—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Rive—none0/10

   Rive's core product is the proprietary Editor (a SaaS/desktop app); only a subset of the runtime rendering layer is open-source (MIT), and community evidence explicitly notes the editor itself cannot be self-hosted and requires the hosted tool to author content. No docs or evidence describe self-hosting the Editor or backend service.

   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”
   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”

   proof ↗⚑ flag

Plugins

1. developerA documented plugin API with typings and samples lets me build and distribute my own editor extensions

   weight 2 · round to Framer
   Framer~partialclaimed6/10

   Framer documents a Plugins API for building editor extensions (small apps that interact with the Editor/CMS, insert layers/images/code components) with a dedicated developer docs section, plus adjacent APIs like Code Components and Server API. However, the evidence pack doesn't show explicit TypeScript typings references or concrete code samples/SDK repo, and there's no distribution/marketplace mechanism described. missing for 10: explicit typings documentation, concrete code samples/starter templates, and a distribution/marketplace mechanism for sharing plugins.

   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Code Components Custom React Components with visual controls to render anything on your site.”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”

   proof ↗⚑ flag

   Rive—none0/10

   No evidence of a documented editor plugin/extension API, typings, or samples for building third-party editor extensions; the evidence only covers runtimes, data binding, AI agent/MCP integration, and RML scripting, none of which document an extensibility API for building/distributing editor plugins.

   ⚑ flag

2. designerExtend the editor from a large plugin community or marketplace — icons, data fillers, accessibility checkers, and more

   weight 2 · round to Framer
   Framer~partialclaimed5/10

   Framer's docs confirm a plugin system where developers build 'small apps' that can interact with the editor and CMS (inserting images, layers, code components, modifying canvas), which is the technical foundation for a plugin ecosystem. However, the evidence never mentions a marketplace, community size, or specific plugin categories like icon packs, data fillers, or accessibility checkers as the story asks. Missing for 10: evidence of an actual marketplace/directory, plugin discovery UX, and named example plugins matching icons/data/accessibility use cases.

   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor.”
   • [claimed-docs] “Plugins Build small apps that can interact with the Framer Editor and CMS.”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”
   • [claimed-docs] “Plugins in Framer are small apps that can interact with the editor. They enable you to perform various actions such as inserting images, lay…”

   proof ↗⚑ flag

   Rive—none0/10

   No evidence of a plugin marketplace, third-party extension ecosystem, or add-ons like icon packs, data fillers, or accessibility checkers. The evidence only covers Rive's own built-in features (components, data binding, MCP/AI agent, RML) — none of which describe an external plugin/marketplace ecosystem. Missing for 10: any mention of a plugin API, extension marketplace, or third-party-built add-ons.

   ⚑ flag

Pricing

1. product managerPublished plan pricing makes seat types, tiers, and AI-feature gating clear before procurement

   weight 1 · round drawn
   Framer—none0/10

   The evidence pack contains no pricing page, plan tiers, seat types, or AI-feature gating details — only one mention that a static-file hosting feature is limited to Pro/Enterprise plans, which does not constitute published plan/seat/AI-gating clarity. No pricing comparison table or plan documentation is present anywhere in the pack.

   ⚑ flag

   Rive—none0/10

   The evidence pack contains only product/docs content about Rive's features (animation, data binding, AI agent, MCP) and community discussion referencing informal price points ($25-$39/month) but no published pricing page, seat-type breakdown, tier comparison, or explicit AI-feature gating documentation.

   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   proof ↗⚑ flag

2. designerThe free tier supports real design work — usable editor and collaboration without a paid seat

   weight 2 · round drawn
   Framer—none0/10

   The evidence pack contains no mention of Framer's free tier, its editor limitations, or free-tier collaboration features; all docs focus on AI agents, CMS, publishing, and plugins. No pricing or free-plan details are cited anywhere in the pack, so there is no basis to confirm the free tier supports real design work or collaboration.

   ⚑ flag

   Rive—none0/10

   No evidence describes what the free tier includes for editor/collaboration access; the only relevant community signal explicitly states that basic solo-dev animation work requires a paid subscription ($25-39/month), suggesting the free tier is not sufficient for real design work.

   • [community] “Didn't we already do this experiment with Flash? ... it seems that Rive wants to open source the player and then charge for the editor... He…”
   • [community] “So does this mean someone can create a free editor I can use for basic animation that I don't have to pay $25 for the rest of my life to use…”

   proof ↗⚑ flag

1. designerPrototypes can carry advanced behavior — animation between states, conditions or variables, scroll effects — to feel like the real product

   weight 1 · round to Rive
   Framer!disputedcontradicted6/10

   Framer's docs and community evidence confirm rich prototyping behavior — animated menus, carousels, code overrides, data-driven components (docs-45, docs-32, comm-4, comm-5) — but hands-on reports document concrete failures that undercut the 'feels like the real product' promise: animations distort during size/geometry changes, performance is inconsistent (60fps then chugging) on the same device, and users found Framer 'falls through' vs alternatives like react-spring when chaining multiple interactive animated nodes (comm-6, comm-7, comm-9). Missing for 10: independent verification that these animation glitches are resolved, and evidence of robust variable/conditional-logic support beyond CMS data binding.

   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”
   • [claimed-docs] “Code Overrides Higher Order Components to modify Layer and Component properties.”
   • [claimed-docs] “Fetch Building API endpoints that designers can use on their Framer sites without code.”
   • [community] “Since Framer is code based, you can do some things that are pretty amazing for a designer... Framer X is based on React, so designers can th…”
   • [community] “As a ux designer... this is quite an interesting tool if you design software. It gives a nice blend between design and code. Your prototypes…”
   • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
   • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
   • [community] “I feel react-spring is better suited for the job... tried them both with r3f, i think it's just about API design and framer starts to fall t…”

   proof ↗⚑ flag

   Rive✓fullcommunity8/10

   Rive's docs explicitly describe building interactive experiences responding to user input, screen size, scrolling, and application state (rive-docs-4), state machines/timelines/keyframes (rive-docs-3), and real-time data binding so animations update live (rive-docs-5, rive-docs-15, rive-docs-22, rive-docs-24) — directly matching the story's states/conditions/variables/scroll-effect prototyping needs. Community evidence corroborates real-world adoption for production-grade interactive UI/UX work (rive-comm-4, rive-comm-7), and Rive's own positioning ('no mockups, no prototypes... the real thing', rive-docs-16/23) reflects this design intent. Missing for 10: independent hands-on verification specifically of scroll-triggered effects and variable/condition-driven prototypes beyond vendor docs.

   • [claimed-docs] “Bring your designs to life with timelines, keyframes, and smooth interpolation.”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Connect animations, text, colors, layouts, and other properties to real-time data.”
   • [claimed-docs] “Data binding — autoBind, view models, bindViewModelInstance”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “I've been pushing over the past six months or so for multiple clients... to adopt Rive over Lottie and other past solutions, as I think it's…”
   • [community] “Truthfully the program they have looks fantastic at empowering UI/UX designers to do more with games... the workflow of this tool is definit…”

   proof ↗⚑ flag

2. designerWire screens into clickable prototypes with triggers, transitions, and overlays — no code required

   weight 2 · round to Rive
   Framer~partialcommunity4/10

   Evidence shows Framer supports animations/transitions (community: 'great for more advanced prototyping needs w/ animations/transitions', 'declarative approach to creating nice animations') and AI-driven interactive elements like 'sticky navbars, animated menus, interactive carousels' handled via prompts, but there is no explicit documentation of screen-to-screen click triggers or overlay linking (the core Figma-style prototyping flow), and community reports flag animation performance/rendering glitches that undercut confidence. missing for 10: explicit docs on multi-screen click triggers, overlay/modal linking, and independent confirmation of a smooth no-code prototyping flow.

   • [community] “Framer is great for more advanced prototyping needs w/ animations/transitions/etc, but Adobe XD is pretty good and fast for many needs, and …”
   • [community] “I use Framer on some projects and I love its declarative approach to creating nice animations. But one thing that has been confusing me is i…”
   • [community] “The rounded corners and the border thickness are getting distorted when animating size changes... Basically any effect that doesn't commute …”
   • [claimed-docs] “Sticky navbars, animated menus, interactive carousels, just describe what you want. The agent handles the wiring so you can focus on the des…”

   proof ↗⚑ flag

   Rive~partialclaimed5/10

   Rive's State Machines and interaction docs (rive-docs-4, rive-docs-22, rive-docs-24) support building input-driven, trigger/transition-based interactivity without code, and rive-docs-16/23 frame the tool as skipping separate 'prototype' handoff entirely. However there is no evidence of a Figma-style multi-screen/overlay prototyping paradigm (linking distinct screens, overlay layers, click-through flows across artboards) — Rive's interactivity is scoped to state machines within/across components rather than an explicit screen-flow prototyping mode. Missing for 10: evidence of multi-screen linking, overlay/modal wiring, and click-through flow prototyping across separate artboards/screens.

   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Bind an enemy's X and Y position so it can be controlled at runtime.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [claimed-docs] “When data changes, your scene updates automatically. Likewise, changes made in your scene can be written back to your data.”

   proof ↗⚑ flag

Canvas

1. designerFrames can behave responsively — auto layout, constraints, and grids resize designs the way real UIs flex

   weight 2 · round to Framer
   Framer~partialclaimed6/10

   Framer's docs describe breakpoint-based responsive adaptation ('adapts your layouts across breakpoints, adjusting stacks, type sizes, spacing, and image crops') and general layout refinement (breakpoints, spacing) via its AI agent and canvas, which implies auto-layout/stack-style responsive behavior. However, there's no explicit documentation of manual constraints or grid systems, and no independent/hands-on corroboration of responsive resizing quality. missing for 10: explicit docs on constraints/grid systems, independent verification of resize fidelity across breakpoints, non-AI-agent manual workflow evidence.

   • [claimed-docs] “Ask the agent to “Make this responsive for tablet and phone.” It adapts your layouts across breakpoints, adjusting stacks, type sizes, spaci…”
   • [claimed-docs] “Start from a prompt and use the Framer canvas to refine layouts, typography, components, breakpoints, spacing, color, and effects. AI helps …”

   proof ↗⚑ flag

   Rive~partialclaimed5/10

   Rive's docs repeatedly reference "responsive layouts" and building interfaces that respond to screen size (rive-docs-1, rive-docs-4, rive-docs-9, rive-docs-18, rive-docs-26), and the AI tooling explicitly generates "Layouts" as an artboard-level construct (rive-docs-10). However, no evidence details the specific mechanics of auto layout, constraints, or grid systems the way Figma-style tools describe them. Missing for 10: explicit documentation of constraint-based resizing rules, grid systems, or auto-layout algorithms, and independent/hands-on confirmation that layouts flex like real UI frameworks.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “Build interactive experiences that respond to user input, screen size, scrolling, and application state.”
   • [claimed-docs] “Rive's AI agent helps you write code, design, and animate. Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “The first set of tools are designed to let AI handle repetitive tasks, like creating complex View Models, State Machines with hundreds of st…”
   • [claimed-docs] “Generate scripts, responsive layouts, data models, and even animation.”
   • [claimed-docs] “Build interactive UI, motion, and game experiences in the Editor, or let an agent generate them with the CLI.”

   proof ↗⚑ flag

2. designerI get professional vector tools — pen and path editing, boolean operations, precise alignment — for real interface design work

   weight 3 · round to Rive
   Framer—none0/10

   The evidence pack is entirely about Framer's AI agents, CMS, publishing, plugins, and developer API — nothing addresses classic vector tools like pen/path editing, boolean operations, or precise alignment guides. No documentation or community evidence confirms these professional vector-editing capabilities.

   ⚑ flag

   Rive!disputedcontradicted3/10

   Rive's docs market it as a full design-to-ship tool ('design, animate, and code in one place... no mockups, no prototypes, no handoff') and mention vector graphics and components, but there is no documentation of boolean operations, precise alignment/snapping tools, or advanced path editing. A hands-on community comment directly contradicts the 'professional vector tools' claim, calling the drawing toolset just 'a pen and a couple of basic shapes' and comparing inefficient pen-only workflows unfavorably to real illustration tools. missing for 10: boolean operations, alignment/snap tooling, path-editing depth, and any rebuttal to the community criticism of basic drawing tools.

   • [claimed-docs] “Create vector graphics, responsive layouts, and reusable components, or import images, audio, fonts, and other assets from your favorite des…”
   • [claimed-docs] “No mockups, no prototypes, no handoff. The real thing.”
   • [claimed-docs] “Design, animate, and code in one place. What you build in the editor is what ships in your app, game, or website. No mockups, no prototypes,…”
   • [community] “Looks kinda interesting but I am not gonna touch anything that thinks an acceptable set of drawing tools is 'pen and a couple of basic shape…”

   proof ↗⚑ flag

Files

1. designerExport production assets — PNG, SVG, PDF, and more — with per-layer presets, scales, and slices

   weight 2 · round drawn
   Framer—none0/10

   Framer is a website-builder/publishing tool, not a design/prototyping tool with layer-based asset export; the evidence pack contains no mention of PNG/SVG/PDF export, per-layer presets, scales, or slices — these are Figma/Sketch-style export features absent from Framer's docs.

   ⚑ flag

   Rive—none0/10

   Rive's documentation focuses on exporting .riv files for runtime playback across platforms (web, mobile, games) rather than static production assets like PNG/SVG/PDF with per-layer presets, scales, or slices; no such export presets are described anywhere in the evidence. Community feedback explicitly confirms this gap — one user complains 'it's so insane they don't offer any way to export movie files' and another asks 'can I export video assets with this!?' — indicating the tool lacks traditional multi-format asset export entirely.

   • [claimed-docs] “Export once and use your interactive graphics across websites, mobile apps, games, videos, and more.”
   • [claimed-docs] “You can use the same exported file across supported runtimes, including web, mobile, game engines, and other platforms.”
   • [community] “It's so insane they don't offer any way to export movie files. The animation IDE is decent. Nowhere near as good as Flash was. But at least …”
   • [community] “But can I export video assets with this!? That's my question - I've had to resort to WebGL for a lot of this so far.”

   proof ↗⚑ flag

2. developerThe file format is open or documented, so my designs stay portable and toolable outside the vendor's editor

   weight 1 · round to Rive
   Framer—none0/10

   The evidence pack covers Framer's APIs, plugins, CMS, and AI agent integrations, but contains no mention of an open or documented native file format that would let designs be opened, edited, or version-controlled by external tools outside Framer's own editor/publishing pipeline. Version history, branching, and staging are all Framer-hosted features, not a portable file format.

   ⚑ flag

   Rive!disputedcontradicted4/10

   Rive documents RML (a text-based/XML representation of Rive files) and open-source runtimes that can load/parse .riv files (rive-docs-13/20/25/30, rive-gh-1/3), suggesting some portability outside the editor. However, community evidence directly disputes this: the open-source runtime is described as only a rendering/playback layer, and actually authoring or building Rive content still requires the proprietary, paid Rive Editor (rive-comm-5), undercutting claims of full format openness/portability. Missing for 10: a public, versioned .riv binary spec independent of RML, third-party tools that can author/edit .riv files without the vendor's editor, and confirmation that RML round-trips losslessly with the binary format.

   • [claimed-docs] “Rive Markup Language (RML) is a text-based representation of a Rive file. It lets you create and modify Rive content as code”
   • [claimed-docs] “making it possible to build Rive files with coding agents and other text-based workflows instead of working exclusively in the Editor”
   • [claimed-docs] “RML uses XML to describe the objects and relationships in a Rive file... build Rive files with coding agents and other text-based workflows …”
   • [claimed-docs] “It lets you create and modify Rive content as code, making it possible to build Rive files with coding agents and other text-based workflows…”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   proof ↗⚑ flag

3. developerSelf-host the full design platform on my own infrastructure under an open-source license

   weight 2 · round drawn
   Framer—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Rive—none0/10

   Evidence shows only the rendering runtime is open-source (rive-docs-21, rive-gh-1/2/3), while the Editor itself is a hosted SaaS product requiring Rive's cloud service—there is no documentation of a self-hostable full design platform. Community discussion explicitly confirms this gap, noting the MIT license covers only 'a subset of the Rive runtime that requires the Rive Editor to build content for' (rive-comm-5), meaning the actual design/editing platform cannot be self-hosted.

   • [claimed-docs] “The Rive runtimes are open-source libraries that allow you to load and control your animations in apps, games, and websites.”
   • [github] “Loads .riv files, advances state machines and animations, and draws via the abstract Renderer interface.”
   • [community] “So I love Rive—the product and the company. And I love open source. But this is an MIT license for Rive's rendering abstraction layer, a sub…”

   proof ↗⚑ flag

4. designerFull version history lets me name milestones, compare, and restore any earlier state of a file

   weight 2 · round to Rive
   Framer~partialclaimed5/10

   Framer's docs confirm automatic version history with one-click restore of any prior version (framer-docs-12, framer-docs-22) and branching to isolate changes (framer-docs-11, framer-docs-47), but there is no evidence of naming/labeling milestones or a side-by-side compare view between versions. Missing for 10: named milestone/checkpoint labeling, version comparison/diff view, independent hands-on confirmation of restore workflow.

   • [claimed-docs] “Version history and rollback. Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Every site change is saved automatically, so you can restore any version in seconds.”
   • [claimed-docs] “Branching. Explore ideas in a branch without touching the main project. Merge when it’s ready to ship.”
   • [claimed-docs] “Branches. Work on a copy of your project and keep the original clean.”

   proof ↗⚑ flag

   Rive~partialclaimed6/10

   Rive's docs confirm automatic revision tracking, non-destructive restore, and the ability to select and edit a prior revision (rive-docs-12, rive-docs-17, rive-docs-29), which covers 'restore any earlier state.' However there is no evidence of naming/labeling milestones or a compare/diff view between versions. Missing for 10: named milestone/labeling capability, side-by-side or diff comparison between revisions, independent corroboration of the restore workflow.

   • [claimed-docs] “Rive saves your files automatically as you work. Even if multiple people are working on the same file at the same time, Rive tracks all chan…”
   • [claimed-docs] “This guarantees that even restoring revisions is non-destructive, and you can always go back to the previous version of the file.”
   • [claimed-docs] “Select a revision to preview it and press the Edit Current Revision button. This copies the selected revision and creates a new entry at the…”

   proof ↗⚑ flag