r/tauri

Image 1 — Robintuk: A beautiful music player built with Tauri
Image 2 — Robintuk: A beautiful music player built with Tauri
Image 3 — Robintuk: A beautiful music player built with Tauri
▲ 6 r/tauri

Robintuk: A beautiful music player built with Tauri

Over the past few months, I've been working on my first Tauri project. I enjoyed listening to music while I studied or coded, but some features were missing in the software I saw online. So I started to build my own with a focus on showing off the nice artwork albums have.

Main Features:

  • Play most music formats (mp3, flac, ogg, aiff, m4a)
  • Custom playlist artwork (including animated images)
  • Customize the look with multiple color themes
  • View last 100 played song history
  • Search to find your music faster
  • Fast scans to add your music quickly (~5000 songs per minute)
  • Backup, Restore, or Reset your music database and images
  • Use m3u/m3u8 files to import playlists from other apps or export your playlists for safe keeping
  • Download song lyrics using LRCLIB

It's been a fun learning experience, and I think Tauri is what I'm going to use on other projects.

u/VulshokBersrker — 9 hours ago
tauri-pilot: interactive testing CLI for Tauri v2 apps (Playwright alternative for WebKitGTK)
▲ 6 r/ClaudeAI+1 crossposts

tauri-pilot: interactive testing CLI for Tauri v2 apps (Playwright alternative for WebKitGTK)

Hey everyone,

If you've ever attempted to automate UI testing on a Tauri app on Linux, you may have encountered the same obstacle: Playwright doesn't support WebKitGTK.

I built tauri-pilot to solve this. It's a lightweight CLI + plugin that lets you inspect, interact with, and debug your Tauri v2 app in real-time.

Setup is minimal:

# src-tauri/Cargo.toml
[dependencies]
tauri-plugin-pilot = { git = "https://github.com/mpiton/tauri-pilot" }

#[cfg(debug_assertions)]
{
    builder = builder.plugin(tauri_plugin_pilot::init());
}

Then from your terminal:

$ tauri-pilot ping
ok (3ms)

$ tauri-pilot snapshot -i
- heading "Settings" [ref=e1]
- textbox "API Key" [ref=e2] value=""
- button "Save" [ref=e3]

$ tauri-pilot fill @e2 "sk-test-123"
ok

$ tauri-pilot click @e3
ok

What you can do:

• Inspect the accessibility tree with element refs
• Click, fill, type, press, select, check, scroll
• Get element text/html/value/attributes
• Capture screenshots
• Wait for elements to appear/disappear
• Execute arbitrary JS or call Tauri IPC commands
• Capture console logs and network requests
• Diff snapshots to see what changed

It's also designed to work with AI coding agents (Claude Code, etc.) the output format is optimized for LLM parsing.

The plugin runs only in debug builds, so there is zero overhead in production.

GitHub: https://github.com/mpiton/tauri-pilot
License: MIT | Platform: Linux (macOS/Windows planned)

Curious to hear what the Tauri community thinks. What features would be most useful for your workflow?
u/Famous_Drive_9010 — 15 hours ago
Week