I just published the first article on my personal website:
RentIt+ started as an HTL diploma project, but it quickly became much more than a typical student application.
The central question was not only:
“How do we build a rental management system?”
It became:
“What happens when users still need to work, but the network is unavailable?”
That one constraint changed almost every architectural decision.
- The desktop client needed local storage.
- Changes had to be queued.
- The backend had to remain the authoritative source of truth.
- Synchronization needed validation, version checks and conflict handling.
- Workflows had to continue even when ideal conditions disappeared.
Real software is not just about screens, APIs and databases.
It is about workflows.
It is about constraints.
It is about understanding what the system must protect when things do not go perfectly.
That is why I built an offline-first rental system.
Read the article here:
brianronock.com/blog