How to Publish Your Rork App to App Store and Google Play

Publishing your Rork application to app stores is a crucial step in reaching users. This guide covers the complete process for both Apple App Store and Google Play Store, including account setup, build preparation, submission, and post-launch management.

Rork Original vs Rork Max

Rork offers two publishing paths with different features and pricing:

Rork Original

Rork Original allows you to publish to both App Store and Google Play Store with full control over the submission process. You manage developer accounts, submissions, and app store pages directly.

Features:

• Publish to both iOS (App Store) and Android (Google Play)
• Full customization of app store listings
• Direct control over update scheduling
• No platform restrictions

Requirements:

• Apple Developer Program membership ($99/year)
• Google Play Developer account ($25 one-time)
• Rork account for code generation

Rork Max

Rork Max simplifies the publishing process with just 2 clicks. However, it currently supports Apple App Store publishing only.

Features:

• 2-click App Store publishing
• Rork handles submission logistics
• Simplified version management
• Apple-optimized release process

Limitations:

• App Store only (iOS)
• Higher per-app costs than Rork Original
• Less customization of store listing

Recommendation: Use Rork Original if you need both iOS and Android presence. Use Rork Max if you want the simplest iOS publishing experience and don't need Android.

Developer Account Setup

Apple Developer Program

1. Visit developer.apple.com and click "Account"
2. Sign in with Apple ID or create a new one
3. Enroll in Apple Developer Program ($99/year)
4. Complete your developer profile with company information
5. Agree to legal agreements for app development
6. Wait for approval (usually instant, sometimes 24-48 hours)

Once approved, you can:

• Create app identifiers
• Set up certificates and provisioning profiles
• Manage development and distribution certificates

Google Play Console

1. Visit play.google.com/console and sign in with Google account
2. Create a new developer account ($25 one-time fee)
3. Set up your developer profile with your name and contact information
4. Agree to Google Play policies and developer agreement
5. Create a Google Wallet account for payments

Certificate and Provisioning Files

For iOS apps:

• Development Certificate: Used during testing and Expo Go development
• Distribution Certificate: Required for App Store submissions
• Provisioning Profiles: Link your app ID, certificate, and devices

For Android apps:

• Upload Key: Used to sign your app for Google Play
• App Signing Key: Google Play manages this for security

Rork and EAS (Expo Application Services) can help generate and manage these files automatically.

Build Preparation

Before submitting your app, ensure it's production-ready:

Code Review

1. Test thoroughly on both iOS and Android devices
2. Check for platform-specific issues (permissions, navigation back buttons, safe area)
3. Test all user flows from signup through main features
4. Performance testing ensure smooth 60 FPS on older devices
5. Memory testing check for leaks with extended use

App Configuration

Update your app.json with correct metadata:

{
  "expo": {
    "name": "My Awesome App",
    "slug": "my-awesome-app",
    "version": "1.0.0",
    "description": "A description of your app",
    "icon": "./assets/icon.png",
    "splash": {
      "image": "./assets/splash.png",
      "resizeMode": "contain",
      "backgroundColor": "#ffffff"
    },
    "ios": {
      "bundleIdentifier": "com.yourcompany.myapp",
      "supportsTabletAndPhone": true
    },
    "android": {
      "package": "com.yourcompany.myapp",
      "versionCode": 1
    }
  }
}

Version Numbers

• iOS: Uses semantic versioning (1.0.0, 1.0.1, 1.1.0)
• Android: Uses both versionCode (internal, auto-increment) and versionName (visible to users)

Each update requires incrementing version numbers.

Building with EAS

eas build --platform ios
eas build --platform android

EAS compiles your React Native code to native binaries:

• Handles all native code compilation
• Manages code signing with your certificates
• Produces .ipa (iOS) and .aab (Android) files
• Stores builds in your EAS dashboard for easy access

Submitting to App Store (iOS)

Create App Record

1. Log into App Store Connect at appstoreconnect.apple.com
2. Click "My Apps" then "+ New App"
3. Select iOS as the platform
4. Fill in app information:
   • App Name
   • Bundle ID (must match bundleIdentifier in app.json)
   • SKU (unique identifier for your records)
   • Primary Category
   • Secondary Category (optional)

Fill App Information

Pricing and Availability:

• Set pricing (free, or choose tier)
• Select territories where app is available
• Choose availability date

Localization:

• Add App Preview, Screenshots, and Description for each language
• Use high-quality 5.5-inch iPhone screenshots
• Write compelling, honest descriptions

App Privacy:

• Declare data collection practices
• List analytics, advertising, and tracking implementations
• Be truthful about privacy practices

Prepare for Submission

1. Build number: Create a build in TestFlight first

   • Upload your build via Xcode or EAS
   • Wait for processing (can take several minutes)

2. General App Information:

   • Category
   • Content rating questionnaire
   • Age rating (fill out accurately)

3. App Review Information:

   • Demo account credentials (if app has login)
   • Notes for reviewers
   • Contact information
   • Website URL and privacy policy

Submit for Review

1. Complete all required fields (marked with red asterisks)
2. Review app information for accuracy
3. Agree to App Store Review Guidelines
4. Click "Submit for Review"
5. Wait for review (typically 24-48 hours)

Submitting to Google Play

Create App on Google Play Console

1. Go to Google Play Console and sign in
2. Click "Create App"
3. Enter app name and select default language
4. Accept declarations about app content

Fill Store Listing

1. Add screenshots:

   • Upload 4-8 screenshots for phones
   • Landscape and tablet screenshots optional
   • Use actual app screenshots, not marketing images

2. Write app description:

   • Short description (80 characters max)
   • Full description (4,000 characters max)
   • Be clear about features and benefits

3. Add app icon:

   • 512x512 PNG image
   • No text, just clean icon design

4. Select category and content rating:

   • Primary category
   • Content rating questionnaire

Configure App Signing

Google Play handles signing for distribution:

• Upload your signed AAB (Android App Bundle)
• Google Play signs the final APK for each device configuration
• This provides enhanced security compared to manual signing

Manage Releases

1. Go to "Release" section
2. Create new release in production track
3. Add your signed AAB (generated by EAS)
4. Write release notes for this version
5. Choose rollout percentage:
   • Start with 5-10% to test
   • Monitor crash reports
   • Gradually increase to 100% over a week

Submit for Review

Google Play has less stringent review than Apple:

• Usually approved within a few hours
• Automated checks run immediately
• Manual review for policy violations

Common Rejection Reasons

App Store Rejections

1. Crashes or Performance Issues: Test thoroughly on real devices
2. Misleading or Incomplete Metadata: Make sure screenshots and descriptions match app functionality
3. Missing App Privacy Policy: Even simple apps need a privacy policy
4. Non-functional Features: Don't include broken features
5. Violating Design Guidelines: Follow iOS Human Interface Guidelines
6. Unauthorized Use of API: Only use Apple-approved APIs
7. Duplicate Functionality: Don't submit variations of the same app

Google Play Rejections

1. Deceptive Behavior: App must do what it claims
2. Intellectual Property Violations: Respect copyrights and trademarks
3. Malware or Security Issues: Security issues result in immediate removal
4. Adult Content: Must be properly rated and restricted
5. Spammy Behavior: Excessive ads or misleading content
6. Broken Download Links: All external links must work

Preparing App Metadata

Screenshots

• Use real app screenshots, not marketing mockups
• Show your app's key features and benefits
• On App Store: 5-8 screenshots per language
• On Google Play: 2-8 screenshots per language
• High quality (no blurry or pixelated images)

App Title and Subtitle

• App Name: 30 characters (iOS), 50 characters (Android)
• Subtitle (iOS): 30 additional characters
• Make it clear what your app does
• Include keywords users search for

Keywords and Category

• Select most relevant category
• For iOS: 100 characters of comma-separated keywords
• For Android: Keywords are less important (description is searched)

Privacy Policy and Website

Both stores require:

• Accessible privacy policy (URL)
• Privacy policy that reflects actual data practices
• Website or support contact information
• Many use template privacy policies as starting point

Post-Launch: Updates and Maintenance

Regular Updates with Rork

After your app is live, updates follow the same process:

1. Make code changes in Rork
2. Increment version number in app.json
3. Build with EAS: eas build --platform ios && eas build --platform android
4. Submit to stores with release notes
5. Monitor crash reports and user reviews
6. Release to percentage of users first, then ramp up

Monitoring Performance

Metrics to track:

• Crash rates
• User ratings
• Download numbers
• Review sentiment
• Session duration
• Feature usage

Tools available:

• App Store Analytics (App Store Connect)
• Google Play Console Analytics
• Firebase Analytics (if integrated)
• Crash reporting (Firebase Crashlytics or Sentry)

Responding to Reviews

1. Monitor user reviews regularly
2. Respond to bugs reported in reviews
3. Thank positive reviewers and address concerns
4. Fix issues quickly to maintain ratings
5. Push updates addressing common complaints

Version Strategy

• Patch releases (1.0.1, 1.0.2): Bug fixes
• Minor releases (1.1.0, 1.2.0): New features
• Major releases (2.0.0): Significant changes

Update frequently enough to stay relevant but don't update excessively (multiple per day).

Wrapping up

Publishing to App Store and Google Play is straightforward with Rork. For most developers, Rork Original provides the best balance of control and simplicity for reaching both iOS and Android users. Focus on creating a quality app with good metadata, test thoroughly before submission, and be prepared for the review process. Once live, monitor user feedback and push regular updates to maintain user satisfaction and app store rankings.