Skip to content

Conversation

@MarijnS95
Copy link
Member

I was surprised to find the android-properties crate with almost 8 million downloads; this crate hasn't been updated for almost 5 years and the repository is a public archive.

Turns out the only published user of this crate is android-activity, so all those downloads are pulled in from folks using this crate (mainly through winit) to build Android apps.

Instead of using an unmaintained, archived crate, use the properties wrapper and typed API-level wrappers provided in in an upcoming ndk crate release instead:

I was surprised to find [the `android-properties` crate] with almost 8
*million* downloads; this crate hasn't been updated for almost 5 years
and the repository is a public archive.

Turns out the only published user of this crate is `android-activity`,
so all those downloads are pulled in from folks using this crate (mainly
through `winit`) to build Android apps.

Instead of using an unmaintained, archived crate, use the properties
wrapper and typed API-level wrappers provided in in an upcoming `ndk`
crate release instead:
- rust-mobile/ndk#495
- rust-mobile/ndk#479

[the `android-properties` crate]: https://crates.io/crates/android-properties
@rib
Copy link
Member

rib commented Jan 7, 2026

I wonder if there's a way to use ndk_sys if that means the change doesn't require a semver bump and can be backported to 0.6. (though I don't quite recall if ndk_sys types are exposed in the public api for android-activity to know if we can bump the ndk_sys dep on 0.6)

Or, maybe the API is trivial enough to just inline the ffi bindings in android-activity if we want to avoid the external dep without needing any other dep bumps.

@MarijnS95
Copy link
Member Author

By that logic I might as well stop maintaining the ndk and ndk_sys crates, if every project open-codes the bindings and abstractions.

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.

3 participants