The Differences between Account Binding Solution 1–2–3
Hello, in today’s article, we will try to examine 3 different solutions of the Account Binding method offered by HAG and the differences between these solutions. After you start reading this article, if you have questions in your mind, what is Account Binding? What does it offer? If such questions arise, I recommend you to review the article titled Huawei Ability Gallery — Account Binding w Card Ability
Huawei Authorizes Developer
The content specially prepared for a certain user group can be shown to the relevant users by using this method by the developer. By applying this method, the Developer shows the content he has prepared to a certain user group.
Solution-1 and Solution-2 are available under Huawei Authorizes Developer heading. So what is the difference between Solution 1 and 2?
Solution-1 : It is a system where user credentials are entered into the developer’s own account system and the application is registered and the UID is assigned according to the developer’s own algorithm. In short, the user has to log in to the account system developed by the developer himself.
Solution-2 : It is the system where the developer does not have his own account system and the application is entered using the Login option with Huawei ID. As a result of matching the UID assigned by Huawei and the Open ID assigned by HAG, the Account Binding process is completed.
Solution 1 and Solution 2 offer the same features for Card and Content Ability.
Developer Authorizes Huawei
It is a method that can only be used for Content Ability. Developer must have its own server and account system, and the user logs into this account system.
Solution-3 : This feature only applies to Content Ability designs. It is a method where the user can see the previously purchased content, that is, the developer does not produce content specifically for the user.
At the end of this article, where we examine the difference between Account Binding solutions, I would like to present an example for each solution below for better understanding.
Solution-1: The developer has his own account system and wants to offer special content to a certain user group.
Solution-2: The developer does not have an account system designed by himself. In this case, by using the Login method with Huawei ID, the user can log in and complete the binding process by matching the Huawei User ID and Open ID.
Solution-3: If the developer has his own account system and wants to present the content of the products (such as music albums) that he has purchased before on Content Ability, he should prefer this method.