Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Use case · Real estate & housing societies · India

One app for housing society billing, visitors, complaints and communication

A Spring Boot backend and Flutter app that run maintenance billing, visitor approval, complaints, chat, notices and documents for residential societies.

Client details are kept confidential. This use case describes the problem and what we built.

The brief

Residential housing societies run a surprising amount of administration: monthly maintenance bills, visitor entry, complaints, notices, documents and the staff who work in members’ homes. Most of it still happens on paper and in messaging groups.

We built a society management platform with a Spring Boot backend and a Flutter mobile app. It gives each role in the community its own view of the same data.

The challenge

What needed solving

Society admin runs on paper and chat groups

Maintenance bills, payment records, notices and complaints were handled through registers, spreadsheets and messaging groups, with no single record.

Gate security without visibility

Security staff had no reliable way to confirm visitors with residents or keep an entry and exit log.

Many roles, one community

Owners, tenants, family members, house help, committee members and security staff each needed different access to the same society data.

The solution

What we built

  1. Multi-society backend

    A Spring Boot 3 API on PostgreSQL with Flyway migrations models societies, units, owners, tenants, family members and house help, secured with JWT and role-based access.

  2. Maintenance billing

    Bills are generated per unit or in bulk, payments are recorded with their mode, and bills can be downloaded. Society-level and unit-level summaries and statistics show what is due and collected.

  3. Visitor management

    Visitors are registered with a code, approved or rejected by the resident, and checked in and out at the gate, giving the society a full visitor log.

  4. Complaints, chat and notices

    Residents raise issues with attachments and comments. Group and one-to-one chat with unread counts, announcements, events, documents and NOC requests keep the community informed.

  5. Notifications and files

    Firebase push notifications, email through Amazon SES and file storage on Amazon S3 are built in, with Redis available for caching and Excel and CSV import and export.

  6. Role-based Flutter app

    A Flutter app built with the Stacked architecture gives owners, tenants and security staff their own views on the same backend.

The outcome

What changed

One record for the society

Billing, visitors, complaints and documents live in one system instead of registers and chat threads.

Safer gates

Residents approve visitors from their phones and the society keeps a checked-in, checked-out log.

Ready for many societies

The data model is built around multiple societies and units, so new communities can be onboarded on the same platform.

Technology used

  • Java
  • Spring Boot
  • Spring Security
  • JWT
  • PostgreSQL
  • Flyway
  • Redis
  • Amazon S3
  • Amazon SES
  • Firebase Cloud Messaging
  • Apache POI
  • OpenAPI
  • Flutter
  • Dart
  • Stacked

Have a similar problem to solve?

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk