[RFC] Recommend apple-cryptokit-rs for App Store Export Compliance

Problem

Tauri apps using cryptography face export compliance challenges when submitting to the App Store. Apps must either use Apple-provided cryptographic algorithms or provide additional export documentation.

Solution

The apple-cryptokit-rs crate wraps Apple's native CryptoKit framework, providing:

• App Store compliance: Qualifies for export compliance exemptions
• System-level crypto: Uses only Apple-provided algorithms
• Rust-friendly APIs: Memory-safe interfaces for Tauri apps

Usage Example

// Cargo.toml
[dependencies]
apple-cryptokit-rs = "0.1.0"

// In your Tauri app
use apple_cryptokit::hashing::sha256_hash;
use apple_cryptokit::symmetric::aes::{aes_gcm_encrypt, aes_gcm_decrypt};

#[tauri::command]
fn secure_hash(data: &str) -> String {
    let hash = sha256_hash(data.as_bytes());
    hex::encode(hash)
}

Benefits

• ✅ No export compliance paperwork needed
• ✅ Optimized Apple crypto implementations
• ✅ Maintains Rust ecosystem compatibility
• ✅ Reduces App Store review friction

This would help many Tauri developers avoid common App Store submission issues.

Review the App Store export-compliance documentation and the Cargo.toml usage example described in the issue. Determine where a recommendation for apple-cryptokit-rs belongs, then document its Tauri usage and the export-compliance outcome described here.