Rent management app (DSII)
Built while I was at Dynamic Services International, Inc. (DSII). The app covers rent workflows: units, tenants, payments, and the day-to-day views staff need for a property or dorm-style setup.
Problem
Spreadsheets and chat threads do not scale. You get double bookings, weak visibility into who has paid, and no single place to see occupancy and arrears.
Solution
An app shell with role-aware flows: unit directory, tenant records, payment status, and simple reporting. The UX priority was clear information architecture and screens that match how staff already work.
Impact
- One place for occupancy and payment state within the project scope.
- New staff could get productive faster than learning the process from chat history.
Lessons learned
- Partial payments and mid-month move-ins need explicit states early, or they become permanent special cases.
- Empty and error states matter as much as the happy path in internal tools.
- Reusing component patterns across DSII apps helped us ship under real deadlines without inventing a new UI each time.
Tech stack
- Frontend: React (and the stack DSII used on the project)
- Backend / data: Internal DSII APIs and persistence
- UX: Wireframes and review with operators before locking flows