Mobile mm call fee payment access process (ane), mmane
The following records the process of mobile mm call fee payment and access
1. What are the differences between strong network connections and weak Network Connections? Are sdks differentiated? What are the differences in user experience?
The difference is that the strong network is a network channel (wifi/gprs/3g), the weak network is a short message channel, the user level difference is that the strong network requires mobile network payment, payment can be made anytime, anywhere on the weak network.
VPC and VPC use different sdks. You do not need to apply for an EIP. You must apply for an EIP to access VPC and have an access door frame.
2. Access key processes
1) register a developer account
2) Fill in all types of developer information and sign the contract electronically (requires review without affecting sdk access) (this step is completed to receive the money, haha)
3) create an iap payment test point (purchased item content) for testing (this step needs to be reviewed and generally the application will be passed the next day)
This step can be connected to the sdk. After self-testing is passed (all items must be tested and recorded in the background), the sdk can be submitted for release.
3. Problems with iap billing points and application creation, weak networking permission Application
There are two modes: What is the difference between "in-app billing (iap)" and "application capability"? I am confused now (I will add it later)
Iap access can be used independently in the mobile mm market, as long as the iap billing point passes the test and the application passes.
You need to create an app in the background to upload a test package when mobile mm is launched.
4. How can I remove the mobile welcome page?
Unknown (supplemented later)
5. sdk access problems
1) initialize the black screen: No. Package the resource image assets/mmiap into the apk.
2) The Initialization is successful, and the payment is not responded: the CopyrightDeclaration. xml mmiap. xml VERSION file is not put into the apk root directory. The main reason is not to omit various resource files.
3) You must use a mobile phone for debugging. You can see the difference on the welcome page.
4) the backend address does not support domain name access. Only ip addresses are allowed.
5) Other considerations: you cannot purchase an instance when Initialization is not completed, or if the time for a single purchase is less than 15 seconds.
6. Comments and comments:
1. The efficiency of the mobile developer platform is the highest among the three major operators, especially when review and debugging do not affect each other. This is user-friendly.
2. If the mobile developer platform does not provide customer service consultation, you can only view materials, ask people, and find your own answers.
3. the user name cannot be saved when logging on to the mobile developer Platform website. The password cannot be copied. If cookies are invalid, you must log on twice before you can log on again .. Amazing.
For mobile mm Access Points
In the February 1mm upgrade, the mm access point can be used but is not stream-free. It is the same as the cmwap access point.
Problems with mobile MM Access Points
An access point is automatically added when MM is installed: the access point is automatically called when cmcc cmmm is used.
Fees are charged for viewing CCTV, and traffic is free for 6 RMB per month.
