AutoWatch began with a deceptively simple proposition: make it easier for the public to see and report information about stolen vehicles. The engineering challenge appeared the moment that proposition was treated seriously. A platform capable of broadcasting an accusation to the public cannot behave like an ordinary classifieds website.
The first design problem was therefore not search, maps or even notifications. It was trust. A legitimate owner needs a way to establish a relationship with the vehicle before the system treats a theft alert as authoritative. That requirement pushed identity, ownership evidence, account verification and review into the centre of the architecture.
The alert itself had to become a controlled state rather than a permanent post. Active stolen vehicles need strong visual treatment and an obvious route for sightings. Recovered vehicles need the opposite: the system must stop soliciting new reports, change the public presentation immediately and preserve the transition for audit purposes.
Case studies at JACE focus on the engineering decisions and operational lessons behind the system — not a feature catalogue.
Sightings introduced another layer. A useful lead is more than free text. Time, location and direction of travel create structure around an observation, while the interface still needs to make clear that public submissions are leads rather than verified findings.
Mobile design matters disproportionately in that environment. The person reporting a sighting may be standing outside, using one hand, under time pressure. Important information has to appear early; the licence plate and vehicle imagery need visual priority; forms need to be short enough to complete without turning the moment into a data-entry exercise.
Abuse prevention is inseparable from usefulness. Public reporting creates opportunities for obscene content, false reports and malicious use. Automated moderation can help screen obvious problems, while uncertain cases need escalation rather than blind automation. The system also needs authorization rules that prevent someone from manipulating another owner's vehicle or alert.
Recovery closes the loop. An owner should be able to mark the outcome, preserve an appropriate recovery story where consent exists and produce an organized record of leads when information needs to be shared with authorities. Designing the end of the incident is just as important as designing its beginning.
The broader lesson from AutoWatch is that public-facing software cannot treat trust as a policy document sitting beside the application. Trust has to appear in the database model, permissions, workflow states, audit trail and user interface. The more consequential the information, the more visible that architecture becomes.
ABOUT JACE CASE STUDIESThese case studies discuss JACE Online's design and engineering experience at a high level. They intentionally avoid confidential customer information, patient information, credentials and security-sensitive implementation details.