Custom Reack Hooks: useAudio

In the last episode of the Custom React Hooks series, weve discovered the useNetworkState hook to simplify the users network state management. Today, well explore another useful custom hook: useAudio. Ready? Lets go!

• Motivation
• Implementation
• Usage
• Conclusion
• Support Me

Motivation

Why would you ever need such a hook? Well, Ill give you two examples. The first one is my personal website, iamludal.fr (I swear this is not self-promotion ), built with React, which top navigation bar contains a button to switch between light and dark theme. Actually, if you turn up the sound a little bit, you might hear a switch sound. This sound comes from this custom hook. The second example is the Typospeed game (not self-promotion either), where you can hear sounds when removing a word (actually, Typospeed was built with Svelte, but you get the idea). In both examples, we need to play some sounds, and we dont want to repeat ourselves by manually instantiating a new audio, settings its volume, its playback rate...

const Home = () => {  const audio = useRef(new Audio('/switch.mp3'))  useEffect(() => {    audio.current.playbackRate = 1.5    audio.current.volume = 0.8  }, [])  return (    <button onClick={audio.current.play}>Play Sound</button>  )}

We dont want write all this code every time we need to use audio sounds. Also, we have to use the useRef hook in this situation and keep track of its current value in order to not recreate the audio instance at each component re-render.

That being said, we now have a sufficient reason to implement our new custom hook. Lets get our hands dirty!

Implementation

As we said in the previous part, we dont want to repeat ourselves (and this is the major goal of custom hooks). Therefore, our function will take optional parameters for our audio instance (which can be either static or dynamic), corresponding to additional options.

const audio = useAudio('/switch.mp3', { volume: 0.8 })

Also, we dont want to bother with the .current property: we have to extract this logic inside the new hook. This way, we will be able to interact with the audio instance directly.

audio.play()audio.pause()

Hence the skeleton will look like this:

const useAudio = (src) => {  const audio = useRef(new Audio(src))  return audio.current}

This is the first and basic version of the hook. If you dont need to have additional options, youre ready to go. But we will add another parameter to this hook: an options object. Each time a given property of that object changes, we have to update our instance. This way, the options can be updated dynamically from outside with another hook, such as useState. The final hook implementation now looks like this:

const useAudio = (src, { volume = 1, playbackRate = 1 }) => {  const audio = useRef(new Audio(src))  useEffect(() => {    audio.current.volume = volume  }, [volume])  useEffect(() => {    audio.current.playbackRate = playbackRate  }, [playbackRate])  return audio.current}

If you need any other options, feel free to add them depending on your needs. For instance, you could add an array parameter for the play method in order to only play a specific part of the audio (particularly useful when you have one audio file with multiple sounds, which is a technique used by some games).

Our hook is now ready to be used.

Usage

Back to our first example, the code can now be simplified as follows:

const Home = () => {  const audio = useAudio('/switch.mp3', { volume: 0.8, playbackRate: 1.5 })  return (    <button onClick={audio.play}>Play Sound</button>  )}

Weve abstracted out all the logic inside this new hook, which leads to a simpler, cleaner and more readable code.

Conclusion

I hope this hook will be useful to you for your projects. If you have any questions, feel free to ask them in the comments section. With that being said, thank you for reading me, and Ill see you next time for a new custom hook.

Source code available on CodeSanbox.

Support Me

If you wish to support me, you can click the following link to buy me a coffee (which I will then probably turn into a new custom hook... ).