Capture a number from Firefox, review the likely identity in the queue and save with better context. Manual lookup and local editing still exist, but clearly as secondary fallback paths.
The main experience is already visible in the app today: a queue for review, confidence where the resolver is strong, and a secondary local edit path when a number still needs user cleanup.
A strong match appears directly in the queue, with confidence visible before saving.
If there is no reliable identity, the app still lets the user edit the contact locally before saving.
QuickContact works best when it receives local page evidence from Firefox. That context makes the queue more useful and reduces guesswork before saving.
Tap visible numbers, `tel:` links or supported call actions. QuickContact carries the page title, host and nearby text into the app so the resolver can do a better job.
The queue becomes the main review surface: likely matches, confidence, open actions and save/edit decisions all stay in one place.
Manual lookup is useful when browser context is not available, but it is intentionally positioned as a fallback rather than the main QuickContact story.
Enter a number, run the lookup and review any likely match the resolver can support.
When no reliable identity exists, the app still lets you adjust the contact locally before saving it on your device.
Manual remains useful for Chrome, copied numbers and incoming calls, but Firefox + extension remains the best path.
The post-install screen should immediately show the best path in under ten seconds, then keep manual lookup visible as fallback without giving it equal weight.
Hero block with autoplay demo, one headline and one CTA. The user should understand the main product value without reading a long explanation.
Secondary demo only. Shown below the Firefox block, with a tap-to-play manual example and explicit copy that manual is useful but less reliable.
Best with Firefox + extension
Capture numbers from pages, review the likely match and save with context.
Manual lookup stays available
Useful when browser context is missing, with local-only editing still available when a result needs cleanup before save.
If a manual lookup ends without a reliable match and you choose your own name, that path remains local to the device. It is not treated as owner contribution, feedback or implicit QuickContact sharing.
Only explicit contribution flows are treated as QuickContact-sharing paths.
Manual unresolved edits stay local-only and are not used as background learning for the QuickContact base.
Open the Play Store listing for the current Android build, or request testing access if your Google account is not yet enrolled in the closed test.
