Yoto-UP

A toolbox for managing Yoto content from the command line, a terminal UI, or a GUI.

🌐 https://github.com/xkjq/yoto-up

User information

A multipurpose set of command-line, terminal UI, and graphical tools for managing your Yoto content.

Features include content organization, device management, and easy integration with Yoto services.

Features

- Integration with Yoto Services: Simplified access to Yoto's API and services.
- Content Organization: Easily manage and organize your Yoto cards and files.
# πŸš€ Yoto-UP

A toolbox for managing Yoto content from the command line, a terminal UI, or a GUI.

Yoto-UP helps with content organization, device management, icon handling, and easy integration with Yoto services.

✨ Highlights

- πŸ”— Integration with Yoto Services β€” simplified access to the Yoto API and helper utilities
- πŸ—‚οΈ Playlist/Card organization β€” chapters, tracks and metadata management
- 🎡 Track titles, keys and durations
- πŸ–ΌοΈ Icon management β€” autoselect or pick icons via search
- πŸ–ŒοΈ Cover management β€” set, import, or auto-search cover art; embed into card metadata
- πŸ“€ Export / πŸ“₯ Import cards
- πŸ–₯️ Interfaces β€” CLI, TUI (terminal UI) and a small graphical UI

For full docs and examples see the project site.

Technical information

Command Line First

Leveraging Python libraries like Typer, Rich, and Textual for a vibrant, user-friendly command-line experience. Creating and managing cards with text has never been easier or more colorful 🌈.

Graphical Interface Included

For tasks better suited to a visual workflow, Yoto-UP also provides a GUI built with Flet, making advanced operations accessible and sometimes even intuitive.

Source code available on GitHub.

Data storage

The application features no telemetry.

Application data is all stored on the running device.

Some features require API/web requests to external services (including the Yoto, iTunes and YotoIcons) which may log requests and data sent.

See the project documentation for a comprehensive list of why each service is used.

3