notes · thoughts ·
The screens were finished, but the flow felt awkward
Only after implementing a PDF preview did I reconsider how people read documents. Working screen by screen, I was looking at the whole experience too late.
After implementing a PDF preview and following the actual usage flow, I began to wonder: is reading this inside the app really convenient?
For someone reading a paper or review document closely, a small modal can feel cramped. Downloading the file and opening it in a familiar viewer at a larger size, or printing it, may be more natural than zooming in, moving around, and zooming out again. I started with the thought that a preview would be convenient. Once it was finished, I found myself asking whose convenience I had been thinking of.
I have not concluded that the feature should be removed. It may be useful for someone who only needs a quick look. But checking a document and reading it at length are different tasks, and I did not distinguish them enough at the start.
Seeing the whole too late
These questions often emerge during integration testing. On an individual screen, the buttons are in the right places and the required features are there. But when I go through applying, submitting, reviewing, and checking the result, I notice steps that may not need to be there.
Development is divided into screens and tickets, but a user’s purpose does not stop at those boundaries. If we only try the whole experience after everyone finishes their part, we postpone asking whether a feature is needed until after implementation. By then, removing what we built has a cost too.
What I feel I missed was the situation of use, more than the implementation method. Before focusing on whether I could display a PDF, I should have asked more closely who would read it, how long the document would be, and where they would read it.
A feature adds more than code. It also adds states to test, platform-specific exceptions, and maintenance. I should be able to explain how it makes the user’s work easier enough to justify those costs. Next time, I want to follow the experience from entering to use the feature through finishing the task, without waiting for the screen to be complete.