Booking app
Try the demo
Corto
Scheduling and bookings for a barber club, designed for phones first.
Explore the project’s design decisions →App design and development
in Florence.
Mobile experienceTry the Corto appOpen the demo We define and develop apps for bookings, services, purchases, or operational processes, choosing platforms and features before work begins.
A useful first version needs to handle one priority journey well. Accounts, payments, notifications, the backend, and publication are evaluated separately and included in the scope.
Our only office is in Montecatini Terme: Kreluna has no office in Florence. Studio meetings are by appointment. Analysis, revisions and delivery can take place online; any other meetings are agreed separately and are not automatically included.
Mobile experienceTry the Corto appOpen the demoAPPS TO TRY
Try the workflow, rather than just imagining the result.
The demos let you explore screens and booking or purchase steps. They do not demonstrate an operational backend, delivered notifications, real payments or an app store release: those parts require a dedicated project.
Beauty app
Try the demo
Aura
A mobile journey for treatments, availability, and bookings.
Explore the project’s design decisions →
Services app
Try the demo
Giro
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 →
An app to find your way, book, and return.
If the app handles visits, stays or events, we distinguish requests, availability and confirmation. Before prototyping, we need capacity, scheduling and cancellation rules and the system that holds current data.
Experiences and visits
Calendars, time slots, tickets, and on-site content need to work even when users have little time. We prototype the journey first and check where maps, notifications, or offline access are needed.
Hospitality and guest services
Check-in, requests, information, and offers can be delivered through a web app without requiring a download. The choice between an app, a web app, and an integration is based on how guests actually behave.
Communities and events
Schedules, favorites, access, and communications need clear rules for accounts, data, and moderation. We design the key states before estimating development and app store publication.
A project suited to your business.
User journey analysis
Users, screens, and the primary action are defined before coding.
Prototype and development
The workflow is tested, then implemented on the agreed platforms.
Testing and delivery
Devices, app store accounts, publication, and maintenance are specified in the proposal.
What we define before starting.
Priority user journey
We start with the action the app needs to make easier: booking, purchasing, accessing a service, or managing a task.
Prototype and platforms
Screens, accounts, payments, notifications, the backend, and iOS, Android, or web versions are defined before coding.
Testing and launch
Devices, app store accounts, data, checks, and publication responsibilities are specified in the proposal.
What this means for Florence.
A useful mobile experience while using the service
Bookings, itineraries, content, support, and accounts add value when they reduce steps at the right moment. We define the context of use and keep the first version focused on the primary action.
Content and operations after launch
Before development, we clarify who updates information, availability, and notifications. A manageable app needs an operational workflow as well as the interface users see.
A REMOTE PROCESS
Clear steps and responsibilities.
We share a sample journey with a user, starting data, action and expected outcome, including an error or cancellation. The prototype clarifies the steps; integrations and technical checks are assessed separately. Decisions and revisions remain documented.
- 01Assessment
Objective, intended users, materials, and current tools.
- 02Scope
Included work, timeline, costs, and external dependencies.
- 03Implementation
Agreed revisions, checks, and delivery.
App design and development for Florence.
Can the app connect to an existing booking system?
It depends on the APIs and access the system provides. Compatibility is checked before the connection is included in the quote.
What does the project include?
Every project starts with your needs. Together we define goals, features and timing, then prepare a tailored proposal.
Do you build iOS and Android apps?
Yes, when both platforms are included in the project. The quote always clarifies which versions and devices are covered.
Do we need a complete app right away?
Not necessarily. It often makes sense to start with an essential first version and test the usefulness of the primary user journey.
How do I request a quote from Florence?
Describe who will use the app, the main action and a complete example including errors or cancellations. Specify devices, data, existing systems, offline needs and available accounts. The proposal distinguishes prototype, development, backend, publication and maintenance.
Let’s discuss your project.
Tell us one action the app must let users complete and who will use it. Specify devices, data and systems to connect: this defines the first version to assess.
Write to KrelunaBefore developing the app.
Kreluna has one office, in Montecatini Terme. Studio meetings are by appointment. Analysis, revisions and delivery can take place entirely online; any other meetings are agreed separately. Materials, decisions and responsibilities are documented in writing.
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.
Images and styling serve a specific purpose: helping people understand the offering and reach the important action without confusion.