2026-11-03 –, Gardenia
In 2020, with no budget for proprietary software, Tripura Forest Department built FIRM — a Forest Incident Reporting Module using Android, Leaflet, and PostgreSQL. Five years on, here's what worked, what didn't, and what we'd do differently.
In 2020, the Tripura Forest Department faced a familiar problem for government agencies in resource-constrained settings: field rangers were logging wildlife incidents and forest crimes on paper, with no way to spatially analyze or respond to patterns in real time. Proprietary GIS and mobile solutions were simply out of budget. So we built our own — entirely with free and open source tools.
FIRM (Forest Incident Reporting Module) combined two components: an Android mobile app built in Java for field data collection, and a Leaflet.js-based web GIS viewer for administrators to monitor wildlife data and forest crime reports spatially. PostgreSQL served as the backend database, with a Java server handling data ingestion and APIs. Field rangers could log georeferenced incidents from the forest; department heads could see them on a live map.
Five years later, this talk reflects honestly on that experience — not as a polished success story, but as a practitioner's retrospective.
What worked: The core FOSS stack proved stable and deployable in a government IT environment with minimal licensing friction. Leaflet was lightweight enough to run on low-spec government desktops. PostgreSQL handled the data reliably. Rangers adopted the Android app faster than expected, particularly because it was simple and worked offline.
What didn't: Building a native Android app in Java was time-intensive for a small team. Offline sync logic was harder to get right than anticipated. Without a dedicated DevOps setup, updates and maintenance were manual and fragile. And without institutional champions, the system risked being shelved when key staff moved on.
What we'd do differently today: In 2025, the FOSS ecosystem has matured considerably. Tools like ODK/KoboToolbox could replace the custom Android app for data collection. GeoServer or pg_tileserv could improve map performance. PostGIS functions would allow richer spatial analysis within the database itself. A containerized deployment with Docker would make the system far more maintainable by non-specialist staff.
The core lesson: FOSS works — even under real-world constraints of budget, connectivity, and capacity. But sustainability requires more than good tools. It requires documentation, community buy-in, and designing for the team that will maintain the system, not just the one that built it. This is a five-minute story that any government technologist, conservation practitioner, or FOSS advocate working in the Global South will recognize.
