ARK-Builders / ARK-Builders/Navigator

Performance metrics gathering

Open
#165 1 comment 0 reactions 0 assignees View on GitHub
good first issue performance
Dominant language
Kotlin
Stars
16
Forks
14
PR merge metrics
No merged PRs in 30d

Description

We should embed measurements into the code and send analytics to our side.
Metrics reporting must be optional and turned off by default in production build (see #77).

Metrics should cover various potentially long operations.
Reports should contain information about device used and parameters of operation called.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing issue #77 and the existing Kotlin/Android project structure; this issue names no files, entry points, or tests. Identify which potentially long operations and analytics destination are in scope, then define how reporting is disabled by default in production and what device and operation parameters reports include. Done requires an agreed scope and tests or verification for optional, production-off reporting.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
observability, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.