Society Automation System

A final-year build with a physical side

Society Automation System was my diploma final-year project. The idea was to make everyday community operations easier to monitor and control by joining a mobile interface with hardware that could sense and act in the real world.

It was a much bigger kind of project than a standalone app. The experience had to make sense to a resident, while the hardware layer had to respond reliably to commands and report useful readings back to the app.

One system, two layers

The Flutter application brought the controls and status information together in one place:

• Home automation for lights, fans, and appliances
• Water-level and consumption monitoring
• Environment readings such as air quality, temperature, and humidity
• Security and society-maintenance updates

The Arduino projects handled the physical side of those ideas. They were organized around separate concerns such as the gate, park motion detection, water and air quality, and fire or garbage detection.

Talking to the hardware

The app communicated with the Arduino servers through small HTTP endpoints. That made the boundary between the interface and the boards visible: the Flutter side requested status or sent an action, and the embedded side translated it into something physical.

Working across C++, PlatformIO, Arduino-style hardware, and Flutter made every feature feel like a complete loop rather than a screen in isolation.

What I carried forward

The project taught me to design for imperfect connections, separate responsibilities across a system, and think about feedback from both sides of an interaction. A button is only useful when the physical world can acknowledge what happened.