Post

Today we're sharing that View Transitions and Activity are ready to try in the experimental channel, along with docs and updates on other areas we're actively working on: react.dev/blog/2025/04...

View Transitions are now ready to try in react@experimental. They’ve been tested in production and are stable, but the final API may change as we iterate on feedback. Check out the docs to see how to add animations to your React app: react.dev/reference/re...

To animate a transition, you can add <ViewTransition> around part of the app to declare “what” to animate. ViewTransition activates "when" an update is caused by an animation trigger like startTransition, useDeferredValue, or Suspense, and "how" to animate is defined in CSS.

Adding <ViewTransition> around part of the app cross-fades the content by default:

You can customize animations with props on ViewTransition: <ViewTransition default=”slow-fade”>

For shared element transitions, you can add a “name”. This will animate an item from one part of the app to another: <ViewTransition name={id}>

ViewTransition can also be triggered by Suspense, to animate content to replace the fallback:

ViewTransitions can also be triggered by useDeferredValue and animate lists:

Check out the blog post and docs to see how to use View Transitions, how they work, and explore more use cases: react.dev/blog/2025/04...

Activity is also ready to try in react@experimental. Activity is a new component to hide and show parts of the UI: <Activity mode={isVisible ? 'visible' : 'hidden'}>

Activity allows you to pre-render parts of the app the user is likely to visit next, or restore state when a user returns to part of the app, so state like input fields isn’t lost:

Activity also includes SSR optimizations, and we may add more modes to Activity in the future. Check out the blog post and docs for more info: react.dev/blog/2025/04...

In this post, we’re also sharing some of the problems we’re currently working on. As we iterate on solutions, you may see features we’re testing shared from the PRs we are landing. Keep in mind, as we try different ideas, we often change or remove different solutions after trying them out.

When the features we’re working on are shared too early, it can create churn and confusion in the community. To balance being transparent and limiting confusion, we’re sharing the problems we’re currently working on, without sharing too much about the solution we have in mind.

When new features are ready to try in the experimental release, we’ll announce them on the blog with docs included, similar to what we’re doing with View Transitions and Activity today. Before then, you can follow along, but let us cook.