About us
Booka is ours. It isn't contract work for somebody else: the two of us decided it, built it and shipped it, and we make the product calls without asking anyone. There is no layer between whoever decides and whoever touches the code.
Who's behind it
Architecture, web, database
Software architect, based in Italy, works in Italian and English. On Booka he designs the data model and the permissions, writes the web applications and takes releases to production. Before Booka he delivered client platforms across different fields, from a mobile marketplace to multilingual hospitality.
robertodrago.devMobile apps, database
Builds Booka's mobile applications, the one for clients and the one for salon staff, and works with Roberto on the database schema underneath all of it.
How it's built
Booka isn't one app dressed up as three. There's the site clients book from, the software the salon uses every day, and an internal console for whoever runs the platform. Three applications with separate releases, on a single data foundation.
The reason is practical: your salon and the person booking are the same piece of information, and it has to stay one. Someone who books as a client in the morning and logs in as an owner in the afternoon is one account, not two that agree on a good day.
It costs more discipline up front, and it's why a schema change is written once and every product sees it at the same moment. It's also why we can tell you what comes next: the roadmap is ours, not a client's.
Where we actually are
Talking to us
If you run a salon and want to work out whether Booka is for you, or you're a business considering early access, the email lands directly with the people building the product. There's no call centre in between, and nobody we have to forward the question to.
hello@booka.it