History

Kayos 7327de2843 v0.1.0-V (vc=9): U-3 — streamInfo via rustypipe drives VideoDetail+Player stream_info(url) UniFFI suspend fn replaces NewPipeExtractor's StreamInfo.getInfo() for both VideoDetailViewModel and PlayerViewModel. One Rust round-trip drives the detail screen render AND the player's resolve(). The VideoDetailUiState.info field cached on detail load is reused by the Download dialog so we don't refetch. Deferred to U-3.5: - like_count (rustypipe's player() doesn't surface engagement data; a separate query is needed) - related (player() doesn't include 'up next'; comes from a separate endpoint). Kotlin gets empty list for now — RelatedRow handles it. Type quirks vs my initial guesses (caught by cargo check): - details.duration is u32, not Option<u32> - channel is split into channel_id + channel_name, not a struct - like_count doesn't exist at this query depth - VideoFormat::Webm (lowercase mb), VideoCodec::Avc1 (not H264) - video_only is a separate vec (video_only_streams), not a bool flag		2026-05-24 08:52:43 -07:00
..
strawcore	v0.1.0-V (vc=9): U-3 — streamInfo via rustypipe drives VideoDetail+Player	2026-05-24 08:52:43 -07:00
Cargo.toml	v0.1.0-V (vc=9): U-3 — streamInfo via rustypipe drives VideoDetail+Player	2026-05-24 08:52:43 -07:00
README.md	v0.1.0-U (vc=8): Phase U-1 + U-2 — Rust core + rustypipe search	2026-05-24 08:36:50 -07:00

README.md

`rust/` — strawcore: Rust YouTube core for Straw

Phase U- of the Straw build. Goal: replace the Java NewPipeExtractor dependency with a Rust core (rustypipe + tokio + reqwest), exposed to the Kotlin/Compose UI via UniFFI. Compose UI stays in Kotlin — only the YouTube/Innertube fetching layer moves to Rust.

Phases

Phase	What
U-1	Toolchain + UniFFI smoke test (`hello_from_rust`) round-tripping through JNA. No real APIs yet.
U-2	rustypipe search. `SearchViewModel` calls the Rust core.
U-3	rustypipe streamInfo + streams. `VideoDetailViewModel` + `PlayerViewModel` use it.
U-4	rustypipe channel + tabs. `ChannelViewModel` + `SubscriptionFeedViewModel`.
U-5	Rip NewPipeExtractor Java dep. Measure APK + cold-fetch latency before/after.
U-6 (stretch)	SponsorBlock + RYD HTTP through reqwest + tokio in the same lib.

Build chain

crafting-table
├── rustup stable (target add: aarch64-linux-android, armv7-linux-androideabi,
│                  x86_64-linux-android, i686-linux-android)
├── cargo-ndk      (cross-compile helper)
├── android-sdk    (ANDROID_HOME, sdkmanager, build-tools, platforms)
└── android-ndk    (ANDROID_NDK_HOME, r27c LTS at /caches/android-sdk/ndk/...)

Gradle (strawApp/build.gradle.kts)
├── cargoBuild         Exec task → cargo ndk -t <abi>... -o jniLibs/ build --release
├── uniffiBindgen      Exec task → cargo run --bin uniffi-bindgen ... --library libstrawcore.so
└── source-set wiring  generated Kotlin lands in strawApp/src/main/java/uniffi/strawcore/

Runtime (StrawApp.onCreate)
├── System.loadLibrary("strawcore")
└── uniffi.strawcore.initLogging()

Why UniFFI (and not raw JNI / JNA bindings)

Hand-written JNI: tedious, error-prone, every type change is two files (Kotlin + Rust) that must stay in sync.
Raw JNA: better, but you still hand-write the Kotlin side and worry about string ownership.
UniFFI: write Rust, annotate with #[uniffi::export], get a Kotlin shim generated. Strings, structs, enums, Result types, async functions all cross the boundary transparently. The runtime is JNA under the hood.

When in doubt

cargo check -p strawcore --target aarch64-linux-android — fast iteration.
cargo run --bin uniffi-bindgen -- generate ... — regenerate Kotlin bindings.
adb logcat -s strawcore — Rust log::info!() lands here.
aapt dump badging strawApp/build/outputs/apk/debug/strawApp-debug.apk — inspect what ABIs/native-libs the APK carries.