Engineering case study / Full-stack
PlusEmlak.
From property listing to a brand-ready visual.
01 / The problem
What needed solving.
Real-estate teams need to manage properties and client requests, then turn listing photography into branded social content. The interface had to bring those workflows together while keeping automated output editable.
02 / How it fits together
- 01Listing photo
- 02Detect + edit zones
- 03Composite
- 04Social publishing
03 / Engineering decisions
One typed API client
I centralized authentication headers, error handling and response types in a fetch wrapper. When the login contract needed a form-encoded OAuth2 request, the change stayed in one place instead of spreading across screens.
Give automation a human correction path
The template studio shows detected photo slots, lets users correct them and draw text zones, then requests a composite. The uploaded photo becomes a listing record first; the composition endpoint receives its image ID.
Keep the workflow resilient
A browser canvas compositor provides a simpler fallback if the server composition fails. Playwright verifies the template flow against the actual backend. The backend and infrastructure belong to my teammates.
04 / Where it stands
The frontend reached a pilot-ready state, with the template-studio workflow verified end to end. The public write-up documents my frontend ownership and the broader architecture as context.