get to prod tasks
This commit is contained in:
88
tasks/ios-production/28-review-compliance.md
Normal file
88
tasks/ios-production/28-review-compliance.md
Normal file
@@ -0,0 +1,88 @@
|
||||
# 28. App Review Guidelines Compliance
|
||||
|
||||
meta:
|
||||
id: ios-production-28
|
||||
feature: ios-production
|
||||
priority: P1
|
||||
depends_on: []
|
||||
tags: [compliance, app-store, production]
|
||||
|
||||
objective:
|
||||
- Ensure the iOS app fully complies with Apple App Review Guidelines to pass review on first submission
|
||||
|
||||
deliverables:
|
||||
- App Review Guidelines compliance checklist
|
||||
- All guideline requirements met
|
||||
- Reviewer demo account and notes
|
||||
- Rejection risk mitigation
|
||||
|
||||
steps:
|
||||
1. Review App Store Review Guidelines:
|
||||
- Safety: no objectionable content, no physical harm
|
||||
- Performance: complete app, no crashes, accurate metadata
|
||||
- Business: no scams, proper IAP if digital goods
|
||||
- Design: minimum functionality, proper use of system features
|
||||
- Legal: privacy policy, data collection disclosure
|
||||
2. Check specific requirements:
|
||||
- App is complete and functional (no placeholders, no "coming soon")
|
||||
- All buttons and features work
|
||||
- No broken links
|
||||
- No test data visible to users
|
||||
- No beta/test labels
|
||||
3. Verify business model:
|
||||
- If subscriptions: use StoreKit or web billing (document choice)
|
||||
- If digital goods: must use in-app purchase
|
||||
- No external purchase links (unless reader apps exception)
|
||||
- No misleading pricing
|
||||
4. Check content guidelines:
|
||||
- No spam, no excessive ads
|
||||
- No misleading claims about security
|
||||
- Accurate description of AI features
|
||||
- No harassment or hate speech content
|
||||
5. Verify technical requirements:
|
||||
- App launches within reasonable time
|
||||
- No excessive battery drain
|
||||
- Proper use of background modes
|
||||
- No private API usage
|
||||
- No beta SDKs or frameworks
|
||||
6. Prepare for review:
|
||||
- Create demo account with realistic data
|
||||
- Write detailed review notes
|
||||
- Include video of app usage (optional but helpful)
|
||||
- Document any complex features for reviewer
|
||||
7. Handle common rejection reasons:
|
||||
- Guideline 2.1 (App Completeness) → all features working
|
||||
- Guideline 4.2 (Minimum Functionality) → not just a wrapper
|
||||
- Guideline 5.1.1 (Data Collection) → proper disclosures
|
||||
- Guideline 5.6 (Developer Code of Conduct) → no manipulation
|
||||
|
||||
tests:
|
||||
- Review: Internal review using Apple guidelines checklist
|
||||
- Functionality: All features tested end-to-end
|
||||
- Content: Review all user-facing text for accuracy
|
||||
|
||||
acceptance_criteria:
|
||||
- All App Store Review Guidelines requirements met
|
||||
- App is complete with no placeholder content
|
||||
- All features functional and tested
|
||||
- Demo account created with realistic data
|
||||
- Review notes prepared explaining app functionality
|
||||
- Privacy policy and terms of service linked
|
||||
- No test data, labels, or beta markings visible
|
||||
- Business model compliant with IAP guidelines
|
||||
- No private APIs or undocumented features
|
||||
- App passes internal review checklist with 0 issues
|
||||
|
||||
validation:
|
||||
- Internal review checklist → all items checked
|
||||
- Test every button and flow → all work correctly
|
||||
- Review all text → accurate, no typos, no placeholders
|
||||
- Check for test data → none visible
|
||||
- Verify no private APIs → scan with otool or similar
|
||||
|
||||
notes:
|
||||
- Apple reviewers test on physical devices with various iOS versions
|
||||
- First submission often takes 1-2 days for review
|
||||
- Have a plan for addressing rejections quickly
|
||||
- Consider using App Review acceleration for critical launches
|
||||
- Document any complex authentication flows for reviewers
|
||||
Reference in New Issue
Block a user