YakShaver - ✨ YakShaver-themed authorization result pages - Brand the success page and add error/failure variants

[steven0x51]

Cc: @calumjs @ricksu978 @adamcogan
Hi YakShaver team

🟥 Watch the video (42 sec)

Pain

When YakShaver completes a third-party integration authorization flow, it shows a very plain “authorization successful” page that feels unbranded and low-quality.

Suggested Solution

Create a YakShaver-themed authorization result page for the “success” state.

Create a consistent set of additional result pages for other outcomes (e.g. authorization error, authorization failure) so the whole authorization flow feels cohesive.

Acceptance Criteria

1. The authorization “success” result page uses YakShaver branding (theme, styling, and layout) and looks consistent with the desktop app.
2. The authorization result page set includes at least “success”, “error”, and “failure” states with consistent styling.
3. Each state communicates a clear, user-friendly message about what happened.
4. The new pages render correctly at typical desktop window sizes.

Tasks

• Identify where the current authorization result page is rendered in the desktop app
• Create a YakShaver-themed UI for the authorization success page
• Add an authorization error result page with YakShaver styling
• Add an authorization failure result page with YakShaver styling
• Wire the success state to the new authorization success page
• Wire the error state to the new authorization error page
• Wire the failure state to the new authorization failure page
• Confirm the pages render correctly at typical desktop window sizes

More Information

Figure: Current authorization “success” page looks plain/unbranded

Screenshots

Thanks!

[tomek-i]

🔭 crows-nest: picked up by ARMADA — dispatching to shipwright.

[tomek-i]

🔭 crows-nest: PR opened — #992

[ZenoWang1999]

• Why the issue is already closed — Armada linked the desktop-side PR to this issue, so once I approved and merged that PR, so the issue closed automatically.
• It's not live in prod yet — the work spans both the desktop repo and the backend. The backend PR is still open, and merging it won't trigger a prod release straight away.
• Next steps — I'll merge the backend PR after the sprint meeting and run a prod release