Case study / Connected product suite
Missing Children SA
A connected API, desktop operations application, and cross-platform mobile experience for reporting, moderating, finding, and understanding missing-person cases.
Guided case study
Follow a report from submission to approved visibility.
Move through the reasoning in six short chapters, or read every chapter with JavaScript disabled.
01 / Problem
Time-critical reports still need a trust boundary.
A missing-person report needs to move quickly, but publishing unreviewed personal information creates its own harm. The system treats operational speed and controlled visibility as one product problem.
02 / Constraints
Three clients must agree on one case state.
Public reporting, desktop operations, and mobile discovery need different interfaces while sharing authentication, moderation status, case history, pagination, and media rules.
03 / Architecture
The API owns the workflow contract.
An ASP.NET Core API connects a Windows operations tool and a .NET MAUI app through generated OpenAPI clients. SQL Server holds structured and temporal data, while Azure Blob Storage holds uploaded media.
04 / Decisions
Visibility follows approval, not submission.
New and edited reports enter moderation. Public listing queries return approved records only, temporal tables retain changes, and clients evolve around a shared service contract.
05 / Evidence
The boundary is visible across every surface.
The desktop workflow exposes pending review, the API separates moderation from public reads, and the mobile experience consumes approved listings and case details through the generated client.
06 / Limits
The public experience uses no real case data.
The workflow explorer is a client-side demonstration with a synthetic case. The private source and any real personal information remain outside this portfolio.
Interactive workflow
Move one synthetic case from report to discovery.
No real person, case, or image is used. Select any stage to inspect the boundary it owns.
Public reporting client
A synthetic report enters as pending.
The reporting client validates required case fields and media metadata before sending one structured request.
Stage 1 of 5: Submission.
01 / The challenge
Move quickly without skipping trust.
A report contains sensitive, time-critical information. The system needed one consistent workflow across public reporting, operational review, approved listings, images, search, and statistics without letting unreviewed data flow directly to public clients.
02 / The system
One workflow, three purpose-built surfaces.
Designed and built the shared service boundary and the two client applications, with generated API clients keeping desktop and mobile contracts aligned.
API
Reporting, approved listings, moderation, users, statistics, image metadata
Desktop
Operational dashboard, role-aware moderation, reporting, user management
Mobile
Approved case discovery, case detail, reporting, image upload, pagination
03 / Engineering decisions
The architecture follows the risk.
Moderation before visibility
New and edited reports enter an explicit moderation queue. Approved records are the only ones returned to the public listing flow.
One contract, several experiences
An ASP.NET Core API owns the workflow. OpenAPI-generated clients connect the Windows desktop operations tool and .NET MAUI mobile app to the same contract.
History that can be recovered
SQL Server temporal tables retain changes to missing-person and moderation records instead of treating the latest row as the whole story.
Images outside the relational model
Azure Blob Storage holds uploaded media while SQL Server keeps the structured case and moderation data.
04 / What this demonstrates
Full-stack delivery with the back-end carrying the contract.
The useful part is not the number of applications. It is the separation of concerns: clients can evolve around their users while the API keeps authentication, moderation, data history, statistics, and media boundaries consistent.
Discuss a system like this