Skip to content

No offline/PWA support — app is unusable without a live network connection #94

Description

@ndii-dev

No service worker, no manifest.json beyond whatever Next.js scaffolds by default, no offline fallback UI. A wallet app benefits from at least being able to show last-known balances/transaction history when offline, even if sending requires connectivity.

Definition of done:

  • Service worker caching last-fetched balance/transaction state
  • Explicit, tested offline UI state (not a blank error page)
  • Send/off-ramp actions clearly disabled (not silently failing) when offline

Before opening a PR for this issue, read CONTRIBUTING.md.

This is not a starter-issue. The Definition of done above is the full
acceptance criteria, not a subset to sample from — a PR that addresses part
of it is an unfinished issue, not a smaller one. Your PR must include, in
the PR description itself:

  • Root cause / design-decision rationale in your own words — not a restatement of this issue
  • Every Definition of done bullet above addressed explicitly, with a one-line note on how
  • Evidence the code actually runs: pasted test/build output, a screen recording or before/after screenshots for UI changes, or real (non-mocked) logs for network/contract-facing work
  • New or updated tests included and shown passing (paste the output)
  • Any adjacent/related behavior this issue calls out re-verified, not assumed unaffected

PRs missing these will be sent back before review, not reviewed and rejected — please do this up front.

Metadata

Metadata

Assignees

Labels

GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions