Corto
Scheduling and bookings for a barber club, designed for phones first.
Explore the project’s design decisions →In Rome, an app is useful where there are many bookings and cancellations: restaurants, guided tours, beauty salons, medical practices, and rental businesses. Reminders, confirmations, and waitlists reduce empty slots and phone calls.
We assess together whether a web app accessible through a link or QR code is enough—often the best choice for tourists who will not install anything.
Our only office is in Montecatini Terme: Kreluna does not have offices in Rome. The project is handled remotely; any in-person meeting must be arranged separately and is not automatically included.
Mobile experienceTry the Corto appOpen the demoBookings, purchases, and services become tangible when you can actually try the key steps.
Scheduling and bookings for a barber club, designed for phones first.
Explore the project’s design decisions →
A mobile journey for treatments, availability, and bookings.
Explore the project’s design decisions →
A rental concept with straightforward search, selection, and use.
Explore the project’s design decisions →Demo concepts designed and developed by Kreluna: they illustrate our approach and quality, but are not presented as projects commissioned by clients. Explore all projects and design decisions →
Users, screens, and the primary action are defined before coding.
The workflow is tested, then implemented on the agreed platforms.
Devices, app store accounts, publication, and maintenance are specified in the proposal.
Confirmation, a reminder the day before, and the option to cancel free up slots in time to reassign them.
For people spending only a few days in the city, a web app opened from a QR code on menus, tickets, or signs works better.
Translated copy, deposits, or advance payments when they help reduce no-shows.
For services, practices, and businesses with many users, we start with the recurring action: booking, checking a status, sending a request, or completing a task. The first version needs to make that action simpler than the current process.
We define which data is necessary, who manages it, and when a notification is genuinely useful. App stores, servers, payments, and external services are explicit line items in the quote.
We start with a prototype to test on a phone with people working on the restaurant floor, at reception, or in the practice. They can tell us whether the workflow holds up on a busy day.
Objective, intended users, materials, and current tools.
Included work, timeline, costs, and external dependencies.
Agreed revisions, checks, and delivery.
Yes. Prototypes, test builds, and reviews are shared online. Supported devices, publication, and account responsibilities are agreed upon before development.
Yes. The project is managed remotely from our Montecatini Terme office; we do not claim to have a Kreluna office in Rome. Analysis, revisions, and delivery take place online.
Yes, when both platforms are included in the project. The quote always clarifies which versions and devices are covered.
Not necessarily. It often makes sense to start with an essential first version and test the usefulness of the primary user journey.
Describe your business, objective, available materials, required features, and approximate budget. After the initial discussion, you will receive a proposal with the scope, timeline, costs, and exclusions.
Tell us what you want to achieve, who will use the solution, and which tools are already in place. We will reply with the questions needed to assess the work.
Write to KrelunaFor businesses, practices, and companies in Rome, work is organized remotely with one point of contact, scheduled online meetings, and decisions documented in writing. Distance does not change the method: objectives and content first, followed by structure, checks, and launch.
We describe the primary action, users, data, and essential notifications. The prototype, platforms, app store publication, and ongoing management are treated separately to avoid unplanned costs or features.
The first discussion separates what needs to work immediately from later developments, so the project does not grow out of control.