It's been over a year since Conform's first major release and we have learned a lot since then. We have seen where people get stuck, where the API causes confusion, and where the complexity starts to pile up. We want to fix those things — but without making the code more complicated.

Over the past 6 months, we have been exploring a new model. We believe it's simpler, more flexible, and easier to reason about without giving up type safety or progressive enhancement. But instead of rushing to v2, we want to validate these ideas with the community first.

That's what the new future export is for:

import { ... } from '@conform-to/react/future';

This is a place for experimental APIs we're ready to share but still refining. They are opt-in, and you can adopt them gradually. As these APIs mature, we'll offer migration guides and eventually promote them as the new defaults in v2. Until then, they might include breaking changes in minor versions. So we recommend locking your version range to patch when using them.

We're planning to roll out the first public release of the future export soon, and we're sharing this early so it's not a surprise when it lands — and to avoid confusion when you see new APIs appear.

First up

The first future API is useControl — a new hook that helps you integrate custom inputs with Conform. Compared to useInputControl, it offers a more flexible setup with better support for multi select, file inputs and checkbox groups.

The first public release of this API is just a few days away. We are sharing this announcement early so you can get an idea of what's coming and let us know what you think.

(Update: released in v1.7.0)

What's coming next

In the coming weeks, you will see:

• A useFormData hook to subscribe to form data and compute derived state (Update: released in v1.8.0)
• A redesigned useForm hook with more control over form state and metadata
• Simplified parse helpers with better async validation support

All of these will be released through the future export and get their own write-up.

If you try any of these APIs, we would love to hear how they go — what works, what doesn't, and what could be better. Your feedback will help shape the next major version of Conform.