[MEDIUM] No retry logic with exponential backoff in frontend API calls

[kilodesodiq-arch]

Engineering Gap

Frontend API calls have no retry logic. Transient network errors or 503 responses result in immediate user-facing errors. Mobile app has retry in syncQueue.ts but frontend does not.

Codebase Evidence

• app/frontend/src/lib/verification-api.ts: No retry on failure
• app/frontend/src/lib/verification-inbox-api.ts: No retry
• app/mobile/src/services/syncQueue.ts: Retry exists — pattern to replicate

Risk Profile

Transient failures surface to users unnecessarily. Poor UX under flaky networks.

Remediation Strategy

Add retry wrapper with exponential backoff (1s, 2s, 4s). Apply to critical API calls. Max 3 retries. Only retry on 5xx and network errors.

Success Conditions

• Retry wrapper created
• Applied to critical API paths
• Max 3 retries with backoff

Change Surface

Files: app/frontend/src/lib/, API call sites

Security Review

No security impact. Ensure idempotent retries for POST.

Completion Checklist

• Implementation completed
• Peer reviewed
• Ready for merge

[DammyAji]

Hi Maintainer, I would like to work on this issue. i am a software developer and I understand the importance of a seamless user flow. I have reviewed the issue description and understand the required changes. I will update the relevant documentation, ensure clarity and consistency with the existing style. Thank you for considering my request. I look forward to contributing to the project.

[jaynomyaro]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.