Corto
Scheduling and bookings for a barber club, designed for phones first.
Explore the project’s design decisions →In Milan, an app makes sense when it reduces friction in something that happens every day: booking a table or treatment, joining an event list, reordering, or receiving an alert. We design iOS, Android, and web apps around that action.
Before writing code, we check whether a web app, which is quicker to publish and update, is sufficient or whether app stores are genuinely needed.
Our only office is in Montecatini Terme: Kreluna does not have offices in Milan. 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.
The app is built around a single action, such as booking, ordering, or signing up for an event, and makes it possible in just a few taps.
During trade shows, exhibitions, and popular evening events, capacity limits, queues, and automatic confirmations are needed: we define them before development.
Developer accounts, app store reviews, updates, and recurring costs are specified in the quote, without surprises after launch.
A new digital service may require accounts, payments, notifications, and business systems. We first test the primary journey with a prototype, so complexity and costs are added only when they support an actual use case.
Essential features, dependencies, metrics, and subsequent versions are separated. This makes it possible to evaluate the first release without confusing it with every future possibility.
With startups and businesses in Milan, we start with a clickable prototype: it is tested on a phone and revised before development begins. This saves weeks of work on features no one would use.
Objective, intended users, materials, and current tools.
Included work, timeline, costs, and external dependencies.
Agreed revisions, checks, and delivery.
Yes. We review workflows, materials, and technical constraints, then identify what can be retained and what needs to be redesigned before development.
Yes. The project is managed remotely from our Montecatini Terme office; we do not claim to have a Kreluna office in Milan. 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 companies and professionals in Milan, the project can be managed entirely online: shared materials, tracked revisions, and an agreed schedule. Every feature is tied to an operational need, avoiding pages or tools added simply to fill out the quote.
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 proposal separates the essential core from optional features so priorities, costs, and timelines can be compared before work begins.