Rapport · Product + Engineering case study
First ask whether the data belongs to today.
Before scaling a historical-data strategy, I matched older customer records against live appointments. Search speed was not the first problem; relevance was.
ReactCustomer search UI
ExpoApp framework
TypeScriptSearch logic
The decisions
Three decisions, the reasoning behind each, and what changed as a result.
Two years of records. Enough for today’s queue?
M. Chen appears in the historical records. Five other appointments in this film example do not.
Historical depth did not guarantee live coverage.The test changed the integration decision—not just the search speed.
How it works
A quick guide to the interactive flow on this page.
Dynamic contentClick each step to see a different part of the story.
The outcome
A clearer integration priority.
Live source access became the priority, while a shorter customer-search path improved usability in the meantime. Older records were kept out of the live-workflow assumption.