Publish to the App Store & Google Play
Right now this is a responsive web app — a website that looks and behaves like a mobile app in the browser. It is not a native mobile app yet, so it cannot be downloaded from the App Store or Google Play on its own. Below is exactly what has been prepared here and what you still need to do to get it into both stores.
What kind of app is this today?
- Current type
- Responsive web app (React + Vite), installable as a PWA
- Runs where
- Any phone or desktop browser — no install required
- Installable?
- Yes — browsers now show “Add to Home Screen” (PWA manifest + service worker added)
- On the App Store / Play?
- Not yet — requires a native wrapper and store submission (see below)
Already prepared here
- Responsive mobile-first design that runs full-screen on phones
- Web App Manifest (name, icons, theme, standalone display) at /manifest.webmanifest
- Service worker registered for offline app shell and installability
- App icon set (192px, 512px, maskable, Apple touch icon) in /icons
- Privacy Policy page at /privacy and Terms at /terms (store-required URLs)
- Organization details, support email and location in the app
What you still need to provide
Apple Developer account
USD $99/year per organization. Enroll at developer.apple.com with the trust’s legal entity info and D-U-N-S number (free, takes a few days).
Google Play Console account
USD $25 one-time. Sign up at play.google.com/console with a personal or organization Google account.
Native app package (.aab + .ipa)
Wrap this PWA with a tool such as PWABuilder, Capacitor or Bubblewrap to produce a signed Android App Bundle and an iOS build. This sandbox cannot build or sign native binaries.
Store screenshots
Google: phone screenshots min 320px, recommended 1080×1920. Apple: 6.7", 6.5", 5.5" device sizes required. Capture from the live app on real devices or a simulator.
Final privacy-policy URL
A public https URL (e.g. https://shaheednazirghulamtrust.com/privacy). The /privacy page is ready — just publish the site and use that link.
Charity registration proof
Apple and Google may ask for the trust’s registration number and regulator entry. Add it on the /verification page before submitting.
Suggested store listing details
Copy these into the store consoles. Edit anything before submitting.
- App name (30)
- Shaheed Nazir Ghulam Trust
- Subtitle / tagline (80)
- Donate • Education • Relief • Mosque
- Short description (80, Google)
- Give to education, water, food, orphans & relief in Parachinar.
- Full description (4000)
- Shaheed Nazir Ghulam Trust & Foundation serves the people of Parachinar and the Kurram valley, KPK, with education, healthcare, clean water, food, orphan support, emergency relief and mosque projects — built on trust and transparency. Browse 16 programs, give one-time or monthly, receive email receipts, track progress, and follow real updates from the field. Humanity • Service • Hope.
- Category
- Apple: Lifestyle or Education · Google: Social or Education
- Content rating
- Everyone (no violence, no ads, no in-app purchases)
- Target audience
- 13+
- Keywords (Apple, 100 chars)
- charity, donation, zakat, sadaqah, Parachinar, Kurram, mosque, orphan, water, relief, Pakistan, education
- Support email
- shaheednazirghulam@gmail.com
- Privacy policy URL
- https://shaheednazirghulamtrust.com/privacy
- Website
- https://shaheednazirghulamtrust.com
- Default language
- English (en-US) · Urdu locale available in-app
Google Play — your steps
- 1Create the app in Play Console → Create app → fill name, default language, app/game, Free.
- 2Complete the App content questionnaire: privacy policy URL, ads (No), app access, content rating, target audience, data safety.
- 3In Data safety, declare that the app collects Name, Email, Phone and Payment info (donations) — and that payments are handled by external processors.
- 4Upload the signed .aab under Production → Create release (or Internal testing first).
- 5Add store listing: icon (512×512), feature graphic (1024×500), phone screenshots, description.
- 6Submit for review. First-time accounts require 20 testers on a closed track for 14 days before production — plan for this.
Apple App Store — your steps
- 1In App Store Connect → My Apps → New App → name, primary language (English), bundle ID, SKU.
- 2Under App Information set category (Lifestyle/Education), content rights, age rating (No for all restricted content), and the privacy policy URL.
- 3Complete App Privacy: declare collection of Name, Email, Phone Number, and that purchases (donations) are not made in-app via Apple’s IAP — donations go through external providers. Apple may require a web-based donation flow.
- 4Upload the signed iOS build (.ipa) via Xcode / Transporter / App Store Connect API.
- 5Add App Store listing: app icon (1024×1024, no alpha), screenshots for all required device sizes, description, keywords, support URL.
- 6Submit for review. Apple reviews charitable-donation apps carefully — expect questions about registration and the donation flow.
Asset specifications
App icon
Apple: 1024×1024 PNG, no alpha channel. Google: 512×512 PNG. A 1024×1024 source is in /icons/icon-512.png — export a 1024 version with no transparency for Apple.
Screenshots
Apple requires 6.7", 6.5" and 5.5" device frames. Google needs at least 2 phone screenshots (1080×1920 recommended). Capture Home, Programs, a Program detail, Donate, Account, and News.
Feature graphic (Google)
1024×500 PNG banner. Use the hero image with the trust name and slogan.
Splash / launch screen
Set by the wrapper (Capacitor/PWABuilder). Use the dark-green background (#1f5c45) with the centered logo.
Before launch
- • Connect and verify a real payment processor (Stripe / EasyPaisa / JazzCash) — donations cannot be charged until one is live.
- • Add the official charity registration number on the Trust & Verification page.
- • Apple and Google both require donation apps to disclose how funds are used and may ask for registration proof.
Nothing has been submitted to either store. This page is a plan and checklist only — you will review the final app and store listings, then submit from your own developer accounts.
