home.social

#tauri — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tauri, aggregated by home.social.

  1. »#Tauri is an alternative cross-platform, open-source framework for building desktop and mobile apps using web technologies while leveraging #Rust on the back-end. In replacing #Electron with Tauri, the #Lemonade SDK is now "10x smaller" than before. The pre-built macOS and Windows binaries for example were 101~107 MB with Lemonade 10.2 and are now 7~9 MB with Lemonade 10.3.«

    phoronix.com/news/AMD-Lemonade

  2. I've started sketching out an app I want to develop and as I want it to have Windows, Mac and Linux builds I was starting down the Electron route but then noticed Tauri. Given this apps usage, amount of data it sometimes processes and possible later uses of the code Rust might have some advantages. Anyone on here used both?

    #coding #rust #electron #tauri

  3. YAKE! вместо нейросети: как мы заменили 600 МБ ONNX-реранкера на 400 строк статистики

    В Yttri мы изначально использовали ONNX-реранкер bge-reranker-v2-m3 для RAG-поиска. Качество было хорошим, но цена для local-first desktop-приложения оказалась слишком высокой: около 600 МБ модели, до 1.8 ГБ RAM в пике и ощутимая нагрузка на CPU. В статье разбираю, как мы заменили тяжёлый нейросетевой реранкер на собственную реализацию YAKE! на Rust: без модели, без прогрева, без внешних сервисов и с латентностью порядка микросекунд. Показываю механику алгоритма, интеграцию в RAG, автотегирование, ограничения подхода и главный архитектурный вывод: не каждая AI-задача требует ещё одной нейросети. Иногда лучший AI-компонент - это тот, который удалось удалить.

    habr.com/ru/articles/1027726/

    #Rust #Tauri #RAG #SQLite #Localfirst #NLP #YAKE #Embeddings #Desktop

  4. Trying to automate Tauri app testing on arch linux.

    Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.

    #arch #webkit #tauri

  5. Trying to automate Tauri app testing on arch linux.

    Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.

    #arch #webkit #tauri

  6. Trying to automate Tauri app testing on arch linux.

    Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.

  7. Trying to automate Tauri app testing on arch linux.

    Currently faced an issue of webkitgtk not providing webkitdriver. Anyone knows which package already exists that includes the driver? I am searching over the web, but all I found is a suggestion to build it by myself, which can be okay, yet I think I just had no luck in finding existing package.

    #arch #webkit #tauri

  8. After working with #Tauri for a few months on SilverBullet.plus I do see the appeal of #Electron’s “F it, let’s just ship an entire Chrome instance” approach. Lot of weird OS specific dependencies and curiosities that you don’t have to deal with. Working through it though, not giving up.

  9. So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

    From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

    Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

    I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

    Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

    I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

  10. So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

    From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

    Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

    I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

    Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

    I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

  11. So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

    From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

    Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

    I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

    Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

    I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

  12. So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

    From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

    Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

    I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

    Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

    I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

  13. So I have read some more about the whole #dioxus vs #tauri plus #leptos plus #axum for a #rust #rustlang #desktop app.

    From what I read by now, I would say that I will try the tauri route next. I would still prefer if Dioxus would just work, but what makes me wary about whether Dioxus would be a sustainable choice is that there's a lot of issues in the Dioxus repository that do not even have a reply by a maintainer. My own issues (which are relatively young!) have only little interaction. I get that this is an open source project and maintainer overload and so on, sure. But there's also something about Dioxus being funded? So there are full-time devs (plural!) working on it? What can I say? This makes me wary.

    Going down that tauri route would mean that I would need to build the whole thing myself. That could work, but is more than I would have liked to do. I want to develop my app functionality, not set up a GUI development environment.

    I could also go for a TUI first, but tbh, I would rather like to have a GUI first, with a clean API that I can then reuse to build a TUI on top of it. Not sure why, the other way around would probably work as well 🤔.

    Either way, I would then try leptos as framework for the app, because it looks rather good from what I can read from its documentation, and I can use axum in the backend, which I think fits my needs as well. (Btw developing this with ratatui with a axum backend would also be possible, but that's not the "native way" for a ratatui app, but much more for a leptos app as I understand it, so I expect less headaches here).

    I hope I can get a MVP fast, so I can get back to developing my core application stuff, because there's sooo much missing still.

  14. FiT календарь тренировок — финал трилогии пет-проекта

    Год назад я опубликовал первую статью про разработку приложения календаря тренировок. Спустя 5 месяцев опубликовал рассказ о 10 обновлениях . Сейчас время финала истории - ещё 7 обновлений за 7 месяцев. Сам регулярно пользуюсь приложением - оно добавляет мотивации заниматься спортом дальше, сохраняет график тренировок, следит за объемом выполненных упражнений. На текущий момент в приложении больше 150 зарегистрированных пользователей. Времени на пет-проект уделял крайне мало, но основная функциональность была уже готова ранее. Сейчас на нём можно пробовать что-то новое - получается хороший полигон для испытаний. Исходный код Приложение в RuStore Веб-версия Frontend: Typescript, Vitest, Vite, Vue, Tanstack Query, Vue I18n, Tauri Backend: Typescript, Vitest, Esbuild, Fastify, Mongoose, MongoDB, Swagger

    habr.com/ru/articles/1021790/

    #vue #vuejs #vuejs #петпроект #петпроекты #tauri #мобильные_приложения #javascript #typescript #вебприложения

  15. #Gatsby starters and plugins (some starters use Axios for data fetching)
    #SvelteKit example projects (can be configured to use Axios)
    #Tauri apps (examples showing Axios with custom fetch adapter)
    #Nodejs backend utilities and CLI tools (server-side HTTP requests with Axios)

  16. starters and plugins (some starters use Axios for data fetching)
    example projects (can be configured to use Axios)
    apps (examples showing Axios with custom fetch adapter)
    backend utilities and CLI tools (server-side HTTP requests with Axios)

  17. #Gatsby starters and plugins (some starters use Axios for data fetching)
    #SvelteKit example projects (can be configured to use Axios)
    #Tauri apps (examples showing Axios with custom fetch adapter)
    #Nodejs backend utilities and CLI tools (server-side HTTP requests with Axios)

  18. Fresh Mayhem Linux desktop app is live 🐧

    Control your HackRF + PortaPack with plain English instead of CLI flags. Built with Rust, runs locally —
    no cloud, no account.

    - Auto-detects your device
    - Built-in RF knowledge base
    - LLM capture analysis via Ollama
    - Browsable LOOT tab

    Beta — report bugs, star the repo, share with fellow RF nerds.

    Download: superbasic.studio/software/fre
    GitHub: github.com/superbasicstudio/fr

  19. Fresh Mayhem Linux desktop app is live 🐧

    Control your HackRF + PortaPack with plain English instead of CLI flags. Built with Rust, runs locally —
    no cloud, no account.

    - Auto-detects your device
    - Built-in RF knowledge base
    - LLM capture analysis via Ollama
    - Browsable LOOT tab

    Beta — report bugs, star the repo, share with fellow RF nerds.

    Download: superbasic.studio/software/fre
    GitHub: github.com/superbasicstudio/fr

    #HackRF #SDR #Linux #Rust #Tauri #PortaPack #InfoSec #BuildInPublic

  20. Fresh Mayhem Linux desktop app is live 🐧

    Control your HackRF + PortaPack with plain English instead of CLI flags. Built with Rust, runs locally —
    no cloud, no account.

    - Auto-detects your device
    - Built-in RF knowledge base
    - LLM capture analysis via Ollama
    - Browsable LOOT tab

    Beta — report bugs, star the repo, share with fellow RF nerds.

    Download: superbasic.studio/software/fre
    GitHub: github.com/superbasicstudio/fr

    #HackRF #SDR #Linux #Rust #Tauri #PortaPack #InfoSec #BuildInPublic

  21. Shoutout to Ofek Bickel aka sinisterMage, who is seemingly building a complete Julia IDE from the ground up single-handedly.

    github.com/sinisterMage/JulIde

    And the repo has the best readme.

    #Julia #ide #programming #rust #tauri

  22. Под капотом Beetroot: как я написал менеджер буфера обмена на Tauri v2 и Rust с установщиком 6 МБ

    Переезд с macOS на Windows для разработчика часто сопровождается болью от потери привычного инструментария. В моем случае решающим стимулом свитчнуться на ПК стала мощная видеокарта. Сейчас мой верный MacBook всё так же лежит на столе и даже подключен к мониторам, но по факту именно Windows (как бы сильно она мне ни не нравилась) стала основной рабочей системой. И главной болью при этом переходе стал менеджер буфера обмена. На маке я привык к тому, что могу найти скопированный лог недельной давности за секунду, вставить текст без форматирования одним шорткатом и вообще не думать о том, что история куда-то исчезнет. Штатный инструмент Windows (Win+V) разочаровал моментально: лимит в 25 элементов, отсутствие поиска и полное обнуление после перезагрузки ОС. Поиск альтернатив тоже не увенчался успехом: Ditto надежен, но выглядит как гость из 2005 года, а мощный CopyQ имеет перегруженный интерфейс суровой системной утилиты. Ни в одном из них не было современных функций вроде OCR «из коробки» или базовой интеграции с LLM для обработки текста на лету. Решение напрашивалось само собой — написать свой велосипед. Но сделать его легким, быстрым и без Electron. В этой статье расскажу о том, как устроен Beetroot — менеджер буфера обмена с бесконечной историей, нативным OCR и AI-трансформациями. Как это работает под капотом

    habr.com/ru/articles/1008770/

    #Rust #Tauri #буфер_обмена #SQLite #Windows_API #архитектура #петпроект

  23. Simply Plural is shutting down in June.

    Ampersand, pretty much the only alternative that mostly lines up with our needs, does not aim to provide feature parity with Simply Plural (e.g. by implementing privacy-preserving fronter change notifications via Veilid).

    You know what that means! It's forking time!

    Please be encouraged to get in touch to work with me on this, let's make this happen! :)

    :boosts_ok_gay:

    #Plurality #Plural #Systemhood #FOSS #NoAI #OfflineFirst #Veilid #Tauri #Rust #JavaScript

  24. Как я сделал свой VPN-сервис в Telegram: бот, оплата, десктоп-клиент

    TL;DR: Собрал с нуля платный VPN SonicVPN: Telegram-бот с Mini App, оплата картой/СБП/Stars/криптой, выдача ключей VLESS+REALITY, свой десктоп-клиент под Windows. Всё на своём сервере, полный контроль над стеком и данными. От 83₽/мес. Бот: @bysonicvpn_bot . Зачем вообще это было нужно Хотелось не «взять подписку», а сделать свой сервис: свой сервер, свой код, свои правила. Плюс интересно было пройти весь цикл — от оплаты в боте до выдачи ключа и клиента в одну кнопку. Готовые VPN — это чёрный ящик: непонятно, кто и как логирует, как режут скорость, почему отваливается. Бесплатные часто собирают трафик или подсовывают рекламу. Я решил поднять свой стек: XRay на VPS, бот в Telegram для оплаты и выдачи ключей, десктоп-клиент под Windows. В итоге получился продукт, которым пользуюсь сам и который могу спокойно рекомендовать — без телеметрии, без посредников в цепочке оплаты, с одним ключом на все устройства. Соник, что ты сделал?

    habr.com/ru/articles/996738/

    #VPN #VLESS #REALITY #XRay #Telegram_Bot #Tauri #Rust #монетизация

  25. Введение в Yttri — Что это и почему это нужно?

    Устали прыгать между Jira, Confluence, Notion, Calendar и почтой? Я написал Yttri — мощный комбайн на Rust + Tauri для управления всей цифровой жизнью. Локальный AI, графовая база знаний, приватность и никакой облачной зависимости. Рассказываю, как объединить хаос в одну систему и почему Local-First победит.

    habr.com/ru/articles/996446/

    #Rust #Tauri #LocalFirst #Open_Source #AI #LLM #Knowledge_Management #Productivity

  26. Buenas!
    Otra vez al día con otro side project. Les presento #YAI: un editor de codigo orientado a NO HACER #vibecoding. (no es fork de VS code)

    codeberg.org/cristodcgomez/YAI

    #AI #opensource #tauri #rust #vue #vscode

  27. Buenas!
    Otra vez al día con otro side project. Les presento #YAI: un editor de codigo orientado a NO HACER #vibecoding. (no es fork de VS code)

    codeberg.org/cristodcgomez/YAI

    #AI #opensource #tauri #rust #vue #vscode

  28. Buenas!
    Otra vez al día con otro side project. Les presento #YAI: un editor de codigo orientado a NO HACER #vibecoding. (no es fork de VS code)

    codeberg.org/cristodcgomez/YAI

    #AI #opensource #tauri #rust #vue #vscode

  29. Buenas!
    Otra vez al día con otro side project. Les presento #YAI: un editor de codigo orientado a NO HACER #vibecoding. (no es fork de VS code)

    codeberg.org/cristodcgomez/YAI

    #AI #opensource #tauri #rust #vue #vscode

  30. Buenas!
    Otra vez al día con otro side project. Les presento #YAI: un editor de codigo orientado a NO HACER #vibecoding. (no es fork de VS code)

    codeberg.org/cristodcgomez/YAI

    #AI #opensource #tauri #rust #vue #vscode

  31. Is that Tauri, running a Roda app locally as a desktop app without exposing it to TCP?

    Almost! It's my experimental Ruby port of Tauri... Tokra!

    Write desktop software in Ruby, with an HTML and CSS interface. You can use JS frameworks, too. Plus: it's Rack-compatible!

    Rubygem: rubygems.org/gems/tokra
    Code: git.sr.ht/~kerrick/tokra/tree/

    #ruby #rust #tauri #tokra #desktop #software #programming #gui #webdev #html #css #javascript #FreeSoftware #OpenSource #PreRelease #PreAlpha #SeriouslyNotFinished

  32. Kawai-Focus 2.1: переезд на новый стек

    В данной статье я попытаюсь переписать часть приложения Kawai-Focus на стек: FastAPI + Vue.js + Tauri + Ionic . Также я соберу приложение только с экраном «Таймеры» под Linux в AppImage, которое подойдёт для большинства Linux-дистрибутивов. Реализация одного экрана не будет слишком долгим процессом, а финальная сборка приложения позволит оценить сложность и удобство полного цикла разработки. Эта cтатья не будет подробным гайдом, так как размер переписанного кода и его описание слишком велики для одной статьи. Однако я покажу часть кода проекта и расскажу о выбранном стеке, а также о трудностях и преимуществах, с которыми я столкнулся в процессе переписывания проекта. Я буду использовать часть кода старого проекта, который не касается Kivy и KivyMD, поэтому его душа не умрёт, а обновится. Заваривайте чай, доставайте вкусняшки — пора «старый стек превращать в удобрение для новых помидор»! 🍅

    habr.com/ru/articles/983652/

    #python3 #tauri #vuejs #nuitka #ionic #appimage #компиляция #linux

  33. 🔐 Ferrocrypt: a tiny, easy-to-use, highly secure multi-platform encryption tool written in Rust — with both a CLI and GUI apps (Tauri + Dioxus). Symmetric + hybrid encryption modes included.

    github.com/alexylon/ferrocrypt

  34. Dự án nhỏ tạo sách nói với giọng tùy chỉnh: dùng AI để nghe bất kỳ cuốn sách nào được đọc bởi giọng nói bạn chọn – ví dụ như Tolkien đọc chính tác phẩm của mình! Xây dựng bằng Tauri và API từ Eleven Labs/Minimax. Tương lai sẽ hỗ trợ chạy mô hình cục bộ và phân giọng cho từng nhân vật. Dành cho mục đích cá nhân, giáo dục. Tôn trọng bản quyền và quyền hình ảnh giọng nói. #Audiobook #AI #TextToSpeech #SáchNói #GiọngNóiAI #HobbyProject #Tauri #ElevenLabs

    reddit.com/r/selfhosted/commen

  35. 🦀🌱 We continue to work on ArkSync and the grid collision detection.

    We're building an environmental monitoring and regulation system.

    twitch.tv/indiedevcasts

    #indiedev #rustlang #tauri #leptos

  36. ✅ Module 0 基建篇完结!

    我们磨好了刀 (Environment),看好了图 (Architecture)。
    下一章节,正式开启 Module 1:AI 核心基础。

    我们要写第一行 AI 代码,让它真正开口说话。🤖

    #BibiGPT #FullStack #Tauri #Monorepo #IndieHacker

  37. O__o

    The #tauri + #yew example setup just works... now I think I will play a bit with this and see whether it gets me somewhere, if #dioxus does not work out of the box, it might be a viable alternative? 👀 🤔

  38. I’m learning Rust and have been building Ferrocrypt, a small cross‑platform encryption tool (Rust core lib + CLI + Dioxus GUI + Tauri GUI).

    It uses XChaCha20‑Poly1305 + Argon2id and a hybrid RSA+XChaCha20 mode with Reed–Solomon parity for header recovery.

    I’d really appreciate a code review (lib/CLI/GUI, error handling, idiomatic Rust).

    Repo: github.com/alexylon/Ferrocrypt

    #rust #rustlang #rustaceans #dioxus #tauri #cryptography #infosec

  39. Retour d'expérience sur une tentative de migration mitigée de Electron vers Tauri (2 technologies permettant de développer des applications de bureau avec les technos web).

    🔗 dolthub.com/blog/2025-11-13-el

    #electron #Tauri #web #comparatif #retourdexperience

  40. A few months ago I published a #rust crate that generates #typescript and #zod boilerplate from #tauri commands. I never thought anyone else would use it and opened my repo to see two pull requests and a few issues added to the tracker. There's obviously a few gaps due to messy development but it gets the job done.

    github.com/thwbh/tauri-typegen

  41. Kerminal là ứng dụng terminal & SSH manager miễn phí, nguồn mở, hỗ trợ đồng bộ nhiều thiết bị và mã hóa cấp doanh nghiệp. Được xây trên Vue 3 + Rust/Tauri, WebGL rendering, giúp ứng dụng nhẹ (15MB), mở nhanh (<1s) và ít tốn RAM. Bảo mật bằng AES-256-GCM, mật khẩu chủ, SFTP, ghi session asciicast, đồng bộ qua DB. Nhanh gọn, hiện đại, bảo mật—đáng thử. #Kerminal #OpenSource #SSH #Terminal #Sync #WebGL #Security #Tauri #Rust #Vue #SFTP #AsciiCast #DevTools #Tech #KerminalDev #SyncMultiDevice #Encry