Backend

The backend is the half of a system nobody sees. You tap a button and something happens; the backend is what happened. It holds the records, checks the rules and answers the screen. The part you look at is the front. The part that remembers is the back.

Think about a booking screen. The list of free times on your phone is the front. The reason two patients cannot both take four o'clock is the backend. It takes the first request, writes it down, and then tells the second person that the slot has gone. That check has to live in one place. If every screen decided for itself, a shop would sell its last item twice on a busy Friday, and someone would spend the evening apologising. A stock system like Storek works because one place owns the number, not four screens.

Here is the part most people miss. A phone app and a browser can talk to the same backend. The receptionist works on a computer, the manager checks the same figures from a phone in the car, and a customer books from a tablet at home. All three are asking the same place, so stock, bookings and prices cannot disagree. When Linkysoft builds a web application first and adds a mobile app afterwards, the second one costs far less than the first, because the hard half is already there.

This is worth asking about before you sign anything. Some suppliers build a small separate system behind each screen. It works on delivery day. Then the phone app shows yesterday's prices, nobody can say which number is right, and the fix is a rebuild. Ask a supplier whether the website and the app read from one place. Ask what happens to your records if you change supplier next year.

You do not need to understand how any of it works. You do need three things in writing. The data is yours. It is backed up, and you have seen a backup restored, not just been promised one. And you can be given a copy in a normal file whenever you ask. Linkysoft puts those lines in the agreement, because a backend usually holds the only copy of things a business cannot rebuild from memory.