mapbox / mapbox/mapbox-maps-android

binary sizes

Open
#2,705 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triaged feature :green_apple:
Dominant language
Kotlin
Stars
578
Forks
161
PR merge metrics
No merged PRs in 30d

Description

New Feature

Reduce binary size.

Why

Currently MapBox SDK compose NDK is huge with the ~8.3mb for arm64-v8a.

Isn't it possible to reduce the output size at all?

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no files, tests, or entry points. Start by measuring the reported ~8.3 MB arm64-v8a Mapbox SDK NDK binary and tracing how the Android build produces it. Done would require an identified, validated approach that reduces the binary size without breaking the SDK.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.