Open MarijnS95 opened 5 days ago
The crate has specific functionality for Android that is conditionally compiled when targeting android as the OS. This is indicated by the [cfg(target_os = "android")] module in the code, which allows interaction between Android and Rust through JNI (Java Native Interface). In the android module, we provide functions that allow Android apps (using Java or Kotlin) to call Rust functions, such as creating databases, tables, inserting data to parquet, and querying them. This is useful for integrating Rust’s performance and capabilities directly into Android apps via JNI.
This crate is categorized under os::android-apis because it provides the necessary bindings to use it within Android through Rust-JNI
This crate is categorized under os::android-apis because it provides the necessary bindings to use it within Android through Rust-JNI
If I'm not mistaken the design of the os
and os::android-apis
category in particular describe crates that expose OS-specific functionality to Rust.
Granted, having more Android (library) related categories would be nice to have.
Thanks for the clarification and pointing this out! You're absolutely right. I'll consider re-evaluating the categorization accordingly.
Hi! I just saw this crate pop up as the second one under the new https://crates.io/categories/os::android-apis category, and wondered what its relation to Android is. Does it provide OS-specific APIs to Android (but nothing else, given that there are no other
os::xxx-apis
categories listed)? Android is never mentioned in the main readme for example, so I'm curious how it fits in the ecosystem :+1: