Work / DwarSeva Property / Wiki / Surfaces
sign-in
Surfacecanonicalverified 2026-10-04
SURFACE.APP.AUTH.SIGN-INSummary
Name and phone number, then an OTP — the whole of sign-up.
Raw wireframe
- .context/designs/mobile/auth/sign-in.html
- .context/designs/web/auth/sign-in.html
Why it is drawn this way
No KYC and no email at sign-up. Name and phone are enough to enter. Email is asked for before the first recharge, because that is the first moment an invoice and a grievance reply need somewhere to go. PAN and Aadhaar are never asked for by the app. The values are in catalog § Identity / KYC.
There is no splash and, on mobile, no landing page. A mobile install opens straight on this screen, which is why it is flow.start for the mobile set. The web set starts on the landing page instead.
Related
- catalog — the identity rules and the tagline
- product-spec — why the product asks for so little
Sources
- .context/designs/mobile/auth/sign-in.html
- .context/designs/web/auth/sign-in.html
Every project of mine is written down like this.
Read the résumé