My State Management Mistake
It wasn't a library. It was the way I was thinking about and defining state.


Did you know that preload="auto" on a video element won't work if the video is
conditionally rendered? React's new <Activity> component solves this problem
elegantly. Here's how.
Let's say you have a movie catalog with trailers. You want to show a video when the user clicks "Watch Trailer", and you'd like to preload it for a better user experience:
{ showTrailer ? <video src={movie.videoUrl} preload="auto" controls /> : null}
The problem? If the video element isn't in the DOM, the browser can't preload it. So when a user on a slow connection clicks "Watch Trailer", they have to wait for the video to load, defeating the purpose of preloading.
You might think: "I'll just use display: none or something instead of
conditional rendering!" And that might work, but there's a better way.
React 19's <Activity> component is perfect for this. Instead of conditionally
rendering the video, wrap it in an Activity boundary:
<Activity mode={showTrailer ? 'visible' : 'hidden'}> <div className="overflow-hidden rounded-lg"> <video src={movie.videoUrl} title={movie.title} loop controls preload="auto" /> </div></Activity>
Now the video element is always in the DOM, so preload="auto" actually works!
When the user clicks "Watch Trailer" on a slow connection, the video appears
instantly because it was already loading in the background.
Here's the complete component:
export function MovieTrailer({ movie }: { movie: Movie }) { const [showTrailer, setShowTrailer] = useState(false) useAutoplay(showTrailer) return ( <div className="mb-6"> <button onClick={() => setShowTrailer(!showTrailer)} className="rr-button mb-4" > {showTrailer ? 'Hide Trailer' : 'Watch Trailer'} </button> <Activity mode={showTrailer ? 'visible' : 'hidden'}> <div className="overflow-hidden rounded-lg"> <video src={movie.videoUrl} title={movie.title} loop controls preload="auto" /> </div> </Activity> </div> )}
Activity does more than just hide/show with display: none. When hidden, it:
This makes it perfect for content that users are likely to interact with again, like tabs, modals, or in our case, videos that should preload.
Since the video is always in the DOM when using Activity, you'll want to handle autoplay carefully. Here's a custom hook that handles pausing when hidden:
function useAutoplay(showTrailer: boolean) { useEffect(() => { const video = document.querySelector('video') if (!(video instanceof HTMLVideoElement)) return if (!showTrailer) { void video.pause() return } video.volume = 1 void video.play() return () => { void video.pause() } }, [showTrailer])}
This ensures the video pauses when hidden and plays when shown, giving you the best of both worlds: preloading and proper playback control.
Activity is a powerful new component in React 19 with many use cases beyond video preloading. Check out the React docs to learn about:
Activity is a great example of React solving real-world problems. Give it a try in your next project!
Delivered straight to your inbox.
It wasn't a library. It was the way I was thinking about and defining state.

Is your app as fast as you think it is for your users?

A basic introduction memoization and how React memoization features work.

When was the last time you saw an error and had no idea what it meant (and therefore no idea what to do about it)? Today? Yeah, you're not alone... Let's talk about how to fix that.
