Skip to main content

Go-Live Checklist

Use this checklist to ensure your Gameball Flutter SDK v3.1.0 integration is complete and ready for production.
During development, use your account Test Key to authenticate requests. Once integration is completed and validated, swap to your Production API Key.

Step 1: Install SDK and Verify Dependencies

  • Gameball Flutter SDK v3.1.0 is added to pubspec.yaml
  • All dependencies are resolved with flutter pub get
  • SDK imports correctly in your Dart files
  • No compilation errors or warnings
  • iOS pods are installed successfully
  • Android build completes without errors
For information, please read more at Getting Started

Step 2: Initialize SDK

  • SDK initializes successfully with your API key in main()
  • Gameball.getInstance().init() runs without errors
  • Language and platform settings are configured correctly
For information, please read more at Initialize SDK

Step 3: Register and Display Customer Profile

  • Test customer registration with registerPlayer returns success
  • Customer data appears correctly in Gameball dashboard
  • Profile widget displays correctly on both iOS and Android
  • Widget navigation works properly
  • Error handling works for invalid registrations
For information, please read more at Initialize Customer Profile

Step 4: Track Events

  • Test events are sent successfully using sendEvent
  • Events appear in Gameball dashboard with correct metadata
  • Event-based rewards trigger properly
  • Error handling works for failed API calls
For information, please read more at Track Customer Events

Step 5: Production Readiness

  • Swap Test API Key to Production API Key
  • Test on multiple devices (iOS and Android)
  • Test on different screen sizes and orientations
  • Memory usage is within acceptable limits
  • No memory leaks in long-running sessions
  • Crash reporting is configured and working

Step 6: Platform-Specific Checks

iOS

  • iOS deployment target is 11.0 or higher
  • Pods are installed and up-to-date
  • App Store privacy requirements are met

Android

  • minSdkVersion is 21 or higher
  • targetSdkVersion is 34
  • ProGuard rules (if used) don’t conflict with Gameball SDK

Step 10: Monitoring and Support

  • Monitor API response times after launch
  • Check crash reports for any SDK-related issues
  • Verify customer transactions in Gameball dashboard
  • Support team is ready to handle inquiries
  • Documentation is accessible to team
Once you’ve completed all items in this checklist, your Flutter Gameball SDK v3.1.0 integration is ready for production!

Troubleshooting Resources