Introduction

This document provides tips on what you can do with the Mobage ngCore SDK (hereafter ngCore).This includes methods of incentive provision and event operation etc.

Invitation Function of ngCore

Currently it is not possible to send an invitation mail to a Mobatomo(friend in Mobage) using other methods than openFriendPicker in ngCore. openFriendPicker is a function originally used to “select” a Mobatomo who has already started a game. However, sending an invitation mail to a Mobatomo who has not started a game is possible. Regarding information of user who has sent invitation mail, the UserId is sent to the Listener by setting up invitedUserEmitter when the WebView is closed.

Transition of Invitation Mail

By calling Social.Common.Service.openFriendPicker(),WebView (refer to the left screenshot below) will be displayed. The following screenshots are diagram showing the process for acquiring UserId by using the Listener set in invitedUserEmitter.

Implementation Example of invitedUserEmitter

For acquiring the invited UserId, you need to implement invitedUserEmitter before calling openFriendPicker. Implementation example is provided below.

Methods of Incentive Provision by Invitation

The two methods of incentive provision by invitation in Smartphone applications are provided as below. After the invitation has accepted, you should provide incentives to users through server because of no life cycle events etc. in Smartphone applications.

Providing Incentives to All Invited Users Using the ClientAPI Only

• Acquire the invited user information from the Listener and provide incentives to all of them.
  In this case, you can only provide relatively light incentive since incentives are provided when the invitation mail is sent.

Managing Invitation Information Using the Server and Providing Incentives

• Acquire the invited user information from the Listener and saves the information of sent and invited users on the server.
• Provide an incentive to the sent user if the server detects that the invited user has started a game.

In this case, it is not possible to know which invitation mail the invited user starts game through if multiple users send mails to the invited user. For example, User A and B have sent an invitation to user C almost simultaneously. If user C starts the application,

• Give an incentive to both user A and B.
• Give an incentive to the user who comes in first or in second
• Let the invited user enter the UserId.
  Or you can set original rules on your own.

Methods of Event Operation in Mobage ngCore SDK for iOS

You can not perform live update in Mobage ngCore SDK for iOS. In order to update the data, you need to make a request in iTunesConnect of Apple again.

However, for the event with no resource code modification, you can update resource by placing setting resources on an external server using the secondary manifest and fire appropriate events. Detailed explanations regarding secondary manifest operation and resource update methods are given below.

Secondary Manifest Operation

• The file “manifest.00.json” such as normal manifest.json should be stored in the Manifests folder located at the same level as manifest.json.
• You can download resources by implementing the following code and set the position of server resources in the first argument of the start method. (Core.Capabilities.getContentUrl() is normally setup when placing resources on the Mobage side.)

• Bake it using nodejs and ngPackager.
• Place webgame.00.ngmanifest in build folder created after "bake” and resource file written in manifest.00.json within the server (inside http://example.com).

Updating Resources

• Change manifest.00.json to updated resources.
• Rebake it after updates.
• Place/overwrite the resource written in the secondary manifest created inside the build folder after bake and webgame.00.ngmanifest within the server (inside http://example.com).

Resources can be updated in the above procedure. Note that resources may be deleted when moving resources written in manifest.00.json to manifest.json.

Posting in the Diary

Posting from the Mobage ngCore SDK to the diary can be performed by implementing the API below.

It is possible to specify a post by placing the title and body of the text in an argument with Social.JP.Service.openDiaryWriter. It is also possible to determine if an entry was made in the diary by using the callback argument “isWrote.” However, users can rewrite the title and body of the text.

By calling Social.JP.Service.openDiaryWriter, the following diary post screen (WebView) will be displayed.

JPLocalAPI can not be used outside of Japan.

A callback argument may be used instead since it does not support Smartphone browser life cycle events.

Sending a MiniMail

Sending a MiniMail from the Mobage ngCore SDK can be performed by implementing the API below.

It is possible to specify MiniMail by placing the recipient, title and body of the text in an argument with Social.JP.Service.openMinimailSender. It is also possible to determine if a MiniMail was sent by using the callback argument isSent. However, users can rewrite the title and body of the text.
By calling Social.JP.Service.openMinimailSender, the following MiniMail submission screen (WebView) is displayed.

JPLocalAPI can not be used outside of Japan.

A callback argument may be used instead since it does not support Smartphone browser life cycle events.

Methods of Evaluation Guidance

Providing guidance for posting reviews and evaluations from the Mobage ngCore SDK to the AppStore or Google Play (formerly called Android Market) can be performed by implementing the API below. (The following example is for Google Play.)

Revision History

• 08/07/2012
  • Change "Android Market" to "Google Play".
• 03/02/2012
  • Released a new translated document.
• 04/18/2012
  • Revised Methods of Evaluation Guidance. (Japanese version)
• 04/06/2012
  • Added Methods of Evaluation Guidance. (Japanese version)

Revision History

• 08/23/2012
  • Initial Release.