Raman Bhise @lostfleetdev
Contact

2025 project brief

Stresso

Emergency workflow from hardware trigger to operations dashboard

Stresso combines SOS-capable hardware, a Flutter app, a Node + SQLite backend, and an admin dashboard for active incidents.

Year

2025

Stack

ESP32nRF24L01FlutterNode.jsSQLiteReact

Impact

Most complete end-to-end system in my current project set.

Repo

Private / in progress

README-derived summary

Stresso connects device behavior, mobile interaction, backend APIs, and operator visibility in one stack. The project exists to reduce response friction during emergencies.

  • Hardware flow with local SOS trigger logic, BLE commands, and RF fallback handling.
  • Backend APIs for auth, profile, SOS events, and emergency contacts with SQLite persistence.
  • Admin dashboard that monitors active incidents with simple high-contrast status cues.

Build notes

Stresso connects device behavior, mobile interaction, backend APIs, and operator visibility in one stack. The project exists to reduce response friction during emergencies.

Current implementation

  • Hardware flow with local SOS trigger logic, BLE commands, and RF fallback handling.
  • Backend APIs for auth, profile, SOS events, and emergency contacts with SQLite persistence.
  • Admin dashboard that monitors active incidents with simple high-contrast status cues.

Known gaps

The architecture is sound, but production readiness still needs stronger secret management, broader test coverage, and deployment discipline across services.