ferenc.rocks/

Proof » Doorie

Doorie – Early-stage hospitality product

2016–2017 · Backend, admin, mobile APIs

The situation

Doorie was an early-stage hospitality product built by a small team from sketches, conversations, and fast product decisions.

There was no detailed specification, separate QA team, or heavy process around the work. The product had to take shape while the backend, administration area, and mobile APIs were being built.

Where the complexity lived

The product was still evolving, so the technical work had to remain flexible without becoming careless.

Backend structure, admin functionality, mobile APIs, and product decisions all had to develop together.

In a small team, there is no separate department to catch every missing detail. The system had to support the product as it changed without overengineering for a future that was still unclear.

What I worked on

I worked across the stack: server-side architecture, backend implementation, administration functionality, and API support for the mobile application.

The work was less about owning one narrow technical layer and more about taking responsibility for enough of the system to help a small team keep the product moving.

Why this matters

Early-stage product work comes with its own kind of complexity: uncertainty, fast decisions, changing requirements, and limited support around each person doing the work.

Doorie shows the same practical pattern in a different setting: understand the product, make useful technical decisions, and keep moving without waiting for perfect conditions.

Technical context

MeteorJS / Node.js, MongoDB, React, backend architecture, administration system, APIs, mobile application support, early-stage product development.