AESHClinic Solutions

Front desk hours: Mon to Fri, 09:00 to 18:00

Library

A small library for people who did not ask to become technical.

Short guides and a glossary for administrative teams commissioning or living with software. Use the search to find a term.

Glossary

12 terms
API
A defined way for two pieces of software to exchange information, such as your booking tool sending times to a calendar.
Accessibility
Designing so that people with different abilities, devices and assistive technologies can use a product.
Backend
The part of a system that runs on a server: storing data, applying rules and sending messages.
Cross-platform
One codebase that produces apps for both iPhone and Android.
Hosting
The rented computer space where a website or app backend runs and is reachable on the internet.
Prototype
A clickable model of an app or site, used to test ideas before building.
Release notes
A short description of what changed in a new version, written for the people who use it.
SSO
Single sign-on: staff use one existing work account to sign in to several tools.
TestFlight
Apple's service for sharing test versions of an iPhone app before public release.
UX
User experience: how a whole task feels from start to finish, not just how screens look.
WCAG
Web Content Accessibility Guidelines, the widely used standard for accessible web content.
Wireframe
A simple layout sketch showing where things go on a screen, without final styling.

Guides

Before your first call: what to gather

A list of the tasks that frustrate your team, a few screenshots of current tools, who would use the new tool and roughly how often, and any deadlines that cannot move. That is plenty.

Writing a one-page brief

Describe the problem in one paragraph, the people affected, what a good result would let them do, and what must not change. Leave the technology out; that is our job.

Questions to ask any supplier

Who will own the code and accounts? What will it cost each year to run? How are updates handled? What happens if we part company? A good supplier answers all of these without hesitation.

Keeping software healthy

Plan for regular updates, keep a list of who has access, review it when people leave, and keep your own copy of key documentation.

External references we trust