Skip to content

Portfolio

Six examples in production from the portfolio.

Six of the projects running right now. The screens are captures from real deployments, not renders.

Below are six examples from the portfolio, chosen because they cover very different ground: a platform for an oncological surgery clinic, a medical platform in three flavours, a salon SaaS, a booking engine for cultural events, a ride service for parties outside the city, and a dental clinic site.

They have more in common than the list suggests. On each I wrote the API contract and the data model first, and the interface came second. On each, the browser talks to an intermediate layer that holds the authentication rather than to the backend directly. And on each I did the deployment too: several nodes, private addresses, encrypted backups, and monitoring that reaches me.

They differ in what each domain demands. A presentation site has to be found and understood in thirty seconds; an internal application has to be used eight hours a day, which is why OncoSurg has both and they look nothing alike. Some need several languages, others need themes and colours the client picks rather than me. Some hold money — commissions, tips, product cost, donations pledged against donations collected — others only appointments. And where people work standing up, a native app replaces the web page.

001

In production

OncoSurg

Private oncological surgery clinic, Cluj-Napoca.

Two products for the same client: the public site, in seven languages, that gets the clinic found, and the internal application the day is actually run from — patients, calendar, clinical records, signed documents and messaging between doctors. The browser never talks to the API directly; between them sits a layer holding the session and the token. Every change passes nine automated stages before production.

View the projectVisit the site
Outcome
In production at a private oncological surgery clinic in Cluj-Napoca, with a public site in seven languages and an internal practice application.
Built with
GoReact 19PostgreSQL 16Kubernetesi18n · 7 limbiPDFChat

002

In beta

Remedic

A medical platform in three flavours: Cabinet, Dental and Pet.

A medical platform built as separate services talking over gRPC against protobuf contracts. Authentication goes through Keycloak with PKCE and the tokens stay on the server. The doctor builds their own consultation form, picks one of three themes, and messages patients securely. Three flavours on one core — Cabinet, Dental and Pet — with Cabinet available now, free for residents.

View the projectVisit the site
Outcome
The Cabinet flavour is in clinical beta with a Romanian practice, ahead of general release.
Built with
GogRPCprotobufKeycloakReact 19PostgreSQLICD-10DRG

003

In production

Salon-Manager

Bookings, stock, documents and money for beauty salons.

SaaS for salons where each salon is a fully isolated tenant in the database. It carries a per-technician calendar, client files with signed GDPR consent, a profit-and-loss report with per-technician commission, WhatsApp reminders with the salon’s own templates and reply-to-confirm, a native mobile app, and an appearance page where the salon sets its own theme, accent colour and interface density. Mani-Manager, live at mani-manager.ro, is the personalised instance.

View the projectVisit the site
Outcome
In production at two salons through the Mani-Manager instance, with online booking, WhatsApp reminders, financial reports and a mobile app.
Built with
GoReact 19PostgreSQLWhatsAppPDFMobileMulti-tenant

004

In production

Eventum

Invite-only seat booking for charitable events.

A booking engine for charitable events where every guest gets a personal link. Each event gets its own micro-site carrying the organiser’s logo and colours, edited from a panel with live preview. The analytics follow the road from invitation to donation and show what was pledged against what was actually collected.

View the projectVisit the site
Outcome
In production for a series of charitable events, with one concert delivered and more scheduled.
Built with
GoReact 19PostgreSQLWhatsAppSMTPCMSAnalytics

005

In production

Get Home Safe

A private ride home from events outside the city.

Guests scan a QR code and ask for a car home: no account, no password, nothing to install. The request reaches every free driver and the first to take it keeps it. Drivers get a native Android app, and the organiser gets a live panel with the roster, assignment, and a history where each ride shows its price broken down by distance and waiting time.

View the projectVisit the site
Outcome
Running at Micus Barn and one further venue, with four events delivered and more scheduled.
Built with
GoPostgreSQLWebSocketsReactFlutterOSMKubernetes

006

In production

FriendlyDent

Public site for a dental clinic in Florești, Cluj.

A static site for a dental clinic: services explained in the patient’s own words, tariffs filtered by category, and a short path to booking. No internal application, no account, no login — a presentation site has one job, and here it is done quickly.

View the projectVisit the site
Outcome
In production at friendlydent.ro as the clinic’s main site.
Built with
Next.jsTypeScriptTailwind CSSSEO

On a phone

Some are used standing up

Get Home Safe is three screens wide because the people opening it are tired, it is dark, and the signal is weak. You get in by scanning a QR code, with no account and nothing to install. Drivers, by contrast, need GPS running the whole way and a notification that sounds with the phone in a pocket, so their side is a native Android app built in Flutter. Salon-Manager ships a native app too, with the same screens and bottom-tab navigation, because a salon is not run from a desk.

That is the rule: start with an installable web app that updates itself and needs no app store, and move to native code only when the hardware demands it - background location, the camera, or notifications that are not allowed to be late.

  1. 01

    Small screen first

    The narrow layout is the design and the desktop one is the adaptation. Nothing hides behind a menu button to pretend it fits.

  2. 02

    Built for a weak signal

    Small payloads, screens that open straight from a link, and actions that are not lost when the connection drops in a basement or a field.

  3. 03

    Native when the hardware demands it

    Flutter, React Native, Swift and Kotlin. A native build earns its place for background location, the camera or push notifications - not because it was on a wish list.

Next step

Let us find out whether it fits.

One conversation is usually enough for us both to tell.

Request a quote