Web applications and booking systems
Web application development and booking systems
For when a site has to do something, not just show something: bookings with dates and rates, an admin panel for the owner, an internal tool for the team. We build custom applications in Zadar, and the code and the data stay yours.
The difference between a website and a web application is not how it looks but what happens when a visitor clicks something. A site shows: text, photos, prices, contact. An application takes input and decides: checks whether dates are free, calculates the price for the selected period, records the order, sends a confirmation, writes everything into a database the owner reads later. Most of our clients do not need an “app” in the App Store sense but a site with one part that behaves like an application. Anyone searching for “app development Zadar” or “mobile app development” usually means exactly this.
When a site is not enough
- A booking flow with dates, rates and availability, where a guest or customer sees at once whether the dates are free and what they cost
- Orders or enquiries that have to end up in a system, with a number and a status, rather than in an email that gets lost
- An admin panel the owner uses alone: prices, dates, units, without calling a developer for every small change
- An internal tool for the team: schedules, records, handovers, the things that currently live in Excel on three computers
- Generating documents from data, for example the CSV price list that Official Gazette 101/2026 requires
What we have built
Flycar in Split is a rent-a-car site with a complete booking flow: the customer picks a vehicle and dates, sees the price for that period and sends the booking, and the owner receives it with every detail in one place. Per-vehicle, per-day rates live in data, so they change in one place and apply everywhere.
Ljetni San near Omiš is a villa with apartments where guests book directly: they choose a unit and dates, get a price and send a booking the owner confirms. The site is multilingual, because guests come from German-speaking markets, and rates and dates are data, not text.
Lika Relax is a holiday house with a heated pool where a guest enters dates and immediately gets the total price, because per-day and per-season rates are part of the site, not an image of a price list. The same data feeds the availability calendar, so the owner does not maintain two things.
How we build
- A one-page specification: what the application does, who uses it and what data it holds. We both sign off on it before any code is written.
- A clickable prototype of the screens, so you see the flow before the code and change it while change is cheap.
- Build in weekly deliveries on a test address, so every week you see what is new.
- Testing with your real data: real prices, real dates, the real cases that usually get stuck.
- Handover with a guide, access in your name and an agreement on who does what after launch.
We send the quote within two working days of the specification conversation, with a fixed price for the described scope. How long the build takes depends on the number of screens and integrations and is stated in the quote, not discovered along the way.
Technology and ownership
We build in React, Node.js and TypeScript, the same tools this site is made with. The application is installed on your hosting or server, under your account. After handover the code and the database are yours, with no monthly licence to us and no lock-in: another developer can continue where we stopped. External services the application uses, such as sending email or taking card payments, also run on your accounts.
Maintenance and changes after launch
An application running on real data needs someone to look after it: security updates, backups, a check that confirmations still arrive. That can be us, under the maintenance arrangement described on the Website maintenance page, or your own person with our instructions. New features after launch are quoted as separate, smaller jobs, so you know the cost before you say yes.
FAQ
Frequently asked questions
A site displays content, an application takes input and does something with it: calculates, checks, stores, sends. In practice most projects are a site with one part that is an application, a booking flow say. It is built and priced by how many such parts there are.
It depends on the number of screens, roles and integrations, so the quote states it for your scope. The biggest influence on the deadline is you: how fast the data, the rules and the answers to questions that come up during the build arrive. That is why we start from a one-page specification, so those questions get asked at the start.
Yours. You get the source code, the database and the access, and the application runs on your hosting. There is no licence or subscription to us; if you want maintenance, that is a separate arrangement you can cancel.
It can. For accommodation the most common link is an iCal feed to Booking and Airbnb, so booked dates close on every channel; if you already use a channel manager, we connect to it. Before the quote we check what your tool offers, because the work and the price depend on it.
We integrate payment through a processor that operates in Croatia, on your merchant account. For accommodation this is often not needed at the start: enquiry, confirmation and a deposit by bank transfer cover most cases, and cards are added once the volume of bookings justifies it.
For almost every client a web application is enough: it opens in the browser, works on every phone, can be added to the home screen and does not go through store approval. An App Store app makes sense only when you need what the browser cannot give, such as working offline or notifications on the lock screen, and then we say so up front.



