It doesn’t have to be this crass. This example is clearly a reactionary afterthought deployed to enable users to run the courses on iPads. My 4 year old absolutely loves doing these activities on our iPad, and while he is never short of things to bug me about, having to press play between each screen is not one of them. So why would we invest time in finding a more complex solution when even a child (such good natural arbiters of user experience that they are) isn’t fazed by an extra button tap.
Ultimately we wanted to maintain a user experience that was free of distractions and clunkiness. The beauty of automatic playback is that the technology disappears and the user is focused on the content. By asking the user to press play every time we wanted them to listen to something, we felt we were taking a step away from what users have come to expect.
There’s also the minor but annoying issue of requiring the user to tap “next” and then having them tap again, this time on a “play” button, to get the audio content going. We figured that in most cases, click- or tap-minimisation is preferable, and that most users would find this double tapping cumbersome.
So what do we know? We know we need the user to make an interaction with a new page in order to play back media. And we know we don’t want an overt play button making the user feel like they have to do more work to engage with the content. So what’s the solution?
One solution was to put the entire course on one page. With everything on the one page we could fire off media events at will with a single tap. The downside here is that the course would take forever to load on slower internet connections. We needed a better solution.