Shane Ian Murphy on App Task Choices for a Cambridge Bookseller

Fictional example: an independent bookseller in Cambridge has ten quiet minutes before opening. She wants to examine a proposed financial app, but not because she enjoys exploring software. She has three different questions: where would she find an account overview, how would she inspect an unfamiliar charge, and what would happen if she left halfway through a task? None requires a tour of everything the app might eventually offer. Each requires a clear entrance.

I am Shane Ian Murphy, founder discussing the Global Secure App concept, and I think this distinction deserves more attention. A feature menu describes the maker's inventory. A task menu describes the reader's purpose. Those can overlap, but they are not interchangeable. For the desired design direction of Global Secure App, I would rather ask what someone wants to understand than expect them to translate a catalogue of product nouns into an action.

In this fictional shop, the bookseller's first selection could be “Understand an entry.” That wording would need testing, because an entry might mean a payment, a deposit, or something else. Nevertheless, it points toward an investigation rather than an immediate transaction. The next screen could explain what information would be needed and which actions would merely display details. A person should not have to wonder whether opening a task has already committed them to completing it.

The second question is about selection itself. Offering twelve equally prominent cards might look generous on a design board, yet make choosing harder at a busy counter. Three well described starting points, followed by a plainly labelled route to the full list, could be more useful. The important qualification is that the short list must not hide inconvenient information or privilege a commercial objective over the reader's stated purpose. Prioritisation should make the interface legible, not manipulate it.

Books provide a useful analogy with limits. A contents page helps a reader locate a chapter without insisting that they read the entire volume. An index supports a different kind of search. A proposed app could similarly offer both a guided route and a direct route. The bookseller who knows the term she needs should not be forced through introductory questions. The person who knows only the problem should not be abandoned with technical labels.

I would also want the task selector to distinguish learning from doing. “See how a transfer would work” and “Start a transfer” carry different expectations. A demonstration should be labelled throughout, not just on its opening screen. Sample figures should remain visibly fictional. If a future service involved an external provider, its role would need explanation at the relevant point, with verified terms rather than assumptions. A concept interface must never imply that such arrangements already exist.

There is another detail the shop counter brings into focus: interruption. A customer arrives, the bookseller sets down her phone, and the ten minute window disappears. The design question is not whether we can hold her attention longer. It is whether she can leave without uncertainty. If she returns, the interface should explain what was saved, what was not, and whether any action actually occurred. Those statements would have to match implemented behaviour exactly.

Before treating this approach as successful, I would test whether people can identify the right starting point using their own descriptions. I would watch for selections made reluctantly, repeated returns to the menu, and confusion between viewing and acting. A fast tap alone would prove little. Understanding the consequence of that tap matters more than speed, especially when the proposed task concerns money or personal information.

The fictional Cambridge bookseller does not need an app to admire its own breadth. She needs a clear relationship between her question and the next available step. That is the opinion I want to carry into Global Secure App: let people select a purpose, make the boundaries of that purpose visible, and give them permission to stop. An app earns a place in a working day by respecting the shape of that day.