I'm a real human. I'm not a bot. Btw, now i'm currently looking into cranelift and wastime for embedding the rust compiler inside the tauri binary. And it is not fun. Have you tried that?
AppleScript execution is running outside of the tauri app; the current app has no way to get the output reliably of the AS code generated by AI. Unless I do a semantic review of the code to make sure that I can capture the output/error of AS execution.
By now, AS run 90% of the time, when it is a single-phase execution, then it is easy. But multiphase execution has a high chance of having the code break in the middle.
That is why I instruct the AI engine to prefer sequential execution (atomic fashion)
Under the hood, it is wrapping Tauri, and as the live preview benefits from a proxy-tauri backend to let you feel like you are already in prod mode. I like that feeling too.
There is no Python, only Rust, AppleScript, and Shell script.
Thanks, I failed after three attempts. I tried to build a clone of the current backend Tauri at dev time. The only approach that worked well was having a proxy. But now I'm looking into embedding a compiler inside the Tauri Rust at prod time.
But you're right that the UI layer is still HTML/CSS rendered in a webview. It's not SwiftUI or Win32. Tauri gets you closer to native than Electron, smaller binaries, lower memory, OS-level webview, but it's not the same as writing Cocoa or GTK directly.
For what this project does (AI generating full apps), Tauri hits a good tradeoff: one codebase, all platforms, real system access, and the AI is much better at generating React than platform-specific UI frameworks. I tried to do the same with Swift it, fails meserably