Mobile release

App Store & Google Play readiness

A working record of what this app already does for store review, and what still depends on the developer account, the generated build, a physical device or a store console. Items are only marked done when they can be confirmed in this app's code.

Ready in the app

Implemented and reachable in the wrapped app today.

In-app account deletion

Dashboard → Delete my account. Lists exactly what is deleted and kept, requires typing DELETE, then deletes immediately. Financial records required by law are kept.

Both are linked from the footer on every marketplace page (/privacy and /terms).

Digital purchases stay on the web

Membership and ad-credit checkout are hidden in the store build. Pricing and credit pages stay informational; plans already bought on the web keep working.

Third-party payment flows untouched

Product, freight and camera-crew payments are for physical goods and real services and remain available.

Delete your account from your dashboard. Legal pages: privacy policy and terms of use.

Still needs an external action

These cannot be completed from inside the app; each needs an account, a build, a device or a console.

Apple Developer Program membership
Active membership, D-U-N-S number for the organisation, work email on the domain.
Google Play developer account
$25 one-time, identity verification completed.
Bundle ID / application ID
Permanent, e.g. io.madeinafrica.app. Cannot be changed later.
Reviewer test account
A real account with a supplier profile, products and an open RFQ so a reviewer can navigate without a login wall.
Screenshots, icon and feature graphic
iPhone 6.7" and 6.5", Google phone screenshots at 1080×1920, 1024×500 feature graphic, 1024×1024 and 512×512 icons without transparency.
Store scan and build
Run in the Mobile app tab on the main branch after publishing, then generate the .ipa and .aab.
Data Safety form and privacy manifest
Submitted in Play Console and verified inside the generated iOS build. Neither can be confirmed from here.
Closed testing
New personal Play accounts need 12 testers for 14 days before production access.

Google Play Data Safety — draft answers

Answer the console form from this draft, then check each row against the published privacy policy before submitting.

Data type	Collected	Purpose	Shared
Name	Collected	Account management, orders, invoices	No
Email address	Collected	Account management, notifications, support	No
Phone number	Collected (optional)	Account management, delivery and crew contact	No
Address	Collected (optional)	Shipping and invoicing	No
Company and business details	Collected	Supplier verification and marketplace listings	Public supplier profile, if published
Photos and videos	Collected	Product listings, reviews, verification documents	Public listings only
Files and documents	Collected	Verification and trade documents, stored privately	No
Messages	Collected	Buyer–supplier communication inside the app	Shared with the other party in that conversation
App activity and in-app search history	Collected	Improving search, recommendations and analytics	No
Device or other identifiers	Collected	Analytics, advertising campaigns, fraud prevention	With analytics and ad providers
Purchase history	Collected	Payments, invoices and accounting	With the payment processor only

Encrypted in transit: yes — the site and its API are served over HTTPS. Confirm the final build before submitting.

Deletion: yes — users delete their account and content inside the app, from the dashboard.

iOS privacy manifest — what to verify

The manifest ships inside the generated build. These are checks, not confirmed facts.

Check the generated iOS build for PrivacyInfo.xcprivacy before uploading. The wrapper may create one; it has not been verified here.
Declare collected data types that match the list above, including data read through the WebView (cookies, local storage, analytics identifiers).
Required-reason APIs commonly used by web wrappers: UserDefaults (CA92.1), file timestamps (C617.1), system boot time (35F9.1) and disk space (E174.1). Confirm against the actual build rather than copying these.
Tracking domains: only add domains actually contacted for advertising or analytics. List them after checking the live build.

Listing metadata — drafts

Character counts follow each store's limits.

Apple App Store Connect

App name (30): Made in Africa — B2B Trade
Subtitle (30): Source African Suppliers
Primary category: Business
Secondary category: Shopping
Keywords (100): B2B Africa,SADC suppliers,wholesale,procurement,tenders,verified manufacturers,African export

Google Play Console

App name (30): Made in Africa — B2B Trade
Short description (80): Source verified African suppliers, compare products and find open tenders.
Category: Business
Ads declaration: Yes — supplier advertising and sponsored placements are shown
Target audience: Business users, 18 and over. Not designed for children.

Review notes must give the reviewer a working account with a supplier profile, at least one published product and an open RFQ, and explain that memberships are bought on the web and are not sold in the app.

Pre-submission checklist

Run this against the built app, not the browser preview.

Check	Platform	Status
In-app account deletion works end to end	Both	Done
Privacy policy and terms reachable from the app footer	Both	Done
No checkout for digital content in the store build	iOS	Done
Membership notice on the pricing page	Both	Done
Reviewer test account created and its credentials recorded	iOS	Needs owner
Privacy manifest present and accurate in the build	iOS	Not verified
Data Safety form completed and consistent with the policy	Google	Not submitted
Screenshots and feature graphic at the required sizes	Google	Needs owner
No placeholder copy on core screens	Both	Review before submission
Android target SDK meets the current requirement	Google	Not verified
No crash on launch, search, product view or RFQ submit	Both	Test on device