How to retain users in today’s increasingly competitive app market is a pressing issue within the industry, and there are many potential ways of going about it.
One of the top solutions is to reduce the size of your app so that users are less tempted to uninstall it when their storage runs low. To that end, a growing number of developers have attempted to reduce the size of their apps by integrating smaller SDKs. This article introduces the SDK sizes of various AppGallery Connect services so that you have a better understanding of how they will affect the size of your app.
SDKDirect DependencySDK Size (KB)AppGallery Connect base frameworkagconnect-credential103agconnect-https33agconnect-core35datastore-annotation3datastore-core6com.huawei.hmf:tasks:1.4.1.30025App Linking50AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0 487com.huawei.hms:hianalytics:5.0.5.301810App Messaging702com.huawei.hmspendevice:5.0.4.301402AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487com.squareup.picassoicasso:2.71828152com.huawei.hms:hianalytics:5.0.5.301408Auth Service77AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Remote Configuration21com.huawei.hmspendevice:5.0.4.301402agconnect-abtest9AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487com.huawei.hms:hianalytics:5.0.5.301408Cloud Functions14agconnect-auth77AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Crash65com.huawei.hmspendevice:5.0.4.301402com.huawei.hms:hianalytics:5.0.5.301408AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487crash-native323agconnect-crash65com.huawei.hmspendevice:5.0.4.301402com.huawei.hms:hianalytics:5.0.5.301408AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487APM237agconnect-remoteconfig21com.huawei.hmspendevice:5.0.4.301402com.huawei.hms:hianalytics:5.0.5.301408AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Cloud DB81AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Cloud Storage135AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487
As shown in the table, the largest dependent modules are HiAnalytics and the okhttp package required for sending network requests.
The HiAnalytics package consists of the hiAnalytics and opendevice modules, which have a combined size of around 1 MB. However, the actual size added by the two modules to your app is not necessarily 1 MB.
For example, the okhttp package is required for sending most network requests and may already exist in your app before you integrate any AppGallery Connect SDK.
If so, the okhttp package won’t be included when you integrate the SDK into your app and package the app, which will make your app 487 KB smaller. Meanwhile, the hiAnalytics and opendevice modules are mandatory only when you integrate Crash and APM. You can simply discard these two modules if your app does not need to collect data of services such as App Linking, App Messaging, and Remote Configuration, which further reduce your app size by 810 KB. Currently, these two modules had been decoupled from AppGallery Connect SDKs and you can add their dependencies manually as required.
SummaryIf your app already contains the okhttp package, and you are not planning to integrate HUAWEI Analytics, the SDK sizes of AppGallery Connect services can be minimized.
For more information about AppGallery Connect services, please visit:
https://developer.huawei.com/consum...ides/agc-get-started-android-0000001058210705
devwithzachary said:
How to retain users in today’s increasingly competitive app market is a pressing issue within the industry, and there are many potential ways of going about it.
One of the top solutions is to reduce the size of your app so that users are less tempted to uninstall it when their storage runs low. To that end, a growing number of developers have attempted to reduce the size of their apps by integrating smaller SDKs. This article introduces the SDK sizes of various AppGallery Connect services so that you have a better understanding of how they will affect the size of your app.
SDKDirect DependencySDK Size (KB)AppGallery Connect base frameworkagconnect-credential103agconnect-https33agconnect-core35datastore-annotation3datastore-core6com.huawei.hmf:tasks:1.4.1.30025App Linking50AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0 487com.huawei.hms:hianalytics:5.0.5.301810App Messaging702com.huawei.hmspendevice:5.0.4.301402AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487com.squareup.picassoicasso:2.71828152com.huawei.hms:hianalytics:5.0.5.301408Auth Service77AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Remote Configuration21com.huawei.hmspendevice:5.0.4.301402agconnect-abtest9AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487com.huawei.hms:hianalytics:5.0.5.301408Cloud Functions14agconnect-auth77AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Crash65com.huawei.hmspendevice:5.0.4.301402com.huawei.hms:hianalytics:5.0.5.301408AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487crash-native323agconnect-crash65com.huawei.hmspendevice:5.0.4.301402com.huawei.hms:hianalytics:5.0.5.301408AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487APM237agconnect-remoteconfig21com.huawei.hmspendevice:5.0.4.301402com.huawei.hms:hianalytics:5.0.5.301408AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Cloud DB81AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487Cloud Storage135AppGallery Connect base framework205com.squareup.okhttp3khttp:3.11.0487
As shown in the table, the largest dependent modules are HiAnalytics and the okhttp package required for sending network requests.
The HiAnalytics package consists of the hiAnalytics and opendevice modules, which have a combined size of around 1 MB. However, the actual size added by the two modules to your app is not necessarily 1 MB.
For example, the okhttp package is required for sending most network requests and may already exist in your app before you integrate any AppGallery Connect SDK.
If so, the okhttp package won’t be included when you integrate the SDK into your app and package the app, which will make your app 487 KB smaller. Meanwhile, the hiAnalytics and opendevice modules are mandatory only when you integrate Crash and APM. You can simply discard these two modules if your app does not need to collect data of services such as App Linking, App Messaging, and Remote Configuration, which further reduce your app size by 810 KB. Currently, these two modules had been decoupled from AppGallery Connect SDKs and you can add their dependencies manually as required.
SummaryIf your app already contains the okhttp package, and you are not planning to integrate HUAWEI Analytics, the SDK sizes of AppGallery Connect services can be minimized.
For more information about AppGallery Connect services, please visit:
https://developer.huawei.com/consum...ides/agc-get-started-android-0000001058210705
Click to expand...
Click to collapse
Thanks for sharing very useful .
Related
Symptom
When I submitted my app to AppGallery Connect for self-check, the following message was displayed:
MAJOR:22: Integrate the version update API (checkUpdate). If you already integrate the API, check whether the HMS SDK code is obfuscated in the configuration file. For details about how to modify the configuration file, visit https://developer.huawei.com/consum...es/appgallerykit-preparation#h1-1574846682104.
Analysis
To determine the reason for integrating the API, I submitted a ticket to Huawei technical support in the following link:
https://developer.huawei.com/consumer/en/support/feedback
I was told that this API is required for joint operations games and apps for which HUAWEI AppGallery Connect Distribution Service Agreement For Paid Apps is signed. For details about how to integrate the API, please refer to:
Joint operations games:
https://developer.huawei.com/consum...lery-connect-Guides/appgallerykit-game-update
Joint operations apps:
https://developer.huawei.com/consum...llery-connect-Guides/appgallerykit-app-update
If you have not signed HUAWEI AppGallery Connect Distribution Service Agreement For Paid Apps, check whether corresponding resource files for the IAP SDK or DRM SDK have been introduced to your app project. If so, the self-check tool will regard your app as a joint operations app, and prompt you to integrate the checkUpdate API. In this case, delete the related resources and perform the self-check again.
Solution
In addition to joint operations apps that integrate the IAP SDK, other apps have introduced resource files.
Then, after I had deleted the IAP-related resource files, based on the reply from Huawei technical support, the problem was ultimately resolved during self-check.
The success of an app is not just dependent on the value it offers users, but also how efficiently it reaches them. HUAWEI AppGallery Connect app service platform is designed to help app developers improve development and operations efficiency, attract a wider range of users and generates greater revenue, by offering end-to-end services at every step along the way, from app innovation and development, to distribution, operations, and analysis, with support for a broad range of devices.
App developers share a number of common challenges when releasing an app. For example, how to acquire most users? How to reach target users with optimal precision? How to improve monetization while continuing to acquire users? All of these challenges, and many others, are addressed at the AppGallery Connect Academy · Live event, offering actionable insights on how to grow your app business to new levels.
Partner with AppGallery Connect to grow your business, by harnessing global app distribution and broad-based device support.
As a top-3 global app marketplace, HUAWEI AppGallery provides access to a wide variety of both global and locally-oriented apps across 18 app categories and has attracted over 530 million MAU in 170+ countries and regions by the end of 2020.
In order to continuously provide quality and safe app experience for users, AppGallery has launched AppGallery Connect, a one-stop app service platform that empowers developers' app creativity and business growth. As of the end of 2020, AppGallery Connect had already partnered with 2.3 million developers across the globe, facilitating 384 billion app distributions on AppGallery in 2020 alone.
A/B Testing: Conduct group experiments to determine the best variant for your app.
A/B Testing enables you to make informed operations decisions based on specific data. It conducts group experiments to determine user preferences related to UI design, written content, and product functions. A/B Testing does not directly boost user activity, but its experiment results help you determine user preferences, and improve indicators such as DAU and MAU.
In one notable example, an app team split users into two groups to determine whether a new function could facilitate user engagement. This function was only made available to one group. Two weeks later, the daily active duration of users in the treatment group was half an hour longer than that for users in the control group. In light of this, the team ultimately decided to release the function, and was proven correct, as the daily user activity duration rose by 15%.
Remote Configuration: Change how your app looks and works, without requiring users to update the app.
Sleep Sounds is an app that provides lullabies and natural white noise to help users fall asleep with greater ease. The Sleep Sounds team utilized AppGallery Connect Remote Configuration to make changes to their app, while also avoiding the need to release a new version. The team simply made changes on the cloud, and the changes took effect on the app side. This enabled Sleep Sounds to make targeted recommendations to users based on their local market, age, gender, and other attributes, upon obtaining the user's consent. Just two weeks into using the service, Sleep Sounds saw an 8% increase in its number of users, and a 10% increase in user engagement.
App Linking: Provide a consistent link access across platforms and versions, for higher conversion rates.
App Linking helps you create deep links for in-app content, and display them across a wide range of channels, including those on social media. By tapping a link, the user can directly access the in-app content. Those users who have not installed the app will be redirected to HUAWEI AppGallery for download and installation.
For example, if you are planning a promotion in your app, App Linking can help you place the promotional link on a diverse range of ad platforms. Existing users can then launch the app and open the specific page with just a tap; new users will be redirected to AppGallery to download and install the app, and then to the specific promotional page upon launching the app.
Linking premium in-app content enables you to convert mobile web users into native app users, which provides a way to grow your user base. App Linking also supports tracing parameters, which means that you can view data analysis and trace traffic sources across different channels.
App Messaging: Send contextual messages to engage users.
With the Call Screen app, users can choose from a range of customized incoming call skins, some of which have visual alerts to ensure that important calls aren't missed. But the developer found that some of the new skins they had released were not being downloaded by very many users, and reviews of the skin were mixed. To address this, the developer used the App Messaging service in AppGallery Connect to notify users of new available skins, after obtaining their consent. Now, when a user signs in, Call Screen provides them with skin recommendations based on their preferences. The service helped increase the number of app users by 11% in just three weeks.
AppGallery Connect Academy · Live: We Connect, You Grow
If you'd like to learn more about the operations and growth services in AppGallery Connect, you simply can't miss AppGallery Connect Academy · Live held from 11:00 UTC+02:00 on March 31, 2021. This event will walk you through how to harness AppGallery's global distribution capabilities to grow your user base, and how to better monetize your app by using AppGallery Connect's operations services to target and activate users. These services, and many others, can help your app stand out from the competition.
Any doubts about this LIVE, click here to leave your reply. We'll answer some questions during the FAQs session.
Thanks for sharing
Hey! I also have my own business and I know that business promotion is very important in any company.I have always spent a lot of time on documentation and other minor matters.But I found a solution.I started using the services of a special company in the UK.Go to this website to learn more information! They will help you with all documents and other tasks.
Do all those features support non-Huawei phones?
Contact Shield is a basic contact diagnosis service developed based on the Bluetooth low energy (BLE) technology. Global public health institutions can authorize developers to develop COVID-19 contact diagnosis apps using Contact Shield APIs. These apps can interact with other devices while protecting user privacy to check whether a user has been in contact with a person tested positive for COVID-19. If so, the user will be notified and instructed to take relevant measures, effectively controlling the spread of the virus.
Working Principles
1. The mobile phone of B broadcasts the DSC (Dynamic Sharing Code). The phone can generate a DSC collection based on the periodic key on each day, select a DSC based on the current time, and broadcast the DSC to surrounding devices through BLE.
2. The mobile phone of A receives the DSC broadcast by B. After scanning the DSC broadcast by the mobile phone of B, the mobile phone of A records the current timestamp and received signal strength indicator (RSSI), and stores the data in a local database.
3. If B is diagnosed as a COVID-19 patient, the app obtains authorization from B and uploads the periodic key within the virus incubation period (14 days by default) to the app server or the server specified by a public health institution. In this case, the periodic key of B is called the shared key.
4. The app of A periodically downloads the compressed package of periodic keys of the diagnosed user from the server and calls Contact Shield to perform contact diagnosis. Contact Shield deduces the DSC collection broadcast by the diagnosed person based on the periodic keys provided by the app.
5. During contact diagnosis, Contact Shield uses the DSC collection generated in 4 to match a record in the DSC data table of the last 14 days stored in the local database. After the matching is complete, Contact Shield generates a diagnosis report and notifies A of the contact diagnosis result through the app.
Based on the diagnosis report, A knows whether he or she has been in close contact with the diagnosed user and the potential contact risk level.
When the Contact Shield invokes the interface, the error code -1 is returned. There are many possible causes in this scenario. This section describes the troubleshooting procedure for this error code.
\Note: If the error code -1 is displayed, view the error log and search for the keyword HmsNearbyKit_sdk_ContactApiImpl. Generally, the log contains an error code with the actual error cause.
1. Developer have not applied for the Contact Shield permission (Error code 6004).
Cause 1：
Unlike other HMS SDKs, the Contact Shield SDK requires developers to send related information through emails to grant permissions.
For details about how to apply for the contact guard API permission, see:
https://developer.huawei.com/consum...equest-access-0000001058448610?ha_source=hms1
Cause 2：
The agconnect-services.json file in the local project does not match.
Check whether the agconnect-services.json file added to the local project is the same as the required agconnect-services.json file.
You can download the new agconnect-services.json file from the AGC official website and commission the project again.
For details about how to download the agconnect-services.json file, see：https://developer.huawei.com/consum...-integratesdk-0000001058897058?ha_source=hms1
2. The generated APK signature file (.keystore or .jks file) is different from the SHA-256 information configured on the AGC. (Error code 6003).
The APK signature file must be the same as the signature configured on the AGC.
The configuration procedure is as follows:
https://developer.huawei.com/consum...ld-config-agc-0000001057648627?ha_source=hms1
3. When the API is invoked for the first time, the mobile phone is not connected to the network.
When the contact guard API is invoked for the first time, if the mobile phone is not connected to the network, the error code -1 is returned.
In this scenario, ensure that the network connection is normal and invoke the Contact Shield API again.
4. After the startContactShield() interface is invoked, the pop-up message is manually canceled.After the startContactShield() interface is invoked, the following dialog box is displayed.
User must select Allow to invoke the Contact Shield API.
Note: The error code in the latest Contact Shield has been updated to 8015.
5. User do not have the location permission of the HMS Core APK.When the startContactShield() interface is invoked, in addition to the pop-up for point 4, the dialog box shown in the following figure is displayed if you do not have the location permission.
User must select “ALLOW ALL THE TIME”to invoke the Contact Shield API.
Note: The error code in the latest Contact Shield has been updated to 8103.
To view the permission, choose Settings > Apps > Apps > Search HMS Core > Permissions > location.
6. When the putSharedKeyFiles() interface is invoked, the file format provided by the developer is incorrect.When the putSharedKeyFiles interface of the Contact Shield is invoked, the transferred file in List<File> files is incorrect.
The format and generation method of this file are the same as those in Google's Exposure Notifications.
For more details, you can go to:
l Our official website
l Our Development Documentation page, to find the documents you need
l Reddit to join our developer discussion
l GitHub to download demos and sample codes
l Stack Overflow to solve any integration problems
Original Source
Curious about how to integrate HMS Core kits into your apps? Or how to convert your apps integrated with third-party mobile services? Want the quickest and simplest way to release them on HUAWEI AppGallery?
Introducing HMS Toolkit.
This IDE plugin provides tools such as Getting Started, Configuration Wizard, and Repository and is designed for every stage of development: creation, coding, debugging, testing, releasing, and quality analysis. Armed with HMS Toolkit, you too can develop your own HMS Core-integrated apps in Android Studio and release them at lower cost and higher efficiency.
Every development phase, faster and easier
Getting Started demonstrates each HMS Core kit.
Configuration Wizard walks you through all the necessary settings, so no more looking up the manual or switching tools. Configure multiple kits at the same time, for different scenarios, so no more four-hour jobs – now just 5 minutes.
Repository shows you SDK version, package size, and usage to make integration and version a one-stop-shop. Automatically add an SDK library dependency after you select the library, get the latest SDK version, and upgrade the SDK with just one click.
Coding Assistant offers HMS Core API descriptions and sample code and templates by scenario. Drag and drop to generate and configure code, and get automatic issue warnings and recommendations.
Convertor helps you move from third-party APIs to HMS APIs. Convert your source code either with Add HMS API (add code to call HMS APIs to match third-party APIs so both can be called as needed), or To HMS API (replace code to call third-party APIs with code to match HMS APIs so only HMS APIs can be called).
Cloud Debugging uses a remote real device to quickly locate and resolve problems. Currently, choose from various Huawei devices if you're in the Chinese mainland, Russia, Asia Pacific, and West Europe. Quickly access the nearest site for single-step or ADB debugging. Drag and drop to upload files, zoom in and out onscreen, and toggle definitions between smooth, SD, and HD on the remote real device as needed.
Cloud Testing tests your app in one click to quickly detect problems on any device. Get screenshots for compatibility, stability, performance, and power consumption.
Publish to AppGallery Connect makes uploading easier to do from the IDE. Choose to upload either the packaged APK of the current project (default) or a local package, and its parameters will be checked against the release requirements. Once it's uploaded, you'll be prompted to access the HUAWEI AppGallery Connect release page.
HMS Toolkit also allows you to generate an API or demo project in one click for quickly verifying and calling the image classification model in your app.
Easy to install
Start Android Studio, go to File > Settings > Plugins > Marketplace, search for HMS Toolkit, and click Install. Or sign in and get it on the HUAWEI Developers official website.
HMS Toolkit will continue to be optimized to help you and other developers around the world create a smart life for users.
If you have any questions, please submit a ticket. Huawei technical support will reply to you as soon as possible.
For more information about HMS Toolkit, go to >>
For how to quickly integrate each kit using HMS Toolkit, go to >>
For more operation tutorials, go to >>
For more details, you can go to:
l Our official website
l Our Development Documentation page, to find the documents you need
l GitHub to download demos and sample codes
l Stack Overflow to solve any integration problems
Very useful sharing.
Background
When using an app, if pop-up ads keep appearing when we browse app pages but we are not interested in the advertised content, not only will our browsing experience be negatively affected, but we will also quickly become tired of the advertised content. Unwanted ads are usually annoying. Aimless ad targeting and delivery will result in the wrong ads being sent to users and cause poor ad performance.
So, as publishers, how do we guarantee that we can deliver ads to audiences who will be interested in them and how can we decrease users' resistance to advertising? The answer is to collect information about the user requirements of your target audiences or to really know them, and to do so in a way that causes the least annoyance. But when a user is unwilling to share their personal data, such as age, gender, and interests, with my app, placing an ad based on the page that the user is browsing is a good alternative.
For example, a user is reading an article in a news app about the fast-paced development of electric vehicles, rapidly improving battery technology, and the expansion of charging stations in cities. If the targeted advertising mechanism understands the context of the article, when users continue to read news articles in the app, they may see native ads from nearby car dealerships for test driving electric vehicles or ads about special offers for purchasing electric vehicles of a certain brand. In this way, user interests can be accurately discovered, and publishers can perform advertising based on the keywords and other metadata included in the contextual information of the app page, or any other content users are reading or watching, without having to collect users' personal information.
But I can't integrate these features all by myself, so I started searching for tools to help me request and deliver ads based on the contextual information on an app page. That's when I had the great fortune to discover Ads Kit of HMS Core. Ads Kit supports personalized and non-personalized ads. Personalized ad requests require users to grant the app access to some of their personal information, which may not be palatable for some users. Non-personalized advertising, however, is not constrained by this requirement.
Non-personalized ads are not based on users' past behavior. Instead, they target audiences using contextual information. The contextual information includes the user's rough geographical location (such as city) authorized by the user, basic device information (such as the mobile phone model), and content of the current app or search keyword. When a user browses a piece of content in your app, or searches for a topic or keyword to express a specific interest, the contextual ad system scans a specific word or a combination of words, and pushes an ad based on the page content that the user is browsing.
Today, data security and personal privacy requirements are becoming more and more stringent. Many users are very hesitant to provide personal information, which means that precise ad delivery is becoming harder and harder to achieve. Luckily, Ads Kit requests ads based on contextual information, enabling publishers to perform ad delivery with a high degree of accuracy while protecting user privacy and information.
Now let's take a look at the simple steps we need to perform in order to quickly integrate Ads Kit and perform contextual advertising.
Integration Steps
1. Ensure that the following prerequisites are met before you integrate the Ads Kit:
HMS Core (APK) 4.0.0.300 or later should be installed on devices. If the APK is not installed or an earlier version has been installed, you will not be able to call the APIs of the Ads Kit.
Before you begin the integration process, make sure that you have registered as a Huawei developer and completed identity verification on HUAWEI Developers.
Create a project and add an app to the project for later SDK integration.
2. Import the Ads SDK.
You can integrate the Ads SDK using the Maven repository.
That is, before you start developing an app, configure the Maven repository address for Ads SDK integration in your Android Studio project.
The procedure for configuring the Maven repository address in Android Studio is different for Gradle plugin versions earlier than 7.0, Gradle plugin 7.0, and Gradle plugin versions 7.1 and later. Configure the Maven repository address accordingly based on your Gadle plugin version.
3. Configure network permissions.
To allow apps to use cleartext HTTP and HTTPS traffic on devices with targetSdkVersion 28 or later, configure the following information in the AndroidManifest.xml file:
Code:
<application
...
android:usesCleartextTraffic="true"
>
...
</application>
4. Configure obfuscation scripts.
Before building the APK, configure the obfuscation configuration file to prevent the SDK from being obfuscated.
Open the obfuscation configuration file proguard-rules.pro in your app's module directory of your Android project, and add configurations to exclude the SDK from obfuscation.
Code:
-keep class com.huawei.openalliance.ad.** { *; }
-keep class com.huawei.hms.ads.** { *; }
5. Initialize the SDK.
You can initialize the SDK in the activity, or initialize the SDK by calling the HwAds.init(Context context) API in the AdSampleApplication class upon app launch. The latter method is recommended, but you have to implement the AdSampleApplication class by yourself.
6. Request ads based on contextual information.
The SDK provides the setContentBundle method in the AdParam.Builder class for you to pass contextual information in an ad request.
The sample code is as follows:
Code:
RewardAd rewardAd = new RewardAd(this, rewardId);
AdParam.Builder adParam = new AdParam.Builder();
String mediaContent = "{\"channelCategoryCode\":[\"TV series\"],\"title\":[\"Game of Thrones\"],\"tags\":[\"fantasy\"],\"relatedPeople\":[\"David Benioff\"],\"content\":[\"Nine noble families fight for control over the lands of Westeros.\"],\"contentID\":[\"123123\"],\"category\":[\"classics\"],\"subcategory\":[\"fantasy drama\"],\"thirdCategory\":[\"mystery\"]}\n";
adParam.setContentBundle(mediaContent);
rewardAd.loadAd(adParam.build(), new RewardAdLoadListener());
ConclusionNowadays, advertising is an important way for publishers to monetize their apps and content, and how to deliver the right ads to the right audiences has become a key focus point. In addition to creating high quality ads, significant efforts should be placed on ensuring precise ad delivery. As an app developer and publisher, I was always searching for methods to improve ad performance and content monetization in my app. In this article, I briefly introduced a useful tool, Ads Kit, which helps publishers request ads based on contextual information, without needing to collect users' personal information. What's more, the integration process is quick and easy and only involves a few simple steps. I'm sure you'll find it useful for improving your app's ad performance.
ReferencesDevelopment Guide of Ads Kit