A national provider of integrated law enforcement software engaged IdeaBlade to rebuild its flagship records management suite — used by officers in the station house and in the field — as a modern, mobile-capable web application. IdeaBlade performed the rewrite from the ground up.
The application is modular: each agency licenses only the modules it needs, and individual editing screens are customizable down to the specific fields a department requires. Modules are unified through the Angular module and routing structure, so a customized deployment is a configuration of one codebase rather than a fork of it.
The governing engineering constraint was that an officer must never lose work. IdeaBlade built a three-tier persistence scheme: entered data is written to local device storage, continuously streamed to a server-side key-value store, and on explicit save fully validated and committed to the relational database. The application had to remain fully usable with no network at all.
What we delivered
A ground-up replacement of a legacy integrated law enforcement management system with a responsive web application usable in the station house and on tablets in the field. Scope included a modular licensing structure, per-agency screen and field customization, an offline-first persistence architecture, and integration with multiple third-party law enforcement products.
Technology
Angular and TypeScript on the client; C# and .NET with ServiceStack on the server; Breeze for data management; Microsoft SQL Server; DevExtreme HTML5 control suite. Source control in Mercurial on Atlassian Bitbucket; project tracking and documentation in Atlassian JIRA and Confluence, at the client’s direction.
Complexity
- A domain model that had to stay flexible across the divergent record-keeping requirements of individual police departments.
- Many integration points with third-party libraries and products.
- Mandatory offline operation.
- A keyboard-only interaction model: full keyboard operability was a functional requirement across the application, since mouse and touch input are frequently unavailable in the field.
Outcome
The suite was delivered as scoped: 126 screens across the licensed module set, with offline operation and per-agency customization in place — a prime example of a progressive web application developed with an offline-first approach.
The client has not given permission to be named or to share screenshots.


