About
Απλό.
It means simple. It is a promise we have to keep on every screen.
Why the name is the specification.
Parking software has a habit of growing. A field here for a case that happened once, a screen there for a report someone asked about in 2014. Ten years on, the person in the booth uses four of the sixty things it does and works around the rest.
Aplo is built the other way. Every feature has to look like the obvious thing somebody would have written anyway — and if it does not, it is not finished. The result is a system that a new attendant can run on their first shift, and an owner can read on a phone without a manual.
We build it in Greece, for lots we can drive to. The bugs get found by people we know, and the features come from watching a real Friday evening rather than a feature-comparison spreadsheet.
What we hold to.
- 01
Simplicity is the sophistication
Taking something out is harder than putting it in, and almost always the better call. We do the harder one.
- 02
The obvious version
If a screen needs explaining, the screen is wrong. Not the person using it.
- 03
Records, not guesses
Every number on every screen traces back to something that actually happened, with a timestamp and a name.
- 04
Built to be handed over
Your data is yours, exportable, in formats that outlive us. Software should earn the next month, not trap it.