Auto Secure LoginFaceScan / Mobile
FaceScan Android: a clearer route into capture and out to a saved result
The phone candidate improves capture-code validation, edited state, scrolling and local save actions.
Work covered: Sep 28, 2026
The capture journey starts before the camera
A person first needs to enter the intended capture workflow and understand whether the supplied code is valid. FaceScan’s September 28 Android candidate corrected that entry validation and preserved edited state. The goal is to avoid losing the person’s current input or moving forward from an invalid entry simply because the rest of the screen is available.
Use the space the phone actually leaves
The layout work improved scrolling beneath system controls and checked larger-text conditions. This matters on capture and result screens where a fixed header or navigation area can otherwise leave the action out of reach. The phone’s display preferences should not turn a supported local action into a search for a hidden control.
Review the result handoff
Local copy actions and document saving were part of the candidate review. Model packaging also received compatibility work, with initialization checked on the test device. These changes cover the surrounding capture workflow and readiness, while the later exact-frame corrections address a different part of the pipeline.
Candidate scope
The dated evidence describes source and controlled phone checks, with distribution and real-person capture acceptance kept separate. It does not establish a public Play release. The meaningful improvement is a more coherent candidate journey from entering the capture flow to handling a local result, with a clearer distinction between interface readiness and full capture acceptance.
Explore the product
Based on dated development and release records from September 25–October 8, 2026. Availability and acceptance are stated for the recorded milestone.