{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is Huawei Ability Gallery (HAG)?
Huawei Ability Gallery is a core capability of the HMS Core ecosystem. HAG creates more convenient experience for users and enables more efficient service distribution for developers, achieving a win-win-win situation for users, developers, and Huawei.
What are HAG Abilities?
Abilities link user intent with various service offerings. Developers define abilities in Huawei Ability Gallery, and users can use these abilities on Huawei devices or through other traffic entries.
HAG provides developers three abilities type
App Abilities: App abilities are presented by icon, and developers must provide deep links to the associated apps.
Card Ability: Developers use quick app development technology to develop ability cards (including data processing and display logic), and abilities are displayed as cards. Information can be displayed in card mode.
Content Ability: Huawei Ability Gallery obtains data from developers’ servers through APIs and provides content abilities for Huawei products. Huawei products then present the abilities as defined. Content abilities can be presented by card or voice.
What is App Ability?
App Abilities which are presented by icon are used to redirect user to application. We can use app Ability with APK and RPK. All app abilities are shown at Instant Access panel on Huawei Assistant page.
Global Search: We can search something at there.
Instant Access: Users click the icon or banner and redirect to APP/Quick App.
Smart care: there are smart cards recommended by the system to serve the users.Cards and contents abilities are displayed at here.
Developers can be created app abilities as static or dynamic ;
Static app ability is an icon and it redirects user to related app.
Note : App abilities aren’t displayed without app installed If related app is Native application(APK).If App ability was created to Quick app (RPK) , users don’t need to install app first.
Dynamic app ability can be used to send parameter to application via HiVoice. For example , When the users want to open an application using specific parameter like Hotel name,book name,music name, etc. Dynamic App abilities can be used .They just need to define parameters inside redirect parameters .You can define many parameters inside there.
Also We can launch app using app keyword is used for triggering an app by voice.If your app ability supports multi languages , You can many keywords for all of them. A maximum of 10 keywords can be configured for each language.
Note: HiVoice uses Celia.currently Celia is available in P40 and following languages and regions：
Languages: English (UK), French (France), Spanish (Spain)
Countries / Regions: United Kingdom, France, Spain, Chile, Mexico, Colombia
Detail: You can follow link to get more information for Celia : Link
How can we create an app Ability?
Note : If you want to create ability , you need to have Entertainment Account .You can create app ability inside 1 or 2 days.
While we create an app ability , We must follow specific way.
Firstly, app ability’s icon design should be done. Icon design has many restriction like size , color , icon border type ,etc.
to get more information you can follow this link (Icon Design Rules).
We need to create deeplink to redirect users.Redirection URL in a deep link, please follow the filling rules.
Under this line you can see correct formats for Both APK and RPK solution:
huawei://
com.huawei://
com.huawei://hag
com.huawei://hag/app/ability
com.huawei://hag/ability?type=app&test=1
Note: RPK and APK have different deeplink integrations.
If you want to create deeplink for APK ,you can define them inside activity or Navigation XML files.I want to give an example for it :
On the other hand You want to create deeplinks to Quick app , You should define them inside manifest file of Quick App.We must add path parameter under router tag .Quick apps use it to redirect.
After add path parameter under Router , You can define deeplink like :
hap://app/quickAppPackagename/hello
How can we test deeplinks?
You can test deep-links with adb .If there is no problem , Your Application automatically is opened . You can use CMD to work ADB commands .Also following code helps you for testing deep-link
adb shell am start -a android.intent.action.VIEW -d deepLink
Examples Of Adb Commands :
adb shell am start -a android.intent.action.VIEW -d pettracker://pet-tracker.fi/home
Note: pettracker://pet-tracker.fi/home is our deeplink , It redirects user to specific fragment.
If you want to send parameter with it , you can use following deeplink
adb shell am start -a android.intent.action.VIEW -d pettracker://pet-tracker.fi/track/Fluffy
After These operations finished , We can start integration to related app.If you want to create HAG ability , you must have Entertainment account.otherwise you never see Huawei Ability Gallery panel on console.
While We begin to create app ability , we have to select countries/regions for release the ability.There are three region Europe,Russia and AALA(Asia-Africa-Latin America).
Note: If your ability needs to serve two countries or regions covered by different sites, create it on both sites. For example, if you want to server both Morocco and France, create an ability on Huawei Ability Gallery (AALA) and Huawei Ability Gallery (Europe).
After selecting a site, you will be prompted to sign the Huawei Ability Gallery Service Agreement. Click App ability, set required parameters, and click Create.(Ability Name has to contain app name .For example your App name Pet Tracker , your app Ability name can be Pet Tracker Ability)
Select countries/regions for release.You can also create an ability for each operations region independently.
We must configure an interaction model.Interaction model page includes ability name ,ability category and ability trigger mode.Under this page you determine trigger mode . For example keyword trigger mode. User can search your app in HiSearch on Huawei assistant page .If your user’s intent matches declared keyword your app ability displayed on screen.
We can configure a deep link that redirects a user from an ability icon to an app on Lint settings page. The deep link can be created for APK or RPK .
Finally Click Ability information page. Fill in basic information and ability display information, and click Save. If Ability information supports multi-language presentation, you can click Manage Languages to select and manage languages, and configure the relevant Ability information.
How can we test created App ability?
Huawei provides us test platform for App abilities.Before releasing an app ability, test its functions and content and make sure that all of them pass the test.
Sign in to Huawei Ability Gallery, go to Test > Release for test, and click Release for test.
We need QR code to test app abilities for this reason click Simulation test to obtain a test QR code. The test QR code is displayed on the right.
After Creating QR code , we can scan it with Our Device.We can do this operation using Huawei Ability test tool. Start Huawei Ability test tool select App Ability, and tap Scan QR Code, and scan the QR code then click search.
After the scanning is successful, set Intent category and Keyword, tap SEARCH, and test the functions and content.
Related Links
HAG Web Page : Link
App Ability Web Page : Link
App Ability Configuration Page : Link
App Ability Design Page : https://developer.huawei.com/consumer/en/doc/development/service/5060600
Thanks to Serkan Mutlu for this article.
Original post: https://medium.com/huawei-developers/huawei-ability-gallery-app-ability-5827c30d1360
Related
Huawei App Messaging Service Part1
Hello everyone, I will explain what is app messaging service, what are the advantages, what are the differences from push kit and how can we use the service in our own applications. App messaging is a service that provides messages and notifications to target active users of the application. Using the console, we can send a message to the application in the format desired, when the users use the application.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In which scenarios can we use the App Messaging?
App messaging is used in almost all kinds of applications, from games, banking applications, food service applications to shopping brands.
Online Shopping Mobile Applications
One of the most well-known of these is discount or opportunity campaign information on online shopping websites’ mobile applications. These shopping sites detect the requests of the users according to the behavior analysis of the users or the events such as button clicks that will trigger the app messaging. According to these analyzes, they present messages about their campaigns to the user.
Mobile Games
Another well-known scenario is in-app information, instructional explanations and sales campaigns in mobile games.
The Themes Applications
One of the scenario examples is its use in applications that provide visual services on the phone. In these applications, new product information in the application is made using the app messaging image feature.
Encourage users
Another scenario is that app messaging can be used to encourage users to watch video, to share app-related features, campaigns, game scores on their social media and to keep up with payment transformation.
Also, with the help of app messaging, We can encourage users to engage with our applications.
Use For Advertising
If we have an advertising agreement with other brands, we can deliver the ads of these brands to users with app messaging in the template we want.
*According to the usage of the applications of the users, their preferences can be analyzed and certain messages can be presented to the user
*The preferences made by the users while using the applications can be analyzed and the messages determined using these analyzes can be presented to the user.
*According to our scenarios, messages can be presented in the form of cards, pictures.
*Data about users can be collected.
Differences Between App Messaging and Push Kit
*App messaging message is arranged by the client and triggered by an event. Push kit message is transmitted by server.
*App messaging message is displayed when the user is using our application. However, It is enough to install the application on our phone to receive the push kit message.
*There are many templates in app messaging and we can customize them. The message style is simple. The notification bar only has a predefined simple style template.
*App messaging message contents are determined according to user behavior. But, the app kit message has weak correlation with user behavior.
*App messaging has attractive and enhancing features for active users. However, app kit message is used to deliver simple notifications and reminders to users about the app.
Getting Started
Development Environment and Skill Requirements
*A computer with Android Studio installed for app development
*Skills in Java and Android Studio
*A developer account registered by referring to Registration and Verification
Device Requirements
*A device running Android 4.2 or a later version
Preparations Before Development
Before we start to apps development , we should apply some steps to our own project. the following preparations:
*Create an app in AppGallery Connect.
*Create an Android Studio project.
*Add the app package name.
*Configure the Maven repository address and AppGallery Connect gradle plug-in.
*Synchronize the project.
we can follow the link below for the steps above.
("https://developer.huawei.com/consumer/en/codelab/AGCPreparation/index.html#0"]https://developer.huawei.com/consumer/en/codelab/AGCPreparation/index.html#0[/URL]
the App Messaging SDK Integration
We need to download and add SDK into our application for App messaging.
1. Firstly, we need to sign in to AppGallery Connect and select My projects.
2. Secondly, we need to select the app then we need to enable App Messaging using the app list in our project.
3. After that, we need to click agconnect-services.json to download the configuration file from the project setting page and copy the agconnect-services.json file and paste it to the app root directory.
4. Fourthly, we need to open the app-level build.gradle file and add the following code for HUAWEI Analytics Kit and the App Messaging SDK integration. Then synchronize the configuration.
("https://gist.githubusercontent.com/hakki2391/4b875a293272b35680d64f2ad2251d08/raw/f716762bfb1a946be60d7d30c862a17fc886c7d2/Dependencies")
Enabling App Messaging
*Firstly, we will sign in to AppGallery Connect and select My projects.
*Secondly, we will find our project from the project list and click the app for which we want to enable App Messaging on the project card.
*Finally, we will go to Growing then we will find App Messaging and click Enable now.
How can we create a Message
*Firstly, sign in to AppGallery Connect and select My projects.
*Select the app for which we need to enable App Messaging from the app list in our project.
*Go to Growing then find App Messaging.
*Click New.
*Set the style and content. We can set Type to image, banner, and pop-up like below
*We will use pop-up.
*Now, set other parameters as required. Click Next.
*On this point, set the sending target condition and the package name of the current app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi everyone, I will explain Card Ability in this article. Article also includes general information for Huawei Ability Gallery. You can find and download a sample Card ability project at the end of Article.(If you want to test it, read requirements section before test).
What is Huawei Ability Gallery ?HUAWEI Ability Gallery is Huawei’s unified platform for ability integration and distribution. It aggregates traffic from a wide range of devices in all scenarios and provides developers with a one-time integration and all-scenario distribution solution.
Note I : If you want to develop an Huawei ability, you need to have an Enterprise account otherwise Smart Service section on AGC cannot be seen. To learn How to register Enterprise account, visit link: Link
Note II : Developers in Team list cannot create ability even if They have enterprise account.
Note III :All Abilities can be seen in Huawei Assistant page. You can open or close page following steps : Settings -> Home Screen & Wallpaper ->Home screen settings -> Huawei Assistant today.
Devices for Ability DistributionServices integrated with HUAWEI Ability Gallery can be distributed to 1+8+N devices in almost all scenarios and provide users with natural interactive services.
“1” : Smartphone.
“8” : tablet, smart TV, speakers, AR/VR, watch, head unit, earphones, and PC.
“N”: devices used in scenarios such as mobile office, smart home, sports and health, entertainment, and smart travel.
For example, the weather service integrated with HUAWEI Ability Gallery can be distributed to devices such as smartphones, tablets, smart TVs, head units, and watches through AI Voice.
Huawei Ability Integration ModesHuawei Ability Gallery include 3 types of ability :
App Ability: Instant Access can access HUAWEI Ability Gallery via app abilities, which are presented by icon. Links for redirecting to an APK, RPK, or HTML5 page are provided by Developer.
Content Ability: HUAWEI Ability Gallery obtains data from developers’ servers through APIs and provides content abilities for Huawei products. Huawei products then present the abilities as defined.
Card Ability : Developers use quick app development technology to develop ability cards (including data processing and display logic), and abilities are displayed as cards.
Card AbilityCard ability presented by card has the following features:
The name and content of the ability are presented to users.
A user who taps the card will be redirected to the native app, quick app or HTML5 page.
More content is displayed to attract users, contributing to higher conversion rate.
Each users must subscribe Card ability to display Card ability in Huawei Assistant Page. Cards can be use without any app. Users just need to subscribe it to use.
Note : Each card has an widget id attribute which cannot be edited or deleted. Otherwise, the widget dragging and simulated preview functions will be unavailable.
Interaction Types of Card AbilityHAG includes three intents type. These are user ,event and resident events. Developers must configure at least one of them .
User Intents : A user intent is represented by one or more intents in the interaction model. Card ability can be triggered by Keywords , Voice and Images.
Event Triggers : An ability is triggered when event conditions (such as time and location) that you have set are met. When an event occurs, HUAWEI Ability Gallery pushes the ability card to users to display event-related information. To add an event, select an event category (Custom event or Preset event), set the event type, name, description, specify whether to push an event to a specified user, set the duration when the event card will stay visible on the screen, and finally set the display mode.
Resident Event Card : If you need a permanent intent card, just create it, with no need to push events. The card will be always available in HUAWEI Assistant.
For Detail Information About Interaction models of Card Ability , visit this page Link
Card Ability DesignHUAWEI Ability Gallery contains common template components and basic parameters, which must be used together with the UX specifications.
Developers use Huawei Quick App ide to design Card ability templates.
Note I : Unless You want to use predefined template, you can select empty template and then design it easily. You just need to look at this document to learn How to use ide.
There are many restriction to design card ability so Before start to design, Huawei Card design page must be checked. Link
Note II : Before you start card development, contact [email protected] for assistance and fill in the Service information registration table to ensure that your card complies with Huawei specifications.
Requirements to develop Card AbilityBefore Developers start integration of HAG , They need to load some tools to design and test.
Huawei Quick App ide Packages
Huawei Quick App ide which is strong development tool is used to develop card ability. You can download here :
Note : Before load Huawei Quick App ide , You must install Node.js. Link
Huawei Quick App ide for Win64 : Link
Huawei Quick App ide for Mac : Link .
Installation Guide for Mac link
Huawei Quick App Loader
It is used to start and debug quick app and HAG development. Link
Card Ability DevelopmentCard ability can be developed with Huawei Quick App ide. Developers use JavaScript, HTML and CSS to develop card ability. Quick app ide has many different template. If Developers want to use one of them , They can use and integrate their features. For instance they can get data from server and show these on Card ability to users like we did.
Note : Card development takes 12 days.
First step design or select card ability template. In our example I choose a template. To select a card template ,you can follow File > New Project > New Widget Project.
After create a card , developers can modify card ability appearance . In Our example, we change number of element list , images and content of card ability. In addition If users click “More Currencies button” , They will be redirected to related page of app. If you want to learn detail of design , visit following link
We need to create objects and variables to store data which comes from API .In our Card has on
JavaScript:
data: {
currencies:[
//Our models consist of 3 properties.name,currency rate and image.
//Images is stored base64 format in objects.
{"name":"GBP","rate":"0.00","imgUrl":"data:image/png;base64,..."},
{"name":"EUR","rate":"0.00","imgUrl":"data:image/png;base64,..."}
],
//It show that when Data was obtained
UpdatedTime:null,
//Our card title
currencyCardTitle:"Currencies",
//Our Button name
currencyCardButton:"More Currencies",
/*
these items will be displayed on card ability, Our design includes only two items.
If you want to add more items, you need to insert into here
*/
'dividings': ['newsandinformationtype_dividing', 'newsandinformationtype_dividing']
}
We need to send request to obtain data from service , We can use Fetch for this operation. Under line you can see how to use fetch .You can download all project to look at code scope from My GitHub repo which can be found at the end of page.
JavaScript:
import fetch from '@system.fetch'
...
module.exports = {
data:{ ... },
getDataFromAPI:function(e){
var that = this
fetch.fetch({
url: 'API url',
success: function (data) {
},
fail: function (data, code) {
}
})
}
}
Card ability includes a button which is called More Currencies. When users click it, they will be redirected to Currency Page which is in App. If developers want to create this feature, they need to use Router API and create a deep link.
JavaScript:
import router from "@system.router"
...
const currencyPageUri ="referenceapp://bank/currencies"//DeepLink of Currency Page
redirectToApp:function(){
//deeplink must be called to jump app page
router.push({uri:currencyPageUri});
}
Card Ability Configuration StepsWhen Developers finish card development, they need to start an card ability in Smart service page. I said before If you want to create an ability, you need to have an Enterprise account.
This part includes only important section for Ability configuration.
When Start to configure ability , need to select a Site like Europe, Russia and Asia-Africa-Latin America(AALA).If you want to publish you ability all regions , You need to create same ability 3 times for different regions.
All ability includes a fulfillment which describes important settings. Fulfilment includes App URLs which users click to open app, qucikApp or H5 page.
Go to service button is important for card and content abilities. After Users click this, They will be redirected to service which may be app, quickApp or HTML 5 page.
Card Ability TestAfter Finish Card development and configuration , Cards can be tested using Huawei Ability Test tool which can be downloaded from Huawei App Gallery or real device .
Developers just need to generate a QR code and then scan it with Huawei ability test tool.
If Real device test tool is wanted to use, user test list should be created on HAG configuration.
ReferencesCard Ability : Link
Configuration Guide : Link
Test Guide : Link
Repo includes card ability example.
GitHub - SerkanMUTLU/Card-Ability-Example at dev
Contribute to SerkanMUTLU/Card-Ability-Example development by creating an account on GitHub.
github.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is Huawei Ability Gallery (HAG)?Huawei Ability Gallery is a core capability of the HMS Core ecosystem. HAG creates more convenient experience for users and enables more efficient service distribution for developers, achieving a win-win-win situation for users, developers, and Huawei.
What are HAG Abilities?Abilities link user intent with various service offerings. Developers define abilities in Huawei Ability Gallery, and users can use these abilities on Huawei devices or through other traffic entries.
HAG provides developers three abilities type
App Abilities: App abilities are presented by icon, and developers must provide deep links to the associated apps.
Card Ability: Developers use quick app development technology to develop ability cards (including data processing and display logic), and abilities are displayed as cards. Information can be displayed in card mode.
Content Ability: Huawei Ability Gallery obtains data from developers’ servers through APIs and provides content abilities for Huawei products. Huawei products then present the abilities as defined. Content abilities can be presented by card or voice.
What is App Ability?
App Abilities which are represented by an icon are used to redirect user to application. We can use app Ability with APK and RPK. All app abilities are shown at Instant Access panel inside Huawei Assistant page.
Note : You have to enable Huawei Assistant today to use Assistant Page
We need to open Huawei assistant page to use it. You should follow this way to change state of it : Settings -> Home Screen & Wallpaper ->Home screen settings -> Huawei Assistant today . Huawei Assistant today must be enabled to use related page. After this you can reach related page
First of all you should open first page of Device and then you should try to change screen left to right. If Page opens , Your settings is correct .Unless Page open , You need to check Huawei Assistant Today setting.
Global Search : We can use it to search something .
Instant Access : Users click the icon or banner and redirect to APP/Quick App.
Smart care : there are smart cards recommended by the system to serve the users. Cards and contents abilities are displayed at here.
App abilities can be created as Dynamic or Static ;
Static app abilities are represented by an icon and it redirects user to related app.
Note : If related app is Native application(APK) , App must be installed to use app abilities . If App ability is created for Quick app (RPK) , users don’t need to install app firstly.
Dynamic app ability can be used to send parameter to application via HiVoice. For example , When the users want to open an application using specific parameter like Hotel name, book name, music name, etc. Dynamic App abilities can be used .They just need to define parameters inside redirect parameters .You can define many parameters inside there.
Also We can trigger our app using app keyword with HiVoice . If your app ability supports multi languages , You can define many keywords for different language.
Note : Maximum of 10 keywords can be configured for each language.
Note : HiVoice uses Celia. currently Celia is available in P40 and following languages and regions：
Languages: English (UK), French (France), Spanish (Spain)
Countries / Regions: United Kingdom, France, Spain, Chile, Mexico, Colombia
Detail : You can follow link to get more information for Celia : Link
How can we create an app Ability?Note : If you want to create ability , you need to have Entertainment Account .You can create app ability inside 1 or 2 days.
While we create an app ability , We must follow specific way.
Firstly, app ability’s icon should be designed. Design operation has many restriction like size , color , icon border type ,etc.
If you need to get more information , you will follow this link (Icon Design Rules).
We need to create deeplink to redirect users. Redirection URL in a deep link,
Under this line you can see correct formats for Both APK and RPK solution:
huawei://
com.huawei://
com.huawei://hag
com.huawei://hag/app/ability
com.huawei://hag/ability?type=app&test=1
Note : RPK and APK have different deeplink integrations.
If you want to create deeplink for APK ,you can define them inside activity or Navigation XML files.I want to give an example for it :
On the other hand You want to create deeplinks to Quick app , You can use quick app package path.
After add path parameter under Router , You can define deeplink like : hwfastapp://appPackageName
How can we test deeplinks ?We can test deep-links with adb . If There is no problem on deeplink, Your Application is opened . You can use CMD to work with ADB commands .Also following code helps you for testing deep-link
adb shell am start -a android.intent.action.VIEW -d deepLink
Examples Of Adb Commands :
adb shell am start -a android.intent.action.VIEW -d pettracker://pet-tracker.fi/home
Note : pettracker://pet-tracker.fi/home is our deeplink , It redirects user to related screen.
If you want to send parameter with app ability, you can use following deeplink
adb shell am start -a android.intent.action.VIEW -d pettracker://pet-tracker.fi/track?param=Buddy
After These operations are finished , We can start integration for related app.
While We begin to create app ability , we have to select countries/regions for release the ability. There are three region Europe, Russia and AALA(Asia-Africa-Latin America).
Note : If your ability needs to serve two countries or regions covered by different sites, create it on both sites. For example, if you want to server both Morocco and France, create an ability on Huawei Ability Gallery (AALA) and Huawei Ability Gallery (Europe).
After selecting a site, you will be prompted to sign the Huawei Ability Gallery Service Agreement. Click App ability, set required parameters, and click Create.(Ability Name has to contain app name .For example your App name Pet Tracker , your app Ability name can be Pet Tracker Ability)
Select countries/regions for release. You can also create an ability for each operations region independently.
We must configure an interaction model. Interaction model page includes ability name ,ability category and ability trigger mode. Under this page you determine trigger mode . For example keyword trigger mode. User can search your app in HiSearch on Huawei assistant page .If your user’s intent matches declared keyword your app ability displayed on screen.
We can configure a deep link that redirects a user from an ability icon to an app on Lint settings page. The deep link can be created for APK or RPK .
Finally Click Ability information page. Fill in basic information and ability display information, and click Save. If Ability information supports multi-language presentation, you can click Manage Languages to select and manage languages, and configure the relevant Ability information.
How can we test created App ability ?Huawei provides us test platform for App abilities.Before releasing an app ability, test its functions and content and make sure that all of them pass the test.
Sign in to Huawei Ability Gallery, go to Test > Release for test, and click Release for test.
We need QR code to test app abilities for this reason click Simulation test to obtain a test QR code. The test QR code is displayed on the right.
After Creating QR code , we can scan it with Our Device.We can do this operation using Huawei Ability test tool. Start Huawei Ability test tool select App Ability, and tap Scan QR Code, and scan the QR code then click search.
After the scanning is successful, set Intent category and Keyword, tap SEARCH, and test the functions and content.
Related LinksHAG Web Page : Link
App Ability Web Page : Link
App Ability Configuration Page : Link
App Ability Design Page : Link
Have you ever encountered the following problems when serving ads:
You allocate a large ad budget but you don't know how well your ads are performing and whether you're getting the most out of your ad spend.
You don't know what valuable actions users take when they view your ads.
You don't know whether ad serving policies such as the ad serving channel and ad type need to be adjusted.
To resolve the aforementioned problems, you'll need to track your ad conversion.
What is ad conversion tracking?
Conversion tracking is a critical part of serving ads. It is a process of reporting important conversion information (such as OAID, timestamp, conversion action, and action parameters) that advertisers care about to the ads analytics platform in order to generate reports. These reports help you quantify the performance of your ads and track the quantity and quality of users acquired by different platforms and ad types, and their corresponding conversion effects, thus helping you find ways to improve how you serve ads.
For example, when using HUAWEI Ads to serve ads, you can use HUAWEI Dynamic Tag Manager (DTM) to set conversion tracking to track ad conversion channels and analyze conversion effects with ease.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DTM is a tag manager system (TMS) that allows you to dynamically update tracking tags on a web-based UI to track specific events and report data to analytics platforms and ad attribution platforms. Visual event tracking in DTM is now the tool of choice for HUAWEI Ads web advertisers to track conversions on web pages.
Once you have integrated the DTM JavaScript code snippet or SDK into your app, simply configure a tracking code snippet for your web pages to collect conversion information. DTM has the following advantages when used for conversion tracking:
Fast setup: Getting DTM up and running is quick and easy: simply configure rules and add visual events to be tracked on the DTM web portal to quickly obtain data. This greatly shortens the configuration time compared with the traditional method of configuring tracking code for web pages.
High flexibility: If you need to adjust the ad serving policy or data to be collected after serving ads, all you need to do is to add related conditions on the tag management page on the DTM portal, which is more flexible and convenient because you don't need to repeat complex tracking code configuration or release an app update.
Multi-platform tracking: DTM supports conversion tracking for apps across different platforms, such as the Android and web platforms.
To configure HUAWEI Ads conversion tracking using DTM, perform the following operations. (Conversion tracking for web pages is used as an example.)
Obtain the tracking code snippet on the DTM portal and embed the code snippet into the pages to be promoted.
1. Create a conversion in HUAWEI Ads.
2. Configure conversion events in DTM and send them to HUAWEI Ads.
3. The procedure is as follows:
(You can click here to view the detailed procedure. Note that if the registration place of your ad account is in China, you need to submit a ticket online to apply to be added to the trustlist before using conversion tracking.)
A. Sign in to AppGallery Connect, obtain the tracking code snippet on the DTM portal, and embed the code snippet into the pages to be promoted.
a. In AppGallery Connect, click My projects and then Add project, enter a project name, and click OK. Then, click Add app, set Platform to Web and enter an app name, and click OK.
b. Go to Grow > Dynamic Tag Manager, click Enable Dynamic Tag Manager, enter a configuration name and URL to be promoted, and click OK. On the Install web page tracking tag page displayed, copy the code snippet and embed it into all pages to be promoted (including those on mobile phones). The code snippet needs to be embedded only once and will be valid permanently.
B. Create a conversion in HUAWEI Ads.
a. Sign in to HUAWEI Ads, go to Tools > Delivery assistance > Conversion tracking, click New conversion, select Lead tracking and then DTM, and click Continue. Set conversion information, such as Conversion actions, Conversion name, and Click attribution window.
b. Click Next. A conversion is created and its ID is generated. Record the conversion ID because it will be used for tag configuration in DTM later.
c. Configure conversion events in DTM and send them to HUAWEI Ads.
Sign in to AppGallery Connect, go to Grow > Dynamic Tag Manager, and create variables, conditions, and tags to generate a configuration or quickly complete configuration by adding visual events.
After completing configuration, you can release a configuration version for conversion tracking. Then, you can view related conversion events and data in a report in HUAWEI Ads.
In summary, DTM makes ad conversion tracking more efficient. In addition, DTM can be used for anti-fraud analysis and operations efficiency improvement. If you have any questions or would like to know more about the service, feel free to leave a message below.
To learn more about DTM, please visit:
>> DTM official website
>> DTM development guide
>> DTM codelab
If you have any questions, please submit a ticket online.
Does it support only web or both Android and Ios?
Basavaraj.navi said:
Does it support only web or both Android and Ios?
Click to expand...
Click to collapse
Hi, DTM SDK supports Android, IOS and web
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ads are everywhere and we can't escape them. They're on road billboards, shops, buses and buildings. If a world filled with ads sounds daunting and you want to hide indoors, just beware that ads will even jump out at you from your TV, computer, or phone.
It's likely that ads will be around with us for forever. Ads are often seen as annoying, but they can in fact be very helpful. If you are looking for a job, want to go somewhere fun, or are not sure what special thing you can get for your other half's birthday, ads may in fact provide some inspiration to you.
Nowadays, ads are transforming in appearance and purpose. Ads are becoming more intuitive as they are able to target specific audiences. For example, ads about quick fashion will target young adults, while some ads are typically pushed to males. This is an advanced advertising mechanism for brands, media, and users, where all can benefit. Someone gets traffic, someone makes money, and someone gets what they needed. Under ideal conditions, ads, under control and without harmful information spread, mean a lot for us.
As an app developer, I have been trying for a long time to request ads in my app to monetize the traffic and increase revenue. Recently, I encountered some obstacles with the ad traffic monetization data of my own app, and I have been searching for tools to obtain data and analyze ad performance. Collecting such data and then deciding how to analyze ad performance was no easy task, and this was complicated by the many tools and plugins needed to do so. I have used some of the tools found in the industry, but their performance rarely satisfied me.
But I eventually came across a very useful tool, the Publisher Service Reporting API of Ads Kit provided by HMS Core. The traffic monetization service helps me display various ad formats, such as banners, native ads, and rewarded ads, to my users. Routine data tracking is crucial for me to boost revenue. What's more, the Reporting API is key to obtaining ad monetization data, including ad requests, returned ads, impression rate, and click-through rate. I can analyze ad performance based on this data and adjust my monetization strategies accordingly.
But how did I acquire traffic monetization data? Here I'll tell you how I did it.
Implementation Procedure1. Obtain the client ID and key.
Before obtaining the monetization data, prepare an OAuth 2.0 client ID and key, which are needed for generating the access token passed for calling the Reporting API.
Note that the client ID and key are not those in App information (shown in the following red box) in AppGallery Connect, instead, the client ID and key of the server app created under HMS API services > Credentials on HUAWEI Developers.
a. Register as a developer and complete identity verification.
b. Sign in to the console, choose HMS API Services > Credentials, and create a project. If you already have a project, directly select it.
Click the drop-down arrow at the top, click New project, fill in the project name and alias, and click OK.
Select the project you created and click OK.
c. Choose OAuth 2.0 client ID.
If an OAuth 2.0 client ID and key already exist in your project, you can check whether the product type is server app by clicking Edit in the Operation column of the project. If so, skip step d.
If your product is not a server app, you should create an OAuth 2.0 client ID.
d. Select Server app from Product type, set Product name, App type, and Default language, and click Create. In the Note dialog box that displays Client ID and Key, click Confirm.
e. Go to HMS API services > My APIs, ensure that the project is the one you created, and click Add API from library.
f. Click Publisher Service Reporting API under App Services.
g. On the page displayed, click Enable to enable the API. Then you can call the API.
If you disable it and then enable it again, the setting does not take effect in real time due to page cache, for example. The setting will take about 6 to 10 minutes to take effect. If you have waited for longer time, try again.
2. Call the Publisher Service Reporting API.
a. Obtain an access token.
Call this API:
POST https://oauth-login.cloud.huawei.com/oauth2/v3/token
Request example:
Code:
POST /oauth2/v3/token HTTP/1.1
Host: oauth-login.cloud.huawei.com
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials&
client_id=<Client ID>&
client_secret=<Client secret>
Screenshot:
Note that again: the client ID and key are those of the server app but not those of the mobile app created.
b. Call the Reporting API.
POST https://ads.cloud.huawei.com/openapi/monetization/reports/v1/publisher
If you are in Russia, call this API:
POST https://ads-drru.cloud.huawei.ru/openapi/monetization/reports/v1/publisher
Request example:
Code:
POST /openapi/monetization/reports/v1/publisher HTTP/1.1
Content-Type: application/json
Authorization: Bearer ***
Accept: application/json
Content-Length: 233
{
"start_date": "2022-06-01",
"end_date": "2022-06-28",
"filtering": {
"currency": "CNY"
},
"time_granularity": "STAT_TIME_GRANULARITY_DAILY",
"page": 1,
"page_size": 10
}
Screenshot:
As shown in the preceding figure, the data is successfully returned. For more request parameters and response parameters, click here.
In addition, I can customize data display formats to suit my specific app scenarios.
Some Problems You May EncounterWhy was message "access forbidden" returned during the API calling?
Some Problems You May EncounterWhy was message "access forbidden" returned during the API calling?
Possible causes:
You have not enabled the Reporting API.
You have not been authorized to call this API, or your permission has not taken effect yet.
The client ID and key used for obtaining the access token are not those of your server app.
My solutions:
1. Click Add API from library under My APIs and enable the Reporting API.
2. If you disabled and enabled the API again, you may need to wait for 6-10 minutes before the setting takes effect.
3. Check whether your client ID and key belong to a server app when you obtain the access token. To find out it, check the app type on the Credentials page. If it is not a server app, create one and use its client ID and key to request an access token.
ConclusionIf you also think obtaining ad monetization data and dealing with ad issues are annoying as me, you can try this tool to help you in daily work to obtain data and help you in subsequent operations. Hope that my procedure and experience can help more guys and you can also find out more useful methods.