PLENA Mobile Wallet Build Brief

Ship the PlenaProof Vault first.

The wallet is the first real app because receipts travel with the user, QR verification is mobile-native, and WhatsApp sharing is the default trust gesture for many mobile-first regions.

Build scope: v1 wallet + verifier core

Do not try to ship all 14 platforms as apps. Ship the wallet first because every other workflow eventually deposits a receipt into it.

In scope

iOS and Android from one shared codebase; local encrypted storage; receipt import by QR, deep link, JSON file, clipboard, and raw JSON; receipt list/detail; L0-L2 local verification; WhatsApp/email/system share/QR/PDF; Life Proof Archive export; five languages.

Out of scope

No cloud sync, no L3/L4 registry lookup, no signing new receipts on device, no ID scanning, no biometrics, no chat, no push notifications, no subscriptions, no Apple/Google Wallet passes in v1.

Why mobile first

East Africa is mobile-first, often intermittent-data, and WhatsApp/QR are natural trust gestures. The wallet becomes the daily proof surface.

Contractor instruction

Use this page as the public build brief for fixed-price quotes. If a contractor cannot answer the screening questions confidently, do not hire them.

  • Flutter or React Native only.
  • Repository ownership from day one.
  • Fixed price against acceptance criteria.
  • Thirty days post-launch support included.
  • No machine translation; PLENA supplies native dictionary files.

Acceptance targets

  • Onboarding in any of five languages under 90 seconds.
  • Import through QR, file, link, and JSON with identical stored result.
  • 100 receipts displayed without scroll lag.
  • L0-L2 local verification under 200ms on a mid-range Android device.
  • Life Proof Archive export produces valid JSON with manifest.
  • No analytics SDK or third-party tracker.
  • Published to both app stores after QA.

Recommended v1 budget target

Target a focused East African or South Asian contractor/studio range of USD 12,000 to 18,000 for a fixed-scope 8–10 week build. Treat shorter than 6 weeks as suspicious and longer than 14 weeks as inflated unless justified.

Rule: ship one app, the wallet

The Wallet v1 is the only mobile build target. The platforms become proof lanes, receipt templates, QR/deep links, issuer portal actions, and reviewer workflows.

Must include

Proof Yearbook timeline, QR verifier, WhatsApp sharing/verification, AI agent authorization receipt, creator proof packet, and selected archive export.

Must avoid

No 14-app build, no generic AI chatbot, no universal database of human identity, and no claims of legal recognition without counsel and pilot evidence.

Build path

Wallet first, issuer portal second, public verifier always, refusal log always, reviewer registry visible, and standards mapping public.