Skip to main content

Rent management app (DSII)

A design systems II (DSII) project focused on rent-related workflows: units, tenants, payments, and operational views for a property or dorm-style context.

Problem​

Paper spreadsheets and ad hoc messaging do not scale: double bookings, missed payment visibility, and no single place for staff to see occupancy and arrears.

Solution​

Design and build an app shell with role-aware flows: property/unit directory, tenant records, payment status, and simple reporting. Emphasis on clear IA, consistent UI patterns, and flows that match how staff actually work.

Impact​

  • Single source of truth for occupancy and payment state (within the scope of the project).
  • Faster onboarding for new staff compared to tribal knowledge in chat threads.

Lessons learned​

  • Edge cases (partial payments, mid-month move-ins) deserve explicit states in the model early.
  • Empty and error states matter as much as the happy path in internal tools.
  • DSII is a good forcing function for design tokens and reusable components.

Tech stack​

  • Frontend: framework and design system used in your DSII brief (e.g. React, Vue, or mobile stack)
  • Storage: mock API, local storage, or backend-as-a-service depending on course requirements
  • Tooling: Figma or similar for UX artifacts alongside the build