Mobile Game update process

Lead: updating a game is not complicated, but the update process is complicated because there are too many mobile game channels. The "73-member team" helped you sort out the mobile game update process and some notes. In the future, we will help you sort out updates from different channels.

<Ignore_js_op>

 

Token update

2 weeks in advance

[Operation, test] test the new version
[Planning] provides updated content
[Operation] re-process and update the content to form external documents
[Operation] evaluates risks of new versions (technical level, player experience level) and provides early warning solutions (rewards and accident handling methods)
[R & D] after the test is passed, start to package the versions of various channels
[Operation] Release of the new version to welcome the launch of the new version
[Art] Prepare an advertisement Diagram

1 week in advance

[Operation] notifies various channels of updating content and time
[Operation] notify other departments by email to update the time and content (Project Team, marketing department, commerce department, and customer service department)
[Operation] reviews packages from various channels (and follows up on the progress to ensure approval)
[Operation] released an update announcement at the player level

1 day before update

Operation: Tests updated activities.
[Operation] Prepare the updated announcement (login, in-game)
[Operation] reminds all channels of the time when the client will be available tomorrow (Update start time)

Updated on

[O & M] Stop server updates
[Operation] notifies all channels to update the client (synchronous)
[Operation] logon announcement modification to inform gamers of updates
[Operation] launch activity configuration and publish announcement Configuration
[Operation] The updated whitelist is used for game testing (game functions, activities, announcements, consumption, and recharge)
[O & M] Open servers
[Operation] observes various real-time data and player feedback
[Operation and O & M] if the client is not updated in a timely manner in some channels, the self-owned CDN update is enabled.

Considerations

Evaluate new version risks

This step should not be missed, because sometimes the updated content of the new version may cause some losses to players, or some players may be dissatisfied.

We need to consider these risks before they are updated, and then reduce these risks through other means such as compensation.

If you do not pay attention to these issues in advance, the update may be very passive and there is not enough time for the solution.

Review process

Each channel requires a self-testing document. before submitting the document, you must first perform all the test items in the self-testing document. Submit after all passes!

If the client is not rejected, most channels can pass the review within three days. However, we need to consider the situation of being rejected. Therefore, the security cycle is 7 working days. (After confirming the update time, submit the version 7 working days in advance .) PS: Saturday is not a workday.

When submitting an application for review, you must instruct the channel not to shelve the client in advance. The update time will be retained. Some channels may be updated due to human errors, and new versions of the client are available in advance. Therefore, after channel review, you must always check whether there are any channels available in advance. If there is an available channel, contact the channel to immediately withdraw the old version.

Client Server synchronously update

Update when the service is stopped, immediately contact each channel to mount the new version of the client. Do not wait until the update is complete before mounting. It takes some time for the client to synchronize the updates.

Because the android channel is generally a Hybrid server, the client must be synchronized. Connect all channels to the client.

Sometimes some channels may not be able to mount the new version of the client after the update is completed. In this case, some record filing is required to provide the new version.

Tip

Sdks in many channels do not have a forced update mechanism. Therefore, CP must have its own update mechanism, either by itself or by using third-party updates (umeng provides an update mechanism)

Mobile Game update process