Cool to see another Rust-based approach to this. I've been building something in the same space using Tauri v2, so the core is also Rust but running natively rather than through WASM. Curious how you're finding the wasm-bindgen boundary for a text-heavy app, I went native partly because I was worried about the overhead of keystroke-level interactions crossing between JS and the Rust engine. Has that actually been a problem in practice or am I overthinking it?
Looks like you're parsing Fountain under the hood, is that correct?
That reading tool is rad as well, nice touch.