01 logo

Shane Murphy on Plain App Language for Cambridge Readers

A fictional newcomer to digital finance asks the questions that technical shorthand leaves unanswered.

By Shane MurphyPublished 26 days ago • 3 min read
Shane Murphy on Plain App Language for Cambridge Readers
Photo by Jonas Leupe on Unsplash

Fictional example: someone in Cambridge who is new to digital finance reads a proposed app introduction. They understand the everyday goal described at the top, but several interface terms remain unclear. This person has no invented biography, financial position or personal difficulty. The scene is about unfamiliar language, not ability. It offers a useful design challenge: can an app explain what its words mean without requiring the reader to learn an entire field first?

As Shane Ian Murphy, founder discussing the Global Secure App concept, I believe plain language starts with choosing which distinction needs to be understood. Replacing a long word with a short one is not enough. If two stages have different consequences, the interface must preserve that difference. The desired design direction for Global Secure App is language that helps someone understand a task and its boundaries, without turning a product explanation into personal financial advice.

In the fictional introduction, the reader encounters “verification.” The word might refer to checking information, confirming contact details or some other process. A useful explanation should describe the relevant activity in context and identify who would perform it. Because this is a proposed concept, we must not imply that a particular procedure, provider relationship or regulatory status already exists. The plainest sentence is still misleading if it presents an unresolved plan as an operating fact.

Next, the reader sees “available.” Available for viewing, selecting, submitting or use under certain conditions? Small words can be as ambiguous as technical ones. I would want an editorial review to inspect ordinary adjectives and verbs as carefully as specialist terms. A glossary cannot compensate for a sentence whose central claim is underspecified. The meaning should usually be clear where the person needs it, with further explanation available for those who want it.

Examples can help, provided their status is explicit. A fictional screen might show how a draft differs from a submitted request using invented labels and figures. The explanation should identify the distinction rather than imply a real transaction has occurred. It should also avoid nudging the reader toward a financial choice. Understanding what a button would do is an interface matter. Deciding whether an action suits an individual's circumstances is a different question that the demonstration cannot settle.

Tone matters because unfamiliarity can make questions feel awkward. Phrases such as “obviously” or “as everyone knows” add nothing useful and may discourage someone from seeking clarification. Excessive cheerfulness can be equally unhelpful when the reader needs a precise answer. I would favour a direct description, a concrete example where necessary and a visible route to further information. Respectful language does not require a performance of friendliness; it requires taking the question seriously.

Consistency is the practical counterpart of clarity. If one screen uses “request,” another uses “instruction” and a third uses “order,” the writer should know whether those terms describe different things. If they do, explain the distinction. If they do not, choose a consistent name. For Global Secure App's proposed direction, a shared vocabulary would be part of the design work, with explanations reviewed whenever the underlying behaviour or scope changes. Copy cannot remain accurate through appearance alone.

Testing should ask readers to explain a phrase in their own words and predict what the associated action would do. Asking whether the wording is clear may invite a polite yes. A prediction gives more specific evidence. If the prediction differs from the intended meaning, the design team should investigate the wording, context and sequence together. The fictional newcomer's questions are prompts for that investigation, not proof that any particular vocabulary has already been validated.

The Cambridge scene ends with a reasonable expectation: an app should not require unexplained expertise merely to understand its own interface. That is the opinion I want to guide Global Secure App as a proposed concept. Plain language should clarify who acts, what happens, what remains uncertain and where more detail belongs. When those relationships are expressed accurately, the reader gains a firmer basis for deciding what to read next. That is a useful design outcome without making a claim about anyone's financial results.

apps

About the Creator

Shane Murphy

Shane Ian Murphy: co-founder/partner, Tri-Party Tokenisation; founder/CEO, Global Secure Technologies (planned 2027 launch); co-founder/partner, Dual Party Capital. Partner, RougeN International Corp. Formerly of Limitless Mobile.

Enjoyed the story? Support the Creator.

Subscribe for free to receive all their stories in your feed.

Subscribe For Free

Reader insights

Comments

There are no comments for this story

Be the first to respond and start the conversation.

Sign in to comment
    Written by Shane Murphy