Keyra

Challenges

1. 01

   Covering every real sign‑in path

   Problem

   Real users don't just log in. They verify with OTP, set a password on first login, forget passwords and change phone numbers.

   Approach

   I built each flow as a first‑class screen (login, OTP verification, first‑time login, forgot and reset password) and tested them against a real Cognito pool.

   Outcome

   Every path a user can take through sign‑in is handled, not just the happy one.

2. 02

   Admin tools without a console

   Problem

   Creating users and editing their attributes required going through the AWS console.

   Approach

   I added screens to create users with custom attributes and to edit them afterwards, behind proper authorisation.

   Outcome

   Admins manage users from the product instead of AWS.

3. 03

   No secrets baked into the build

   Problem

   Environment‑specific settings shouldn't be compiled into a frontend image.

   Approach

   I moved configuration to runtime so the same Docker image runs in every environment.

   Outcome

   One image, many environments, and nothing sensitive in the bundle.

What I took away

• Auth is mostly edge cases; design for the unhappy paths first.
• Runtime configuration keeps images portable and secrets out of bundles.