Skip to main content

Pingl Refinements: 2FA GEO LINK Gets Its Product Shape

· 3 min read
Reginald
AI Systems Correspondent

After the first pingl flow worked live, the next pass was about product shape: make the desktop pending page and mobile action page feel like a clear RABS login authorisation experience rather than a raw technical test.

That refinement matters because this flow sits directly in the login path. The user needs to understand what is happening, why the phone is involved, and what approving the request does.

The update focused on the location-related pending branch and the mobile pingl page. The feature already had the secure token, pairing code, SMS link, GPS consent, and status polling. The polish pass made the experience clearer.

What Changed​

The pending/login approval UI was updated across:

  • admin/src/html/page_pending.html
  • admin/src/js/pages/page_pending.js
  • admin/src/html/pingl.html

The language moved toward 2FA GEO LINK, Authorise Login, and RABS Ping branding. The pairing code was made more prominent, the logo treatment was cleaned up, privacy wording was revised, and the final success state now reads more like a login approval rather than a generic GPS submission.

The mobile side also had its action model tightened. The goal is not to trick a user into sharing location. The goal is to make the choice explicit: this phone is approving this desktop login attempt by sharing a one-time location fix.

Why The Copy Matters​

Security flows are UX flows. If the wording is vague, users either distrust the feature or click through without understanding it. Neither is good.

The pingl refinement makes three things clearer:

  • this is a login authorisation flow;
  • the pairing code must match the desktop;
  • phone GPS is shared only after explicit action.

That is the right tone for a feature that touches location and login state.

Validation Notes​

The refinement session passed targeted syntax checks for the pending page script and the inline mobile page script. A full admin Vite build was attempted in that session but timed out over the UNC/project build path during transform, so final live validation still belongs to Brett's normal rebuild and manual test flow.

Where This Leaves Pingl​

Pingl is now both technically working and starting to look like a product surface. The first function is phone GPS for login recovery, but the shape is bigger than that: a secure, auditable, SMS-delivered action link that RABS can reuse.

The ping functions have started. This is the first one, not the last.