Shane Ian Murphy on Explaining App Symbols to Cambridge Readers

Fictional example: a visitor in Cambridge opens a demonstration app and sees a row of small symbols. A circle contains an arrow. Another button shows a tray. A third uses two overlapping shapes. The visitor does not know which opens information and which might begin an action. No real person or product interaction is being reported here. The invented scene asks a straightforward question: how much meaning should an interface expect a picture to carry alone?

I am Shane Ian Murphy, founder discussing the Global Secure App concept, and I am wary of calling icons universal. Familiarity is learned through repeated use in particular contexts. Even a recognised symbol can mean different things in different apps. A downward arrow could suggest downloading, expanding, receiving or moving to another section. The desired direction for Global Secure App should be to support interpretation through context and words, rather than treat recognition as a test the reader must pass.

In our fictional example, the visitor first tries to infer meaning from position. A symbol beside a balance might concern that balance, but the relationship remains ambiguous. Adding a short visible label changes the task. Instead of guessing a metaphor, the person can read an action. That label still needs careful wording. “Receive” and “Request” are not interchangeable, and an icon cannot repair a verb that describes the wrong consequence.

The distinction between an action and a status is especially important. A check mark might communicate that a stage is complete, that an item is selected, or that the user should tap to approve it. Those meanings should not be collapsed into the same visual treatment. I would want a proposed design review to ask what each symbol represents: a place, an action, a condition or an illustration. Consistent roles would matter more than merely consistent drawing style.

There is also a problem of visual resemblance. Two icons may look distinctive when enlarged on a designer's screen and nearly identical at normal size. An appealing outline style can conceal the difference between a document, a card and a window. The appropriate response is not to blame the visitor for missing a detail. It is to test the symbols at the size and in the surroundings where they would actually appear, with labels where ambiguity persists.

For Global Secure App, a demonstration would also need to avoid borrowing reassuring symbols as substitutes for evidence. A shield, lock or badge can imply more than a concept has established. The presence of a familiar security image would not demonstrate a specific safeguard, regulatory status or guarantee. Any such claim would require verified facts and precise language. In a proposal, decorative imagery should not create the impression that operational or legal questions have already been settled.

The visitor's route through the example suggests a modest research method. Show a symbol in its intended context and ask what the person expects to happen before they select it. Do not first explain the designer's interpretation. After the selection, ask whether the result matched that expectation. The answer may expose a wording problem, a placement problem or a misleading symbol. It is more useful than asking whether the icon looks modern or attractive.

I would keep the findings specific. If several readers mistake a tray for an archive, that tells us something about that symbol in that context. It does not prove that a broad population cannot understand digital interfaces. Design research should identify correctable relationships between presentation and interpretation. The fictional exercise is valuable precisely because it directs attention toward those relationships without inventing demographic claims or turning one imagined visitor into evidence about everyone.

At the end of the Cambridge scene, the visitor has a reasonable request: tell me what the control means before asking me to trust it. That request belongs at the centre of the Global Secure App design ambition. Symbols can help people scan, recognise and navigate, but they should work with language rather than carry hidden instructions. A compact label is sometimes the most respectful design decision available, especially when a mistaken interpretation could change the course of a task.