Skip to main content
Use this checklist to ensure your Gameball Android SDK v3.1.1 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 SDK v3.1.1 is installed via Gradle/Maven
  • All dependencies are resolved without conflicts
  • SDK imports correctly in your activities
  • No compilation errors or warnings
  • GameballApp.getInstance(...).init(...) succeeds
For information, please read more at Getting Started

​
Step 2: Initialize and Register Customers

  • SDK initializes successfully with your API key in Application class
  • Test customer registration with initializeCustomer returns success
  • Customer data appears correctly in Gameball dashboard
  • Error handling works for invalid registrations
For information, please read more at Initialize Customer Profile

​
Step 3: 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 4: Push Notifications

  • Firebase or Huawei SDK is integrated
  • Device tokens are generated and registered successfully
  • Push notifications credentials configured in Gameball dashboard
  • Test notifications are received on devices
  • Notification content displays correctly
  • Token refresh handling works properly
For more information, please read more at Push Notifications

​
Step 5: Production Readiness

  • Swap Test API Key to Production API Key
  • ProGuard/R8 rules added to proguard-rules.pro: 
    -keep class com.gameball.gameball.** { *; }
-keep class com.gameball.gameball.model.** { *; }
-keepattributes Signature
-keepattributes *Annotation*
-keep class com.google.gson.** { *; }
  • App works correctly with code obfuscation enabled
  • Test on multiple Android devices and versions (API 21+)
  • Memory usage is within acceptable limits
  • No memory leaks in long-running sessions
  • Crash reporting is configured and working

​
Step 9: 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 Android Gameball SDK v3.1.1 integration is ready for production!

​
Troubleshooting Resources