Apartmanom

A property management app for Hungarian apartment hosts, pairing one operations dashboard with a booking widget that lives on the host’s own website.

Project Overview

Hungarian apartment hosts run their business across a wall calendar, a spreadsheet and a mail client. Every booking gets typed in three or four times, and every slip surfaces later as a double booking or a missing invoice.

Our client wanted one system: a single place to run the property, and a booking flow where the guest reserves without leaving the host’s own site. We built both halves as one product, a property management app for apartment hosts and the guest widget that feeds it.

We did the interface design, not only the build. A few rounds with the client settled the direction: a clean, uncomplicated dashboard and a calendar that reads at a glance. The client brought reference shots from Dribbble, and we designed the product out from there. It ships in Hungarian, but it is wired for translation from the start. Every interface string carries a translation key, so a second language is a content job rather than a rewrite.

The app is in live testing and gets polished most weeks. The client uses it daily to run real properties, and that has caught what no test suite would: everyday use surfaces the small breakages a developer never trips over, and a steady stream of those reports has gone straight back into the product.

Key Features

• Operations calendar: bookings, closures, maintenance and staff shifts in one view, filtered by unit or worker.
• Embeddable booking widget: guests pick dates, unit and extras in four steps, inside the host’s own site.
• Automated invoicing: deposit, proforma and final invoices from the host’s existing Hungarian invoicing account.
• Guest email on autopilot: confirmations, changes, payment reminders and a pre-arrival note with the local weather, sent from the host’s own domain.
• Guest self-service: guests change or cancel from a link in their email, seeing the price difference first.
• Digital guest registration: the required Hungarian form, completed and signed by the guest on their phone.
• Channel calendar sync: availability stays aligned with Airbnb, Booking.com and Szállás.hu.
• Team, payroll and statistics: per-module permissions, work-time entries, plus revenue, occupancy and average nightly rate.

The booking widget is the part guests actually touch, so here it is running live, the same build a host drops into their own site. It resizes itself to whatever step it is on.

Tech Stack & Integrations

• Flutter and Dart: one codebase behind both apps, so they stay consistent in look and behaviour.
• Supabase and PostgreSQL: the data and application backend, including the scheduled jobs behind mail and calendar refreshes.
• Firebase Hosting: serves both apps in production.
• Billingo and Számlázz.hu: hosts connect whichever Hungarian invoicing provider they already use.
• Resend: guest and system email, including mail sent from a host’s own domain.
• OneSignal: web push for events a host wants to hear about immediately.

Challenges & Solutions

A price has to survive time. A guest books in March for an August stay. In between, the host raises rates and a coupon expires. Recompute later and you hand the guest a surcharge they never agreed to. Every booking now locks its own commercial terms when it is created, and later changes can move the price only in the guest’s favour. Surprise charges stopped.

One calendar, several sources. Direct bookings compete with Airbnb, Booking.com and Szállás.hu for the same nights. Scheduled sync pulls external stays in, publishes availability back out, and surfaces a clash instead of overwriting a night. Careful backend development stops a host selling the same room twice.

The client owns the words, not the code. The product carries thousands of Hungarian interface texts, and the person with the best instinct for them does not write code. Rather than route every change through a developer, we built a round trip. She edits the entire interface in a spreadsheet, and her edits land back in the product. The voice of the app is genuinely hers.

Development Time

Development started in FlutterFlow around October 2025. Two apps in one product moved slowly there, so we rebuilt the whole thing in native Flutter to pick the pace back up. The current repository’s first commit lands in March 2026, and the product went into production by mid-June. Work ran on through the summer, adding invoicing, channel sync, statutory guest registration and data-retention tooling.

Impact or Outcome

Apartmanom went live in June 2026 and has handled real bookings, real invoices and real guest email at live properties ever since. Both apps ship on the web, and the dashboard is responsive enough to run a property from a phone.

Being straight about the rest: there is no App Store or Google Play release. The paid subscription tier is not switched on, and NTAK statutory reporting is built but still in testing. We have no public user or revenue figures, and we will not invent any. The public launch runs on the client’s timetable, not ours: they want the product finished to their own plan before it goes on sale to other hosts, and the release is expected in early 2027.

My Role & Value

We are the whole product team: discovery with the client, interface and brand design, both apps, the backend, the production rollout, and improvements most weeks since. The client makes the business calls, pricing rules, refund policy and the words. Everything else is ours.

Running apartments and tired of retyping every booking? This is what our web app development looks like once it is carrying real money. Book a free call below and we will map out yours.