Campus Safe

What we did

• •We ported the product’s legacy libraries to modern C# and Xamarin, addressing code that no longer compiled or behaved correctly in the newer development environment. This preserved usable parts of the existing system while creating a practical path to a modern cross-platform client.
• •We organized the application around a single shared codebase for iOS, Android, Windows, macOS, and ChromeOS. This approach reduced the need to maintain separate implementations and helped keep key features consistent for students and staff using different types of devices.
• •We implemented the alert flow around a short automatic countdown that starts when the application opens. Users can cancel the action when no emergency exists; otherwise, the application distributes the alert and connects notified users through a shared chat for situation updates.
• •Cross-platform messaging created a specific compatibility challenge because the legacy chat package did not work on every target device. We replaced that component with an alternative that worked across the new client, allowing the shared communication feature to remain part of the modernized application.
• •The resulting application brought the core alert and messaging experience to a wider set of operating systems while giving the client a more maintainable foundation. A common codebase also made it easier to preserve feature parity as the product moved beyond its older, platform-limited version.