HM.Guru

Context

Property management for multi-apartment buildings (manager portal, work orders, accounting). My role: thesis prototype on the chosen stack, then continued product work at BBIT (plus related eTop / CMS).

Problem

Managers needed clear day-to-day workflows — auth, entities, admin screens — that don’t feel like a raw database UI.

Decisions & tradeoffs

• Angular + Bootstrap instead of a heavier design system — fit BBIT delivery speed and responsive admin needs.
• ASP.NET Core + EF Core + SQL Server instead of a new Node stack — matched the team’s existing backend.
• Thesis: compare mobile frameworks first, then build the prototype on the winner — research had to become shippable code.

What I built

• Angular manager UI for property workflows (buildings, operations-oriented screens).
• Auth and session flows against ASP.NET Core APIs.
• Frontend integration with REST endpoints, Entity Framework–backed SQL Server data.
• Work-order / accounting-adjacent screens as part of the broader HM.Guru product surface.
• Bachelor thesis: framework comparison research + working prototype that fed into HM.Guru.
• Shared UI pieces reused across related BBIT products (eTop / CMS context).

Outcome

Working thesis prototype delivered; product work continued at BBIT as part of the HM.Guru / related stack.