Getting a Rork Max App Through Store Review — Certificates to Rejections

Rork Max Build Settings and Export

iOS Build Configuration

Before building, configure these settings in Rork Max:

1. Bundle ID: com.yourcompany.appname (reverse domain notation)
2. Team ID: Found in Apple Developer Account under Membership
3. Code Sign Identity: Set to "iPhone Distribution"
4. Version: Semantic versioning like 1.0.0
5. Build Number: Increment with each build (e.g., 1, 2, 3)

Android Build Configuration

1. Package Name: com.yourcompany.appname
2. Version Code: Integer (incremented with each release)
3. Version Name: User-facing version like 1.0.0
4. Key Alias: Name of your signing key
5. Keystore File: Upload your .jks file (if not using Google Play's managed key)

Creating the Distribution Build

iOS:

1. In Rork Max, click "Archive for App Store"
2. Select your distribution certificate and provisioning profile
3. Rork generates an .ipa file (usually 2-5 minutes)
4. Download and keep it safe

Android:

1. Click "Build Release AAB" (not APK)
2. Select your keystore and key alias
3. Rork builds the signed app bundle
4. Download the .aab file

App Store Connect: Submission Walkthrough

Creating an App Listing

Log into App Store Connect and create a new app.

Core Information:

1. App Name: Maximum 30 characters. This is what appears on the App Store.
2. Subtitle: Optional, up to 30 characters. Use it to clarify your app's purpose.
3. Bundle ID: Must match your Xcode configuration exactly.
4. SKU: Internal identifier (doesn't appear to users). Use APP_NAME_001.

Metadata and Ratings

Content Rating:

Complete Apple's content rating questionnaire truthfully. Incorrect ratings cause rejections.

Questions cover:

• Violence/Cruelty
• Medical/Gambling/Alcohol
• Sexual Content
• Privacy/Location
• Ads/Analytics

Default to the most restrictive option unless your app genuinely requires otherwise.

Preparing Assets

Screenshots (Required):

You need 5-7 screenshots per device type:

• iPhone 6.7-inch (Pro Max)
• iPhone 6.1-inch (standard)
• iPhone 5.5-inch (older models)

Each screenshot should:

• Show key features in sequence
• Include text overlays explaining functionality
• Use large, readable fonts
• Avoid watermarks or UI mockups

Preview Video (Optional but recommended):

Create a 15-30 second video showing your app in action. This dramatically increases conversion rates.

Upload to YouTube, then link in App Store Connect.

Privacy Information

Apple requires a Privacy Policy URL.

Create one that covers:

• What personal data you collect (location, photos, contacts, etc.)
• Why you collect it
• How long you retain it
• User rights (deletion, access)
• Whether you share data with third parties

Many template services provide boilerplate privacy policies—customize and use one.

Description and Keywords

Description (up to 4,000 characters):

Write for real users, not Apple reviewers. Explain:

• What problem your app solves
• Key features
• Who should use it

Promotional Text (up to 170 characters):

This appears above the description. Highlight the most important new feature or benefit.

Keywords (up to 100 characters combined):

Choose 5-8 keywords. Use App Radar or Sensor Tower to find terms with search volume but low competition.

Examples:

• Weak: "app", "game" (too competitive)
• Strong: "habit tracking app", "meditation timer" (specific, searchable, less competition)

Building and Uploading

With Rork Max:

1. Create your distribution build (as described above)
2. Rork Max can upload directly to App Store Connect
3. Or manually upload via Xcode Organizer

Process:

1. Open Xcode with your Rork Max project
2. Product → Archive
3. Distribute App → App Store Connect
4. Sign in and select your team
5. Xcode uploads the build
6. Within 5-10 minutes, it appears in App Store Connect

Submission

Once all information is complete:

1. Review everything one more time
2. Click "Submit for Review"
3. Answer Apple's export compliance questions (usually "No" for standard apps)
4. Submit

Apple will send you status updates via email.

Timeline:

• Submission confirmed: Immediate
• Review begins: Within 24 hours
• Decision: Within 48 hours (usually faster)

Google Play Console: Submission Walkthrough

Creating Your App

1. Google Play Console → Create App
2. Enter app name, primary category, and target audience
3. Set up app profile (publisher details, support email)

Filling Out Store Listing

Basic Info:

1. Title: Up to 50 characters
2. Short Description: Up to 80 characters (appears in search results)
3. Full Description: Up to 4,000 characters
4. Category: Choose the most relevant category
5. Content Rating: Complete Google's rating questionnaire

Providing Assets

Screenshots (Minimum 2, maximum 8):

Google Play requires screenshots for multiple device types:

• Phone (portrait)
• 7-inch tablet (landscape)
• 10-inch tablet (landscape)

Create screenshots in these dimensions for best results.

Feature Graphic (1,024 × 500 px):

This large banner appears at the top of your store listing. Make it visually compelling and clearly communicate your app's purpose.

Preview Video:

Upload a 15-30 second video to YouTube, then link it in the console.

Privacy and Permissions

Privacy Policy URL: Required. Link to your full privacy policy.

Data Safety Section: Declare what data your app collects:

• Personal information (location, contacts, etc.)
• Sensitive information (health, financial, etc.)
• Third-party sharing

Google is strict about accurate data declarations. Misrepresenting your data practices causes rejection and potential account suspension.

Testing: Internal → Closed → Open

Before public release, Google recommends a phased rollout:

Phase 1: Internal Testing

• Only you and specified team members
• Duration: At least 48 hours

Phase 2: Closed Testing

• Invite 100-1,000 external testers
• Duration: At least 1 week
• Get feedback, fix critical bugs

Phase 3: Open Testing (Optional)

• Public beta for anyone with the link
• Duration: 1-4 weeks
• Generate buzz, find edge-case bugs

Each phase builds confidence in your app's stability before the full release.

Release to Production

Once testing is complete:

1. Navigate to Production Release
2. Create a new release
3. Select your signed AAB file
4. Review all store listing details one final time
5. Choose rollout strategy:
   • 100% immediate rollout (typical for first release)
   • Staged rollout (5% → 25% → 100% over days)
6. Submit for review

Google typically reviews within 2-4 hours for existing publishers, or up to 24 hours for new apps.

Common Rejection Reasons and Fixes

Apple App Store Rejections

1. Privacy Policy Missing or Incorrect

What triggers it:

• No privacy policy URL
• Privacy policy doesn't match actual data collection
• Using location/photos/calendar but not disclosing it

How to fix:

• Create a clear privacy policy
• List every data point your app accesses
• Ensure Info.plist matches declared permissions
• Test on a real device—do permission prompts appear?

2. Incomplete App

What triggers it:

• Buttons that don't work
• Features shown in screenshots that don't exist
• Login screens that don't function

How to fix:

• Test every button, link, and feature
• Use Testflight (Apple's beta testing platform) with real users
• Create a testing checklist and verify every item

3. Performance or Stability Issues

What triggers it:

• App crashes on launch
• Crashes when using specific features
• Unresponsive UI or 5+ second hangs

How to fix:

• Run on real iPhone (simulator testing misses some issues)
• Use Xcode's Organizer to check crash logs
• Profile with Instruments for memory leaks
• Test on older iPhones (A12 and earlier) where performance issues are most visible

4. Metadata Issues

What triggers it:

• Screenshots show outdated UI
• Screenshots contain misleading text
• App name in screenshots differs from listing

How to fix:

• Screenshots should match your current app version exactly
• Don't use mock-ups or designer renderings
• Use actual device screenshots
• Have a native English speaker review all text

5. Design Issues

What triggers it:

• App doesn't rotate (landscape not supported)
• Text too small for accessibility
• Layout breaks on iPad

How to fix:

• Support both portrait and landscape
• Use at least 11-point font for body text
• Test on iPad (even if not submitting for iPad)
• Test on iPhone 14 Pro and iPhone SE to cover size extremes

Google Play Store Rejections

1. Policy Violations

Common issues:

• Malware, spyware, or privacy-invasive code
• Misleading descriptions
• Fake ratings or reviews
• Sexual/hateful/dangerous content

How to fix:

• Review Google Play Policies thoroughly
• Never scrape user reviews or manipulate ratings
• Ensure description accurately reflects features
• Don't request excessive permissions

2. Broken Functionality

What triggers it:

• App crashes immediately
• Core features don't work
• Login fails on all devices
• Network requests fail

How to fix:

• Test on real Android devices (emulator misses some issues)
• Test on Android 8.0, 11, and 14 minimum
• Monitor logcat for crashes
• Use Firebase Crashlytics for production monitoring

3. Permission Misuse

What triggers it:

• Accessing location without explicit user permission
• Recording audio without consent
• Accessing contacts/calendar without justification

How to fix:

• Request each permission explicitly at runtime
• Only request permissions you actually use
• Document why each permission is needed
• Test that app functions with permissions denied

4. Intellectual Property Issues

What triggers it:

• Using trademarked logos without permission
• Copying another app's design/content
• Using music/images without licenses

How to fix:

• Use original assets or properly licensed content
• Avoid using Apple/Google logos
• Credit all third-party libraries
• Review Open Source licenses (GPL conflicts with App Store)

Rork Max-Specific Considerations

When submitting Rork-built apps:

1. Code Bloat: Rork Max generates efficient code, but custom native modules can add significant bundle size. Aim for <100 MB.
2. Dependencies: Verify that Rork's dependencies (Expo modules, React Native packages) don't violate App Store rules.
3. Permissions: Review AndroidManifest.xml and Info.plist—remove unused permissions.
4. Testing: Export a test version and run through all features before final submission.

Post-Launch Operations: ASO, Reviews, and Updates

App Store Optimization (ASO)

ASO is the process of optimizing your app to rank higher in search results.

Keyword Strategy:

1. Use App Radar or Sensor Tower to research keywords
2. Target keywords with:
   • 1,000+ monthly searches
   • Low competition (difficulty < 50)
   • Relevance to your app
3. Include in title, subtitle, and keyword field

Example:

• Instead of "Fitness App", use "Running Tracker: GPS Distance & Pace"
• Captures "running tracker", "gps fitness", "distance running"

Screenshot Strategy:

A/B test different screenshots:

• Set A: Feature-focused
• Set B: Benefit-focused

After 2 weeks, compare download conversion. Switch to whichever converts better.

User Review Management

Monitoring:

1. Set up alerts for 1-star and 5-star reviews
2. Read new reviews within 24 hours
3. Identify patterns (e.g., "crash on login")

Responding:

• To negative reviews: Acknowledge the issue, apologize, ask for details
• To positive reviews: Thank them, ask them to recommend to friends
• Keep responses professional and brief

Improving Ratings:

Ask satisfied users to leave reviews:

• Add in-app prompt after successful action
• Time the prompt carefully (not on first launch, but after user experiences value)
• Make it easy: Direct link to App Store review page

Update Cadence

First 30 Days:

• Weekly updates
• Focus: Bug fixes, performance
• Announce: "Improved stability" in release notes

Months 2-3:

• Bi-weekly updates
• Focus: New features responding to feedback
• Result: App stays in "What's New" section

Months 4+:

• Monthly updates
• Focus: New features, maintenance
• Minimum: Monthly for continued discoverability

Analytics Integration

Use Rork Max's built-in analytics to understand user behavior:

1. Retention: What % of Day 1 users return on Day 7? (Good = 25%+)
2. Feature Usage: Which features see highest engagement?
3. Crash Rate: Monitor in-app crashes (target: <0.5%)
4. Session Length: Are users spending expected time in app?

Act on this data:

• Low retention? → Onboarding may need improvement
• Unused features? → Consider removing or repurposing
• High crash rate? → Investigate logs, push emergency update

Timeline: From Submission to Live

Rejections add 3-5 days per rejection. Plan accordingly—submit at least 2 weeks before any critical launch date.

Pre-Launch Checklist

Before submitting to either store:

• [ ] App runs without crashes for 5 minutes
• [ ] All buttons/links function correctly
• [ ] Screenshots match current app UI
• [ ] Privacy policy written and linked
• [ ] Tested on at least 2 physical devices
• [ ] Tested on both portrait and landscape
• [ ] Permissions in code match declarations
• [ ] App name, description, keywords finalized
• [ ] Version number set correctly
• [ ] No debug logs or console output
• [ ] TestFlight beta tested with 5+ external users
• [ ] Analytics tracking functional
• [ ] Crash monitoring set up (Sentry, Firebase)

Check every item before hitting submit.

Conclusion

Publishing your Rork Max app is achievable with preparation and attention to detail. The process is:

1. Set up: Developer accounts (1-2 days)
2. Build: Create distribution-ready app (3-7 days)
3. Submit: Fill out store listings, upload build (1-2 days)
4. Wait: Apple and Google review (1-4 days)
5. Launch: App goes live, users download

After launch, your work continues: monitoring reviews, responding to user feedback, releasing updates, and optimizing for discoverability.

The majority of rejections are preventable with careful testing and following policies. Use this guide as your checklist, and you'll avoid the most common pitfalls that trap indie developers.

Your app is ready to reach real users. Submit with confidence.