fix first
Scope truth
Decide exactly what the public can see: source-to-sale demo, role dashboards, public-first story, and Business Pro gates.
No fake wallet claim
No real payout claim
No unlicensed finance wording
No unfinished ERP sold as live
Phase 210
Public-Demo Readiness Board
Final FAEDA starts here: decide what can be safely shown to the public, what stays internal, and what blocks Google/public upload.
Phase boundary
Readiness board, not a launch button
Phase 210 is a public-demo readiness board only. It does not publish FAEDA, submit to Google Play, create a mobile build, enable real auth, activate payments, collect real customer data, or approve production launch.
Decision
4
Days
5
Real ops
0
Readiness lanes
public gateready candidate
User journey
The first public path must explain FAEDA in one clean loop: supplier source, manufacturer demand, wholesaler route, shop listing, customer order draft, rider proof, partner payment evidence.
Clear first screen
Role choice is obvious
Customer is not first if source story is being shown
Every next link works
must verify
Mobile fit
Every public page must feel like an app on a phone: readable, tappable, fast, no horizontal spill, no desktop-only layout.
390 px width pass
Large text does not overflow
Buttons stay tappable
Navigation stays simple
blocked until complete
Legal and privacy
Google and real users need privacy policy, terms, support contact, delete-account readiness, and data safety truth.
Privacy policy
Terms
Support email
Delete account path
Data safety inventory
blocked until pass
Security and secrets
The public demo must contain no keys, tokens, real CNICs, real phone numbers, provider payloads, or production credentials.
No secrets in repo
No real user data
No partner credentials
No raw backend errors
planned
Google package
For Google Play, prepare app name, icon, screenshots, store copy, category, content rating, data safety, and testing track.
Icon
Splash
Screenshots
Store description
Internal or closed testing track
Can show publicly
Safe demo scope
1Founder story: what FAEDA is and what problem it solves
2Source-to-sale demo journey with fake/demo records clearly marked
3Role dashboards in preview mode for Supplier, Manufacturer, Wholesaler, Retailer, Customer, Rider, and Founder
4Universal Product Data Bank concept with master product, listing, availability, manufacturer product, demand signal, and order draft separated
5Upaisa/SBP partner-powered payment wording as future/partner rail, not an independent wallet claim
6Business Pro upgrade story for deeper ERP modules
Must stay internal
Do not expose as live yet
1Real wallet balances, stored value, credit, lending, BNPL, or direct payout claims
2Real customer onboarding with phone/password unless auth is actually secured
3Real payment execution, callback trust, settlement, ledger posting, COD clearing, or payout approval
4Real supplier invoice, GRN, inventory movement, tax filing, payroll, or export document execution
5Any AI governance, fraud detection, or IoT promise shown as live when it is only planned
6Any admin override that looks capable of changing real money, stock, identity, or legal records
Five-day upload board
210-230Day 1
Public demo lock
Readiness board, scope lock, route cleanup, first screen polish, demo-mode guard.
Day 2
Public journey
Source-to-sale public demo flow, role entry UX, login/register demo gate, mobile navigation, founder demo script.
Day 3
Policy and listing
Privacy, terms, Google data safety inventory, permissions audit, support/delete account readiness, store listing copy.
Day 4
Build and QA
Android/PWA wrapper decision, icon/splash/screenshots, full mobile QA, no-secrets and no-fake-claims audit.
Day 5
Release pack
Google Play internal or closed testing release pack and final upload decision board.
Google reality
Public web demo and Play production are not the same thing
1If the Play developer account is a newer personal account, Google can require a closed test with at least 12 opted-in testers for 14 continuous days before production access.
2Internal testing can still be used quickly for trusted testers, and a public web demo can be shown before full Play production approval.
3FAEDA should not promise public Play Store production in 5 days unless the account already has production access and all policies are complete.
4The safest 5-day target is public web demo plus Google Play internal or closed testing release pack.
Release blockers
Any one of these blocks public upload
1Broken route or missing CSS on mobile
2Any link back to /home from Business Pro public routes
3Wallet, payout, credit, or bank wording that implies FAEDA is independently licensed
4Privacy policy, terms, support contact, or delete-account readiness missing
5Store screenshots, app icon, splash, or demo script missing
6Real personal data, phone numbers, CNICs, payment references, secrets, or provider credentials visible
7Horizontal overflow, unreadable cards, hidden CTA, or desktop-only layout
8Any admin action appearing to execute real money, stock, invoice, identity, or settlement truth
Decision states
founder gateReady
Safe to show as public demo or tester build.
Fix first
Visible enough to review internally, but not public.
Internal only
Keep behind founder/team review until runtime and policy are real.
Blocked
Cannot upload or publicize until legal, security, policy, or UX blocker is cleared.
Next phase
Phase 211: Public Scope Lock
Next we freeze exactly which FAEDA screens, claims, demo data, role paths, and CTAs are allowed in the first public build.
Open Phase 211