Resolve the UX review findings and make authentication/onboarding measurable through a dummy analytics service ready for a future PostHog adapter.
Approach
Correct recipient confirmation, recovery hierarchy and simulated-outcome copy. Add shared typed analytics contracts, bounded in-memory dummy service and semantic journey tracking with privacy-safe correlation, retries, outcomes and abandonment. Review keyboard/semantics and EN/RU responsive states.
Acceptance criteria
Sent recipient stays accurate; changing email explicitly leaves sent state.
Retry verification is primary for internal confirmation errors.
Demo status and outcomes are clearly identified beside the heading.
Login/signup/verification journeys emit correlated, deduplicated semantic events; telemetry failures do not affect user operations.
Attempts, measurement windows, metrics, privacy and PostHog adapter boundary documented.
UX checks, tests, analysis and build pass; commit, push and PR completed.
Notes
No real PostHog SDK, credentials, collection or network calls. Dummy auth outcomes are proxies, never business successes. Preserve theme and EN/RU; record any browser/screen-reader limitations honestly.
Delivery and validation
Committed and pushed on onboarding-12, PR #13. All 68 tests, formatting, analysis of app/auth/analytics and web build passed. Browser confirmed mobile recovery, actual keyboard Tab/Enter submission, visible demo state and accessible recipient text.
Contract: docs/ux/auth-journeys.md. Dummy analytics is process-local only, bounded to 500 events; no PostHog SDK or transmission. Cross-device correlation and reliable browser termination signals require future integration; native VoiceOver/TalkBack audit remains a release check. PR remains open for review.
### Goal
Resolve the UX review findings and make authentication/onboarding measurable through a dummy analytics service ready for a future PostHog adapter.
### Approach
Correct recipient confirmation, recovery hierarchy and simulated-outcome copy. Add shared typed analytics contracts, bounded in-memory dummy service and semantic journey tracking with privacy-safe correlation, retries, outcomes and abandonment. Review keyboard/semantics and EN/RU responsive states.
### Acceptance criteria
- [x] Sent recipient stays accurate; changing email explicitly leaves sent state.
- [x] Retry verification is primary for internal confirmation errors.
- [x] Demo status and outcomes are clearly identified beside the heading.
- [x] Login/signup/verification journeys emit correlated, deduplicated semantic events; telemetry failures do not affect user operations.
- [x] Attempts, measurement windows, metrics, privacy and PostHog adapter boundary documented.
- [x] UX checks, tests, analysis and build pass; commit, push and PR completed.
### Notes
No real PostHog SDK, credentials, collection or network calls. Dummy auth outcomes are proxies, never business successes. Preserve theme and EN/RU; record any browser/screen-reader limitations honestly.
### Delivery and validation
Committed and pushed on `onboarding-12`, [PR #13](https://git.sendico.io/tech/sxchnge/pulls/13). All 68 tests, formatting, analysis of app/auth/analytics and web build passed. Browser confirmed mobile recovery, actual keyboard Tab/Enter submission, visible demo state and accessible recipient text.
Contract: `docs/ux/auth-journeys.md`. Dummy analytics is process-local only, bounded to 500 events; no PostHog SDK or transmission. Cross-device correlation and reliable browser termination signals require future integration; native VoiceOver/TalkBack audit remains a release check. PR remains open for review.
tech
added the frontend label 2026-09-12 06:23:44 +00:00
tech
self-assigned this 2026-09-12 06:23:44 +00:00
tech
added this to the SXCHNGE project 2026-09-12 06:23:44 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Resolve the UX review findings and make authentication/onboarding measurable through a dummy analytics service ready for a future PostHog adapter.
Approach
Correct recipient confirmation, recovery hierarchy and simulated-outcome copy. Add shared typed analytics contracts, bounded in-memory dummy service and semantic journey tracking with privacy-safe correlation, retries, outcomes and abandonment. Review keyboard/semantics and EN/RU responsive states.
Acceptance criteria
Notes
No real PostHog SDK, credentials, collection or network calls. Dummy auth outcomes are proxies, never business successes. Preserve theme and EN/RU; record any browser/screen-reader limitations honestly.
Delivery and validation
Committed and pushed on
onboarding-12, PR #13. All 68 tests, formatting, analysis of app/auth/analytics and web build passed. Browser confirmed mobile recovery, actual keyboard Tab/Enter submission, visible demo state and accessible recipient text.Contract:
docs/ux/auth-journeys.md. Dummy analytics is process-local only, bounded to 500 events; no PostHog SDK or transmission. Cross-device correlation and reliable browser termination signals require future integration; native VoiceOver/TalkBack audit remains a release check. PR remains open for review.