Investigation of some mobile games

Experience Sharing from qihai technology @ LIU Yu to gameres friends. Some precautions for mobile game production are not textbooks for reference!

1. uidesign

1.1 The layout should be as simple as possible, avoiding multiple frame menus as much as possible, which has a great impact on efficiency
1.2 button is big, at least one finger is big, clear color, concise and not fancy

2. Controls and operations

2.1 double-click. Do not use the drop-down list.
2.2 drag is not commonly used
2.3 hover text description is directly written to a visible place, or click to display it
2.4 Single-choice, multiple-choice box can have
2.5 The input method uses the built-in mobile phone

3. Music sound effects:Music is required. Generally, game sound effects are not required (users have not raised any requirements ).

4. Paid promotions:It is not much different from web games and client games.

5. user habits:

5.1 of mobile game users are looking for a game. They have expectations for the game, so the survival is higher than that of web games, and the gameplay is more important.
5.2 players can operate on multiple threads when playing web games. For example, they can view web pages when playing games. However, mobile phone users cannot perform multi-thread operations. The main method is to hook up and wait for Cd, which means players have nothing to do. Mobile phone users are usually bored when opening their mobile phones. Therefore, mobile games generally do not play CD or hook up.

6. Data Communication:2G and 3G networks are not as good as you think, so do your best to do automatic combat, client combat, or short-term combat gameplay.

7. Cheating:Players' research on plug-ins for mobile games is as powerful as that for client games.

8. Successful product examples:

8.1 battles: the sword of the king, time and space hunters
8.2 arpg class: Forget fairy (class journey)
8.3 card categories: My name is Mt.
8.4 horizontal layout: Legend of the legend of the dragon mobile version is an example of failure ).

9. gameplay Disposition:If it is not an arpg game, players prefer single-host or cross-time interaction, and have no obvious preference for group activities.

10. Recommended Development languages:

10.1 cocos2dx: the most widely used, a large number of games use this language.
10.2 Flash Air: Emerging flash language mechanisms, such as mengjianghu and Magic Card fantasies.
10.3 unity3d: It is said that it is difficult and deep.

11. operation data,The following data is an operation reference

11.1 Single Server user import volume: 6 kb-1 W
11.2 retention:
-Keep more than 40% billion items the next day to check whether there is a problem with the guide and selling phase.
-The deposit rate for the 15th day is 15%. Check whether the game content is faulty. Users after the 15th day are long-term users and are not easy to lose.
11.3 ARPU value:
-The Daily arpu150 + billing method is sharp. It depends on the user's ability to pay for the attack and whether the user accepts the payment.
-The monthly arpu500 + is sharp, depending on the Payment depth.
11.4 payment conversion rate of 4% +, more than 7% will certainly be able to fire.
11.5 download to registration conversion rate 40%-80%, Android 40%, ios80 %. If you give up on the download process, the download fails, the installation fails, and the operation fails, all of which are lost. The installation package is less than 50 MB.
11.6 players can accept 1 hour and 2 m traffic, but the smaller the game, the better. The legend of God is 300 k per hour and is hailed as sharp