Skip to content

perf(core): migrate foreground interval aggregation to Rust - #1

Draft
meilide38 wants to merge 7 commits into
mainfrom
refactor/rust-core-aggregation
Draft

meilide38 wants to merge 7 commits into
mainfrom
refactor/rust-core-aggregation

Conversation

@meilide38

Copy link
Copy Markdown
Owner

Summary

  • Add a Rust cdylib core and JNI bridge for per-app foreground interval aggregation.
  • Keep a Kotlin fallback so the app remains functional if the native library cannot load.
  • Build the Rust library for arm64-v8a and armeabi-v7a as part of the database flavor build.
  • Add Rust unit tests to CI and provision the Android NDK for CI and signed Release builds.
  • Remove the duplicate optional-signing Release workflow; retain the existing workflow that refuses to publish unsigned APKs.
  • Document the Kotlin/Rust boundary and build requirements.

Scope

This is the first measured migration slice, not a claim that the whole application has already been rewritten. Android APIs, UI, Room/database schema, permissions and lifecycle remain Kotlin. Further pure business-logic modules can move incrementally after parity tests.

Validation

CI runs cargo test, both flavor unit-test suites, and both debug APK builds. The signed Release workflow continues to use the existing KEYSTORE_BASE64, KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD secrets and must verify the same signing certificate before publishing.

Compatibility

No application ID, database schema, versioning format or signing configuration is changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant