Having rich UI library was important for us too. We went with Tauri because we wanted access to web UI libraries.

RAW files aren't supported yet, but we plan on including them. We're also working on a support page, I'll share that here when it's out.

Thank you! Looking forward to the new features, I'll keep an eye out.

Yeah, we were talking about the app itself, it was way too big when we first started.

Now knowing how big Electron is off the bat compared to Tauri, I think I'd have to learn a lot more about how to optimize Electron to build with it again. That said, I think Electron is great for prototyping an idea and quickly getting it out.

Yes, we were able to port the CLIP model to work with ONNX Runtime for inference

May I ask, which version or ORT are you using? Were the outputs identical to PyTorch outputs for the same image?

Yeah, familiarity with the UI component libraries was a big driver in using web technologies for it.

Interesting. I'd love to get our app size down further, under 15MB would be great.

Yes, it's nice that we can support the same functionality we were supporting in our Electron app using a much smaller binary with Tauri.

I'd love to see a comparison like this.

sounds like you built a really useful app for working with large media libraries.

In our case, the bottleneck was related to how big the app was to start and how much we could optimize it to index media files for local AI search.