Thinking About the People Who Come Back to Read in bubbleBible
A look back at bubbleBible's mobile-first reading experience. Making the place to read and the next action clear mattered more than introducing features to first-time visitors.
Joohwan Yu · Founder, Full Stack Developer
Toris · Published
Contents
When I started bubbleBible, what I had in mind was not a feature that shows more Bible text. I wanted to reduce friction around what to read today, how far I had read, and how to keep a record of what I read. Getting access to content and keeping up the reading were not the same problem.
What the First Screen Needed Differed Every Time
Someone visiting for the first time needs to know what the service is. Someone coming back may want to start reading right away. Making them pass through an introduction every time charges repeat users the same cost. Designing mobile-first, I felt that deciding which action to show first on a small screen is the heart of the product.
In the retrospective on the early web version, I recorded the background to choosing a PWA. It was a choice to be web-centered so improvements could ship quickly. This post looks back at the judgment of that period, and it does not mean that every distribution channel since, including apps, shares the same structure. I want to record the product’s current state separately from the context of the initial choice.
The Reading Experience Is Also Decided Outside the Content
Body text size, line spacing, and the area a finger can tap are not decoration. If zooming in or mis-tapping keeps happening while reading, small actions become a burden. In a product like a church community, where users vary in age and digital skill, it is hard to take only how a familiar developer uses it as the standard.
If I were reviewing it again now, I would walk through the flow of reading a verse and then leaving a bookmark or note at the size of a real phone. I would check that actions are not hidden not only with short content but also with long sentences and enlarged text. I would also look at how much unnecessary visual stimulation there is on the reading screen.
If You Want to Call Return Visits a Result
Helping build a reading habit is a hypothesis of the product. To conclude that habits actually improved, you need separate observation. The fact that there were installs or visits alone cannot prove sustained reading. I don’t attach unverified retention figures to this retrospective.
The question I took from bubbleBible is closer to “where do they start immediately the next time they come in?” than “what else should I add?” For a product used repeatedly, designing from the familiar user’s second visit was a good starting point.
Related record: bubbleBible early web design
Advertisement