Riven Makes Branded Forms a Design Problem

A form can collect the right information and still look like it was pasted into a website as an afterthought. That becomes a practical problem when a signup flow, project brief, or client intake form sits beside carefully designed product pages. The form is part of the experience, but many tools treat its appearance as secondary.

Riven is a web-based form builder aimed at that gap. It lets you create branded forms in either a conventional full-page layout or a step-by-step flow, then add conditional paths without moving to a separate logic tool. Its central idea is straightforward: the form's visual treatment and its behaviour should be configured in the same place.

The basic job Riven does

The likely starting point is a form such as a project enquiry, feedback survey, signup flow, or client brief. You choose a layout mode, select a visual theme, add questions, and configure how answers should affect the next step. Riven's landing page shows examples using single-select questions, star ratings, text fields, and multi-select inputs.

The classic mode presents a more familiar full-page form. The step mode turns the same general task into a sequence of screens, with the respondent moving through one stage at a time. That makes Riven relevant to both ordinary data collection and what the product calls conversational forms. It is not limited to a single-question chat-like interaction, since the classic layout remains available.

The design controls are organised around nine named themes, including Modern Minimal, Neo-Brutalist, Sketchbook, Corporate, and Boxed. The examples also show a warm paper style with high-contrast inputs. The point is not merely to change an accent colour. Riven is trying to give the whole form a visual direction through typography, spacing, borders, contrast, and background treatment.

That makes the product most useful when a plain embedded questionnaire would clash with the rest of a site. A studio could use a more editorial treatment for an agency enquiry. A SaaS team could keep a project intake form closer to its product interface. These are design decisions rather than separate technical features, but they are the problem Riven is built around.

Where the logic fits

Riven's more substantial feature is visual branching logic. You can route respondents based on their answers, chain conditions with AND or OR rules, and use operators such as equals, contains, greater than, between, or regular-expression matching. The page shows a role question sending founders, designers, and developers down different paths before those paths reconnect.

The workflow described by the product is: define questions, connect rules, simulate a path, then publish. A path simulator is useful here because branching forms become difficult to reason about once several answers affect later questions. Riven also says it checks for broken loops and prevents infinite routing cycles before publication.

That does not remove the work of designing a good questionnaire. You still need to decide which questions belong on which path and what happens when a respondent gives an unexpected answer. The value is that those decisions are represented in the builder instead of being hidden inside scattered conditions or custom code.

How it reaches a website

Riven is designed to be embedded rather than used only as a standalone form destination. The landing page shows an iframe example for Next.js and React, and names Webflow, Framer, and static HTML as supported destinations. The iframe is described as dynamically resizing, which should reduce the usual problem of a fixed-height form creating an awkward nested scroll area.

It also advertises structured postMessage events between the embedded form and the host page. The example includes ready and resize events, so a developer can at least observe the form's state from the surrounding site. That gives Riven a place in projects where the form needs to sit inside a custom front end rather than live on a generic share page.

The setup still has a boundary. Riven runs on the web, so it is not a native desktop or mobile app. Its embedding story is aimed at websites and web frameworks. Teams looking for an all-purpose operational database, a native data-entry tool, or a deeply programmable form component will need to check whether the available events and exports cover their workflow. The page describes data export, but the material supplied here does not explain the full handling of submissions, permissions, or retention.

Who should use it

Riven is a sensible fit for startups, SaaS teams, agencies, and developers who care about how an intake or survey flow looks as well as where its answers go. It is also a reasonable option for anyone who needs branching logic but wants to configure that logic visually.

The tradeoff is that the design system appears theme-led. The product highlights nine handcrafted themes and says no custom CSS is needed, but it does not describe a fully freeform styling layer. If your brand depends on exact component-level control beyond those themes, that omission matters. Riven is for teams that want a polished, configurable form without building the whole interface themselves. It is not for teams whose main requirement is unrestricted visual or data-model customisation.