Chapter four
Ready was supposed to mean ready.
I had spent so long trying to finish the app that finishing felt like the obvious turning point. Now, surely, we could find out whether people wanted it. A useful product ought to have a chance to speak for itself.
The store introduced a different set of questions. There were listings, screenshots, categories, privacy answers, payment requirements, and all the details needed to present the app. Then there was the much larger question of whether anyone would see it.
I did not object to explaining the product. I wanted to explain it. The surprise was how quickly that explanation could become one small part of a much larger undertaking. The app had needed to make sense to the people using it. Now I also had to learn what made sense to the systems responsible for deciding where it appeared.
The work had changed its name, but it had not ended. I had crossed one finish line and found another waiting behind it. This time, the app working well was only the starting condition.
The app-store machine
A listing became a whole new job.
The product needed words and pictures that would help a stranger understand it. That was reasonable. But choosing a category, preparing screenshots, answering requirements, and maintaining the listing created a separate stream of work.
Then came the problem the listing could not solve by itself: being noticed. Finishing a page in a store does not mean the right person will ever stand in front of it. Discovery had its own demands.
The person looking at a listing has very little reason to be patient with it. They do not know the years behind the icon, and they should not have to. They need a clear reason to care about what the app can do. Learning to respect that brief encounter was useful. Confusing it with the entire business of discovery was not.
I had built a tool to help people keep work together. Now the work of presenting that tool was spreading into more places. The resemblance was hard to miss.
Before discovery
I was ready for the useful part to begin.
After so much preparation, I wanted the important test to happen: someone using the app and finding out whether it helped. That was the reason for all the decisions that came before it.
Yet every added step could delay that meeting. It became possible to spend more time improving the route to a hypothetical customer than learning from a person with the app in front of them.
The first useful feedback could be very ordinary. A person might not understand a label. They might look for a document somewhere unexpected. They might tell us which detail saved them time. Those were things I wanted to learn from actual use. No amount of preparation around selling the app could replace the understanding that comes from seeing where it helps and where it gets in the way.
That is a lonely place for a useful idea to sit. The work is real, the cost is real, and the chance to help still feels farther down the road. I needed to shorten that road.