App store checklist (table)
Download the latest files:
| Sequence | Priority | Phase | Store | Category | Activity | Description | Deliverable | How To Do It | Dependencies | Owner | Target Date | Cost INR | Cost USD | Timeline | Status | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | P0 | Pre-Launch | Both | Legal | Create Privacy Policy | Required by both stores. Must detail data collection, storage, usage, third-party sharing, user rights (GDPR/CCPA). | 1. Use privacy policy generator (iubenda.com or privacypolicies.com)<br />2. Customize for your data practices<br />3. Host on your website/GitHub Pages<br />4. Add URL to app stores and in-app settings | Website or hosting for policy page | 0-2000 | 0-25 | 1-2 days | Not Started | Free generators available. Must be publicly accessible URL | |||
| 2 | P0 | Pre-Launch | Both | Legal | Create Terms of Service | User agreement for app usage. Required for both stores. | 1. Use ToS generator (termly.io or similar)<br />2. Include user conduct rules, liability limitations<br />3. Cover community guidelines<br />4. Host publicly | Privacy Policy completed | 0-2000 | 0-25 | 1-2 days | Not Started | Can use free template and customize | |||
| 3 | P0 | Pre-Launch | iOS | Legal | Create EULA (iOS) | End User License Agreement required for iOS apps. | 1. Apple provides standard EULA<br />2. Can customize if needed<br />3. Add to App Store Connect metadata | None | 0 | 0 | 1 day | Not Started | Can use Apple's standard EULA | |||
| 4 | P0 | Pre-Launch | Android | Accounts | Create Google Play Developer Account | Required to publish on Play Store. One-time registration fee. | 1. Go to play.google.com/console<br />2. Sign in with Google account<br />3. Pay $25 one-time fee<br />4. Complete account details<br />5. Verify identity (can take 48hrs) | Google account with payment method | 2075 | 25 | 2-3 days | Not Started | $25 one-time fee. Use business account if possible | |||
| 5 | P0 | Pre-Launch | iOS | Accounts | Create Apple Developer Account | Required to publish on App Store. Annual subscription. | 1. Go to developer.apple.com/enroll<br />2. Sign in with Apple ID<br />3. Pay $99/year<br />4. Complete enrollment (can take 48hrs) | Apple ID + Payment method | 8225 | 99 | 2-5 days | Not Started | $99/year recurring. Required for iOS distribution | |||
| 6 | P0 | Pre-Launch | Both | Marketing | Set Up Waitlist Landing Page | Gauge interest before launch. Collect early adopters emails. | 1. Create landing page on Framer (free tier)<br />2. Add compelling headline and app preview<br />3. Integrate Formspree/Formsspark for email collection<br />4. Add social proof and features preview<br />5. Set up thank you page with social sharing | Domain (optional) | 0-1500 | 0-18 | 1-2 days | Not Started | Framer free tier works. Formsspark free: 250 submissions/month | |||
| 7 | P1 | Pre-Launch | Both | Marketing | Set Up Pre-Launch Email Sequence | Nurture waitlist subscribers until launch. | 1. Use Loops.so or Mailchimp for email automation<br />2. Create welcome email for signup<br />3. Create 2-3 teaser emails with feature previews<br />4. Create launch day announcement email<br />5. Schedule sequence | Waitlist page + Email tool | 0-2500 | 0-30 | 1-2 days | Not Started | Loops.so free: 1000 contacts. Mailchimp free: 500 contacts | |||
| 8 | P0 | Pre-Launch | Both | Branding | Finalize App Name | Grove - ensure name is available on both stores. | 1. Search Play Store for 'Grove'<br />2. Search App Store for 'Grove'<br />3. If taken, consider 'Grove Community' or similar<br />4. Update app.json with final name | None | 0 | 0 | 1 day | In Progress | Current name: Grove | |||
| 9 | P0 | Pre-Launch | Both | Branding | Create App Icon | 1024x1024 icon for stores. Multiple sizes for devices. | 1. Design 1024x1024 master icon<br />2. Use icon generators for all sizes<br />3. Android: Adaptive icon (foreground + background)<br />4. iOS: Solid corners (system rounds them)<br />5. Update assets in expo project | Branding guidelines | 0-15000 | 0-180 | 2-3 days | In Progress | Icons exist in docs/assets. Verify final quality | |||
| 10 | P0 | Pre-Launch | Android | Branding | Create Feature Graphic (Android) | 1024x500 banner for Play Store listing. | 1. Design landscape banner<br />2. Include app name and tagline<br />3. Showcase key feature or screenshots<br />4. Follow Google's design guidelines | App Icon + Branding | 0-8000 | 0-100 | 1-2 days | Not Started | Required for Play Store. Can use Canva free | |||
| 11 | P0 | Pre-Launch | Both | Assets | Create Professional App Screenshots | Store listing screenshots - CRITICAL for conversion. | 1. Use TheScreenshotFirstCompany or similar service<br />2. Capture 8 key screens per device size<br />3. Add compelling captions and context frames<br />4. A/B test different styles<br />5. Include lifestyle/mockup versions | Working app + Device mockups | 8000-40000 | 100-500 | 3-5 days | Not Started | Professional screenshots increase downloads 25-35%. Worth the investment. | |||
| 12 | P1 | Pre-Launch | Both | Assets | Create App Preview Video | 15-30 second video showing app in action. | 1. Screen record key user flows<br />2. Add captions and music<br />3. iOS: 1920x1080 or device resolution<br />4. Android: YouTube video link<br />5. Edit with iMovie/Premiere/Canva | Working app | 0-10000 | 0-120 | 2-3 days | Not Started | Optional but highly recommended. Free tools available | |||
| 13 | P0 | Pre-Launch | iOS | Content | Write App Store Description with ASO | Short and full description optimized for search. | 1. Use AppTweak, SensorTower, or ASO.dev for keyword research<br />2. Write compelling 80-char short description<br />3. Write 4000-char full description with keywords<br />4. Highlight key features with bullet points<br />5. Include call-to-action | Finalized feature list + ASO tool | 0-8000 | 0-100 | 1-2 days | Not Started | ASO tools: AppTweak $69/mo, SensorTower $79/mo. Free trials available. | |||
| 14 | P1 | Pre-Launch | iOS | Content | Optimize Keywords (iOS) | 100-character keyword field for App Store search. | 1. Research competitor keywords<br />2. Use ASO tool for keyword suggestions<br />3. Prioritize high-traffic low-competition keywords<br />4. Include location terms if relevant<br />5. Update keywords after launch based on data | ASO tool subscription | 0-5000 | 0-60 | 1 day | Not Started | Keywords are iOS only - very important for discoverability | |||
| 15 | P1 | Pre-Launch | Both | Content | Write Release Notes | What's new in this version for each release. | 1. List new features<br />2. Mention bug fixes<br />3. Keep it concise and user-friendly<br />4. Update with each release | Version planning | 0 | 0 | 1 day | Not Started | Keep template ready for future releases | |||
| 16 | P0 | Pre-Launch | Both | Technical | Configure App Bundle ID / Package Name | Unique identifier for The Grove app. Cannot change after publish. | 1. Choose format: com.grove.app or similar<br />2. Update app.json ios.bundleIdentifier<br />3. Update app.json android.package<br />4. Ensure consistency | None | 0 | 0 | 1 hour | In Progress | Current: com.grove.app - verify availability | |||
| 17 | P0 | Pre-Launch | Android | Technical | Configure App Signing (Android) | Generate and secure upload key for Play Store. | 1. EAS Build handles this automatically<br />2. Or generate manually: keytool -genkey<br />3. Store keystore securely (backup!)<br />4. Never lose the keystore | EAS or local build setup | 0 | 0 | 1-2 hours | Not Started | CRITICAL: Backup keystore. Loss = new app listing | |||
| 18 | P0 | Pre-Launch | iOS | Technical | Configure App Signing (iOS) | Certificates and provisioning profiles. | 1. EAS Build handles automatically<br />2. Or manually: Create distribution certificate<br />3. Create App Store provisioning profile<br />4. Match bundle ID exactly | Apple Developer Account | 0 | 0 | 1-2 hours | Not Started | EAS simplifies this significantly | |||
| 19 | P0 | Pre-Launch | Both | Technical | Set Up EAS Build | Configure Expo Application Services for builds. | 1. Install eas-cli: npm install -g eas-cli<br />2. Run: eas login<br />3. Run: eas build:configure<br />4. Configure eas.json for production builds<br />5. Test with: eas build --platform all | Expo account + Developer accounts | 0 | 0 | 1-2 hours | Not Started | Free tier: 30 builds/month | |||
| 20 | P0 | Pre-Launch | Android | Technical | Create Production Build (Android) | Generate AAB file for Play Store. | 1. Update version in app.json<br />2. Run: eas build --platform android --profile production<br />3. Wait for build to complete<br />4. Download AAB file | EAS Build configured + App Signing | 0 | 0 | 30-60 mins | Not Started | AAB required (not APK) for new apps | |||
| 21 | P0 | Pre-Launch | iOS | Technical | Create Production Build (iOS) | Generate IPA file for App Store. | 1. Update version in app.json<br />2. Run: eas build --platform ios --profile production<br />3. Wait for build to complete<br />4. Submit directly or download IPA | EAS Build configured + App Signing | 0 | 0 | 30-60 mins | Not Started | Can submit directly from EAS | |||
| 22 | P1 | Pre-Launch | Both | Technical | Configure Push Notifications | Set up FCM and APNS for production. | 1. Create Firebase project (if not exists)<br />2. Download google-services.json<br />3. Create APNs key in Apple Developer<br />4. Upload to Expo/EAS<br />5. Test notifications | Firebase account + Apple Developer | 0 | 0 | 2-4 hours | Not Started | FCM is free. APNS included in dev account | |||
| 23 | P0 | Pre-Launch | Both | Technical | Set Up In-App Analytics | Track user behavior, retention, and drop-off points. | 1. Integrate Mixpanel, Amplitude, or PostHog<br />2. Track key events: signup, create_community, invite, event_create<br />3. Set up funnels for core user journeys<br />4. Create retention cohorts<br />5. Set up dashboards for daily review | Analytics account | 0-10000 | 0-120 | 2-4 hours | Not Started | PostHog free: 1M events/mo. Mixpanel free: 100K events/mo. CRITICAL for understanding churn. | |||
| 24 | P1 | Pre-Launch | Both | Technical | Set Up Error Monitoring | Configure Sentry or similar for production. | 1. Create Sentry project<br />2. Add expo-sentry package<br />3. Configure dsn and settings<br />4. Test error reporting<br />5. Set up alerts | Sentry account | 0 | 0 | 1-2 hours | Not Started | Free tier: 5K errors/month | |||
| 25 | P0 | Pre-Launch | Both | Backend | Configure Production Supabase | Ensure Supabase is production-ready. | 1. Enable RLS on all tables<br />2. Set up proper auth redirect URLs<br />3. Configure rate limiting<br />4. Set up database backups<br />5. Review security policies | Supabase project | 0-2000/mo | 0-25/mo | 2-4 hours | Not Started | Free tier sufficient for launch. Upgrade as needed | |||
| 26 | P0 | Pre-Launch | Both | Backend | Set Environment Variables | Configure production environment. | 1. Set SUPABASE_URL and ANON_KEY<br />2. Configure GOOGLE_CLIENT_ID<br />3. Set up API keys in EAS secrets<br />4. Verify all production URLs | Supabase + Auth providers | 0 | 0 | 1-2 hours | Not Started | Use EAS Secrets for sensitive values | |||
| 27 | P1 | Pre-Launch | Both | Marketing | Set Up Feedback Board (Canny) | Collect feature requests and feedback from users. | 1. Create Canny account (free tier)<br />2. Set up feedback board categories<br />3. Customize branding<br />4. Add feedback link in app settings<br />5. Configure email notifications for new feedback | Canny account | 0 | 0 | 1-2 hours | Not Started | Canny free: 100 tracked users. Essential for product roadmap. | |||
| 28 | P2 | Pre-Launch | Android | Testing | Internal Testing (Android) | Test with internal team before public. | 1. Create internal test track in Play Console<br />2. Upload AAB<br />3. Add tester emails (up to 100)<br />4. Share opt-in link<br />5. Gather feedback | Production build + Developer account | 0 | 0 | 2-3 days | Not Started | Fastest approval, no review needed | |||
| 29 | P2 | Pre-Launch | iOS | Testing | TestFlight Testing (iOS) | Beta testing with TestFlight. | 1. Upload build to App Store Connect<br />2. Add internal testers (up to 100)<br />3. Submit for external beta (up to 10,000)<br />4. Gather feedback via TestFlight | Production build + Developer account | 0 | 0 | 3-5 days | Not Started | External TestFlight requires review | |||
| 30 | P0 | Launch | Android | Submission | Complete Play Store Listing | Fill in all required store listing details. | 1. Upload app icon<br />2. Upload feature graphic<br />3. Upload professional screenshots<br />4. Write optimized descriptions<br />5. Complete content rating questionnaire<br />6. Set pricing (free)<br />7. Select countries | All assets + Descriptions ready | 0 | 0 | 2-3 hours | Not Started | Content rating questionnaire takes 15-20 mins | |||
| 31 | P0 | Launch | iOS | Submission | Complete App Store Listing | Fill in all App Store Connect details. | 1. Create new app in App Store Connect<br />2. Upload screenshots for all sizes<br />3. Write descriptions<br />4. Add optimized keywords (100 chars max)<br />5. Set pricing (free)<br />6. Answer export compliance questions | All assets + Descriptions ready | 0 | 0 | 2-3 hours | Not Started | Keywords are iOS only - choose wisely | |||
| 32 | P0 | Launch | Android | Submission | Submit to Google Play Review | Submit app for Google Play review. | 1. Complete all store listing sections<br />2. Upload AAB to production track<br />3. Answer data safety questionnaire<br />4. Submit for review<br />5. Wait for approval (usually 1-3 days) | Complete store listing + Build | 0 | 0 | 1-3 days | Not Started | First review may take longer | |||
| 33 | P0 | Launch | iOS | Submission | Submit to App Store Review | Submit app for App Store review. | 1. Complete all App Store Connect sections<br />2. Upload build via EAS or Transporter<br />3. Select build for review<br />4. Answer review questions<br />5. Submit for review (usually 1-2 days) | Complete store listing + Build | 0 | 0 | 1-7 days | Not Started | First review may take longer. Common rejections: crashes, broken links | |||
| 34 | P1 | Launch | Both | Submission | Respond to Review Feedback | Handle rejection or requests. | 1. Read rejection reason carefully<br />2. Fix issues mentioned<br />3. Submit updated build<br />4. Write explanation in Resolution Center<br />5. Resubmit for review | Reviewer feedback | 0 | 0 | 1-3 days | Not Started | Keep response professional and detailed | |||
| 35 | P0 | Post-Launch | Both | Engagement | Set Up Welcome Email Sequence | Onboard new users and drive engagement. | 1. Use Loops.so for email automation<br />2. Welcome email (immediate): Thank user, highlight key features<br />3. Day 2: How to create your first community<br />4. Day 5: Tips for engaging members<br />5. Day 7 inactivity: Ask for feedback, offer help<br />6. Day 14: Feature education (events, finance)<br />7. Day 30: Ask for app store review | Loops.so account + Email templates | 0-4000 | 0-50 | 2-3 days | Not Started | Loops.so free: 1000 contacts. Email sequences increase retention 30%+ | |||
| 36 | P1 | Post-Launch | Both | Marketing | Create Landing Page | Website for app promotion and SEO. | 1. Create simple landing page (Framer/Carrd.co free)<br />2. Include screenshots and features<br />3. Add store badges with links<br />4. Add privacy policy link<br />5. Set up domain (optional) | Published app | 0-5000 | 0-60 | 1-2 days | Not Started | Can use free hosting initially | |||
| 37 | P1 | Post-Launch | Both | Marketing | Set Up Social Media Presence | Create presence for Grove. | 1. Create Twitter/X account (@GroveCommunity)<br />2. Create Instagram account<br />3. Create LinkedIn page (optional)<br />4. Plan content calendar<br />5. Share updates, tips, and user stories | Published app | 0 | 0 | 1-2 days | Not Started | Organic social is free | |||
| 38 | P2 | Post-Launch | iOS | Marketing | Set Up App Store Optimization (ASO) | Ongoing optimization for store visibility. | 1. Monitor keyword rankings weekly<br />2. A/B test icons and screenshots<br />3. Encourage ratings and reviews<br />4. Respond to all user reviews<br />5. Update keywords based on performance data | Published app + ASO tool | 0-8000/mo | 0-100/mo | Ongoing | Not Started | AppTweak or SensorTower for tracking | |||
| 39 | P1 | Post-Launch | Both | Marketing | Launch Day Social Campaign | Maximize visibility on launch day. | 1. Prepare launch announcement posts<br />2. Email waitlist with download links<br />3. Post on Product Hunt (optional)<br />4. Share in relevant communities (Reddit, Facebook groups)<br />5. Reach out to early adopters for reviews | Published app + Social accounts | 0-3000 | 0-35 | 1 day | Not Started | Product Hunt can drive significant traffic | |||
| 40 | P2 | Post-Launch | Both | Marketing | Content Marketing Strategy | Build organic traffic through content. | 1. Start a blog (Medium or own site)<br />2. Write about community management tips<br />3. Case studies of successful communities<br />4. SEO-optimized articles<br />5. Share on social media | Website/blog platform | 0-5000 | 0-60 | Ongoing | Not Started | Long-term strategy. Takes 3-6 months to see results | |||
| 41 | P1 | Post-Launch | Both | Marketing | Influencer/Community Outreach | Partner with community leaders. | 1. Identify local community group leaders<br />2. Offer free premium features for testimonials<br />3. Create case studies together<br />4. Get video testimonials<br />5. Feature on landing page | Published app + Relationship building | 0-15000 | 0-180 | Ongoing | Not Started | Word of mouth is powerful for community apps | |||
| 42 | P1 | Post-Launch | Both | Operations | Set Up Customer Support | Handle user questions and issues. | 1. Create support email (support@grove.app)<br />2. Set up FAQ/Help section in app<br />3. Configure auto-replies<br />4. Create response templates<br />5. Monitor reviews for issues | Email setup | 0-3000/mo | 0-35/mo | 1-2 days | Not Started | Start with free email. Intercom later | |||
| 43 | P1 | Post-Launch | Both | Operations | Set Up Review Monitoring | Track and respond to store reviews. | 1. Enable email notifications in store consoles<br />2. Use AppFollow or similar (optional)<br />3. Respond to negative reviews within 24h<br />4. Thank positive reviewers<br />5. Track trends and common issues | Published app | 0-5000/mo | 0-60/mo | Ongoing | Not Started | Manual monitoring is free. Reviews impact ranking. | |||
| 44 | P1 | Post-Launch | Both | Operations | Create Release Process | Standard process for updates. | 1. Document version numbering scheme<br />2. Create release checklist<br />3. Set up staging environment<br />4. Plan testing before each release<br />5. Communicate updates to users | Published app | 0 | 0 | 1 day | Not Started | Document in team wiki/docs | |||
| 45 | P1 | Post-Launch | Both | Growth | In-App Review Prompts | Ask happy users for reviews at right moments. | 1. Integrate expo-store-review<br />2. Trigger after positive moments (event success, milestone)<br />3. Don't ask too early (wait 7+ days)<br />4. Respect user choice (don't ask again if declined)<br />5. A/B test timing | Published app | 0 | 0 | 2-4 hours | Not Started | Good reviews boost ranking significantly | |||
| 46 | P2 | Post-Launch | Both | Growth | Set Up Referral Program | In-app referral for organic growth. | 1. Design referral flow (unique invite links)<br />2. Track referrals in Supabase<br />3. Reward referrers (premium features/recognition)<br />4. Show referral leaderboard<br />5. Promote within app | App with user base | 0-5000 | 0-60 | 3-5 days | Not Started | Can implement with Supabase. Most powerful growth lever. | |||
| 47 | P2 | Post-Launch | Both | Growth | Community Building (Meta) | Build a community for Grove users. | 1. Create Discord/Slack for power users<br />2. Host virtual meetups/webinars<br />3. Share best practices and tips<br />4. Gather feedback directly<br />5. Create ambassador program | Published app + Community platform | 0 | 0 | Ongoing | Not Started | Meta-community of community organizers | |||
| 48 | P2 | Post-Launch | Both | Compliance | GDPR Compliance | European data protection requirements. | 1. Add cookie consent (if web)<br />2. Allow data export from settings<br />3. Allow account deletion<br />4. Document data processing<br />5. Update privacy policy | Privacy Policy + App functionality | 0-8000 | 0-100 | 2-3 days | Not Started | Required if targeting EU users | |||
| 49 | P2 | Post-Launch | Both | Compliance | COPPA Compliance | If app may be used by children. | 1. Determine if app targets children<br />2. Add age verification if needed<br />3. Limit data collection from minors<br />4. Update privacy policy | Privacy Policy | 0 | 0 | 1 day | Not Started | Grove targets adults (community organizers) | |||
| 50 | P3 | Post-Launch | Both | Growth | Localization | Translate app for new markets. | 1. Identify target markets (Hindi, Tamil, etc.)<br />2. Extract strings for translation<br />3. Use professional translators or Lokalise<br />4. Update store listings per language<br />5. Test with native speakers | Published app + Translation service | 10000-50000 | 120-600 | 1-2 weeks | Not Started | Can significantly expand market. Start with 1-2 languages. | |||
| 51 | P3 | Post-Launch | Both | Growth | PR and Media Outreach | Get press coverage for credibility. | 1. Write press release<br />2. Create media kit (screenshots, logos, story)<br />3. Identify relevant tech/local journalists<br />4. Pitch story angle (local community revival)<br />5. Prepare for interviews | Published app + Media kit | 0-25000 | 0-300 | Ongoing | Not Started | PR can be expensive. Start with organic outreach. | |||
| 52 | P3 | Post-Launch | Both | Monetization | Plan Premium Features | Roadmap for monetization. | 1. Analyze free tier usage<br />2. Identify power user features (analytics, export)<br />3. Design subscription tiers<br />4. Integrate Stripe/RevenueCat<br />5. A/B test pricing | Published app + User data | 5000-15000 | 60-180 | 2-4 weeks | Not Started | Wait until you have active users. Don't rush monetization. | |||
| 53 | P1 | Post-Launch | Both | Analytics | Set Up Funnel Tracking | Understand where users drop off. | 1. Define key funnels: Signup > Create Community > Invite > First Event<br />2. Track each step in analytics<br />3. Identify biggest drop-off points<br />4. Create weekly funnel reports<br />5. Prioritize improvements based on data | In-app analytics set up | 0 | 0 | 1-2 days | Not Started | Critical for understanding user behavior | |||
| 54 | P1 | Post-Launch | Both | Analytics | Retention Analysis | Track cohort retention to measure product health. | 1. Set up cohort analysis in analytics tool<br />2. Track Day 1, Day 7, Day 30 retention<br />3. Compare retention by acquisition source<br />4. Identify features that correlate with retention<br />5. Focus on improving D7 retention first | In-app analytics set up | 0 | 0 | 1 day | Not Started | Retention is the key metric for product-market fit | |||
| 55 | P1 | Post-Launch | Both | Analytics | Weekly Analytics Review | Regular check on app health. | 1. Schedule weekly 30-min review<br />2. Check: DAU/WAU, new signups, retention<br />3. Review funnel drop-offs<br />4. Read new feedback/reviews<br />5. Prioritize action items | Analytics + Feedback tools | 0 | 0 | Ongoing | Not Started | Discipline to review data regularly is key | |||
| 56 | P0 | Pre-Launch | iOS | Compliance | Complete App Privacy Details (iOS) | Fill out App Store Connect privacy labels based on data collection and usage. | App Privacy section completed | App Store Connect > App Privacy > answer data types, tracking, data linked to user. Align with privacy policy. | Privacy Policy completed | 0 | 0 | 1 day | Not Started | Required for App Review. Must match actual SDK usage. | ||
| 57 | P0 | Pre-Launch | Android | Compliance | Complete Data Safety Form (Android) | Declare data collection, sharing, and security practices in Play Console. | Data Safety form submitted | Play Console > App content > Data safety. Map to privacy policy and SDKs used. | Privacy Policy completed | 0 | 0 | 1 day | Not Started | Required before production release. | ||
| 58 | P0 | Pre-Launch | Both | Submission | Prepare App Review Notes + Demo Account | Provide reviewer instructions and test credentials if login is required. | Review notes + test account | Create reviewer account, list steps to access core features, add in App Store Connect and Play Console. | Working build + QA sign-off | 0 | 0 | 1 day | Not Started | Common reason for rejection if missing. | ||
| 59 | P1 | Pre-Launch | Both | Technical | Add Support & Marketing URLs | Set Support URL and Marketing URL in store listings. | Support + Marketing URLs live | Use landing page or docs site. Ensure privacy policy URL is reachable. | Landing page or docs hosting | 0-1500 | 0-18 | 1 day | Not Started | Support URL is mandatory for iOS. | ||
| 60 | P1 | Pre-Launch | Both | Testing | Release Build Smoke Test | Install the production build and complete critical flows end-to-end. | Signed QA checklist | Test login, community creation, invite/join, events, feed, finance, profile. | Production build ready | 0 | 0 | 1 day | Not Started | Prevents last-minute store rejections. | ||
| 61 | P1 | Pre-Launch | iOS | Compliance | App Tracking Transparency (if tracking) | Show ATT prompt if any tracking is used; otherwise document why not needed. | ATT prompt or N/A note | If using tracking SDKs, add ATT prompt and update privacy labels. | Analytics/SDK list finalized | 0 | 0 | 1 day | Not Started | Required if tracking users across apps/sites. |