Spil Games Integration Guidelines. For Native Android and ios apps.

Transcription

1 Spil Games Integration Guidelines For Native Android and ios apps. We strive to make it as easy as possible working with Spil Games. To ensure we deliver high quality games to our end users we have to set some important guidelines. Please read this document carefully to understand these guidelines to ensure a smooth integration with Spil Games and enable a great experience to endusers. The following guidelines are our default guidelines for all contracts signed after the 1 st of August Please note that in certain cases your contract can have a different set of guidelines.

2 GOOGLE (ANDROID) GUIDELINES General requirements Game is provided to Spil Games without source minification or obfuscation The game needs to work on the following Android Devices: Samsung Galaxy S3, Samsung Galaxy S4, Samsung Galaxy S5, and Samsung Galaxy Tab 2 7.0, Samsung Galaxy Tab , Samsung Galaxy Tab , Samsung Galaxy Tab , Samsung Galaxy S II and the Nexus 7. We will assist in testing your game on all relevant devices and will provide you detailed bug reports where applicable. Please test on any devices you have access to, after validating it works properly in the simulator. The game needs to work on: OS versions Android: 3.2+ and 4.0+ File size of the final build should not exceed 50 MB. This will allow users to download over 3G. Exceptions allowed when agreed upon with your Spil Games account manager. Visual requirements All visual assets that are needed in order to publish your app will be created by Spil Games. In order to be able to create the best presentation of your game, you need to provide us with: Logo( s) Main character(s) Level design(s) Main screen design(s) All files preferable in layered Illustrator, PSD or at least vector (when possible).

3 Technical guidelines SDK integration prerequisites Before starting the integration of the required SDK frameworks, please make sure you received the following information from your Spil Games account manager (you should get this by default): Spil Games Google Analytics API key Spil Games Chartboost appid Spil Games Chartboost Signature Spil Games Android app certificate Google API Project ID (optional) You need to implement to following two SDK frameworks: Google Analytics SDK Chartboost SDK Implementing Google Analytics Please start the implementation by following the documentation: Implementing Chartboost We ask you to implement the following features of Chartboost: Interstitial ads More Apps feature Please find below the Chartboost implementation to integrate the framework: Google API Project ID If you have implemented push notifications or any other Google service inside your game, please use the Google project id given by one of the Spil Games account managers.

4 Testing your apps We recommend you test your game in various simulators to start with and during the development process test frequently on a real device. Especially performance is important to test on a real device. If you don t have a real device to test your game on, please contact your Spil Games account manager in advance to discuss assistance of a QA engineer to test various development builds. We understand you might not have all the devices we have listed in this requirements document. This is not a problem. Once you have tested the game in the simulator (and preferably on one real device) you can request a QA moment for your game. We will test your game on all listed devices. Good practices: To receive extensive crash reports you can integrate crashlytics. This is not required but can help you solve potential crash issues faster. For more information about crashlytics please look at: You can create custom events using the Google analytics SDK. These custom events can be send on certain checkpoints of your game. It will further clarify the results of the test, as you will know for sure which checkpoints we ve reached during our QA test. This is not required but will help you verify certain critical moments. Request a Spil QA Review Build your app in debug mode and send an to your license manager including the following information: Subject: QA request: <GameName> <Developer> The body should contain the following information: o The App name o The platform type (Android) o In case of updates send us a description of the changes o Login or cheatcodes if applicable o Include the Androidmanifest.XML file. o A Wetransfer or Dropbox link containing the debug build

5 App Signing & sending the final build The final step in getting your game ready for publishing, is to sign the app with the certificate given by one the Spil Games account managers. The required password will be provided as well. Final builds with a different version number than we ve received so far or without a final QA report (showing it s been approved) will be rejected. Send an to your license manager including the following information: Subject: Store Build: <GameName> <Developer> The body should contain the following information: o The App name o The platform type (Android) o Include the Androidmanifest.XML file. o Attach the approved QA report o A WeTransfer or Dropbox link containing the store build We look forward to getting your game published!

6 APPLE (ios) GUIDELINES General requirements Your game must meet the standard Apple guidelines: ml File size of the final build should not exceed 50 MB. This will enable users to download over 3G. Exceptions allowed when agreed upon with your Spil Games account manager. The source files of the Game should be provided to Spil Games without source minification or obfuscation The game needs to work on the following ios Devices: iphone 4 (all versions), iphone 5 (all versions), ipad Mini (1st generation), ipad Mini (2nd generation), ipad 2, ipad (3rd generation), ipad (4th generation), ipad Air, ipod touch 4G and ipod touch 5G We will assist in testing your game on all relevant devices and will provide you detailed bug reports where applicable. Please test on any devices you have access to, after validating it works properly in the simulator. The game needs to work on: OS Versions IOS: 6+ Visual requirements All visual assets that are needed in order to publish your app will be created by Spil Games. In order to be able to create the best presentation of your game, you need to provide us with: Logo( s) Main character(s) Level design(s) Main screen design(s) All files preferable in layered Illustrator, PSD or at least vector (when possible).

7 Technical guidelines SDK integration prerequisites Before starting the integration of the required SDK frameworks, please make sure you received the following information from your Spil Games account manager (you should get this by default): Spil Games Google Analytics API key Spil Games Chartboost appid Spil Games Chartboost Signature Spil Games AdHoc and distribution certificates *Push notification details (not required by default) You need to implement to following two SDK frameworks: Google Analytics SDK Chartboost SDK Implementing Google Analytics Please start the implementation with following the documentation below: Implementing Chartboost We ask you to implement the following features of Chartboost: Interstitial ads More Apps feature Please find below the Chartboost implementation to integrate the framework: More details about all methods can be found here: More details about the moreapps feature can be found on: Note: you don t have to configure things in the Chartboost dashboard.

8 Testing your apps We recommend you test your game in various simulators to start with and during the development process test frequently on a real device. Especially performance is important to test on a real device. If you don t have a real device to test your game on, please contact your Spil Games account manager in advance to discuss assistance of a QA engineer to test various development builds. We understand you might not have all the devices we have listed in this requirements document. This is not a problem. Once you have tested the game in the simulator (and preferably on one real device) you can request a QA moment for your game. We will test your game on all listed devices. Good practices: To receive extensive crash reports you can integrate crashlytics. This is not required but can help you solve potential crash issues faster. For more information about crashlytics please look at: You can create custom events using the Google analytics SDK. These custom events can be send on certain checkpoints of your game. It will further clarify the results of the test, as you will know for sure which checkpoints we ve reached during our QA test. This is not required but will help you verify certain critical moments. Signing your app for QA and request a Spil Review For complete documentation about how to sign your app you can refer to the following page: DistributionGuide/Introduction/Introduction.html Send an to your license manager including the following information: Subject: QA request: <GameName> <Developer> The body should contain the following information: o The App name o The platform type (ios) o The App version number o In case of updates send us a description of the changes o Login or cheatcodes if applicable o A Wetransfer or Dropbox link containing the adhoc build

9 Signing your app for production Please note you can only send a final production build of the version that is approved by QA. Final builds with a different version number or without a QA report will be rejected. Send an to your license manager including the following information: Subject: Store Build: <GameName> <Developer> The body should contain the following information: o The App name o The platform type (ios) o The App version number o Attach the approved QA report o A WeTransfer or Dropbox link containing the store build We look forward to getting your game published!