[New Rule] AppMetrica

Open Beginner friendly
#1,462 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
database

Research direction

Start by reading nearby library rules and the repository’s rule format; the issue names AppMetricaService and PreloadInfoContentProvider as identifiers to check, and links the Android SDK source. Add an AppMetrica rule that recognizes those identifiers and records the supplied label and metadata. Confirm the rule matches the listed apps and follows the format used by neighboring rules.

Written by the indexing model from the issue text.

Description

Library filename / 库文件名

See Files & Comment

Library label / 库的文字标签

AppMetrica

Library team / 库的开发团队

Yandex

Files & Comment / 同组文件 & 备注
  • Services:
io.appmetrica.analytics.internal.AppMetricaService
  • Content providers:
io.appmetrica.analytics.internal.PreloadInfoContentProvider

More might exist, see source code linked below

In Apps / 出现于
Name Application ID VersionName VersionCode Source
Aquapark.io com.cassette.aquapark 6.53.1 1622 Play Store
Ball Blast com.nomonkeys.ballblast 4.6.0 3980 Play Store
Flappy Dunk com.acidcousins.fdunk 2.17.0 22017 Play Store
Geometry Dash Lite com.robtopx.geometryjumplite 2.2.148 44 Play Store
Helix Jump com.h8games.helixjump 6.9.1 60000094 Play Store
Library icon / 库图标
  • AppMetrica icon:
AppMetrica icon
Library description / 库描述

AppMetrica is a free real-time ad tracking and mobile app analytics solution. AppMetrica covers the three key features for discovering your app's performance — ad tracking, usage analytics and crash analytics.

Library relative URL / 相关链接

https://github.com/appmetrica/appmetrica-sdk-android

Dominant language
Python
Stars
201
Forks
85
Avg merge
1m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LibChecker/LibChecker-Rules

All issues in LibChecker/LibChecker-Rules

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.