Overview
PlayStatus is a native SwiftUI macOS menu bar app for controlling Apple Music and Spotify without living in a full desktop window all day. The current generation of the app is a full SwiftUI relaunch with a richer now-playing surface, better onboarding, customizable display themes, provider-aware search, lyrics and credits, play history, Last.fm scrobbling, Shortcuts support, a detached floating player, and a cleaner settings flow.
PlayStatus is built on open-source principles to guarantee security, privacy, and full reproducibility. All sensitive data transformations run locally on your hardware with zero telemetry or unexpected cloud dependencies.
Key Technical Features & Capabilities
The old AppKit utility-style player has been replaced with a layered SwiftUI player that supports regular, mini, and detached modes.: Streamlined desktop functionality optimized for macOS and Windows.
New users get a guided walkthrough, and existing users can replay the full tour or the shorter "What's New" tour at any time.: Streamlined desktop functionality optimized for macOS and Windows.
Lyrics, credits, and provider-aware search now live inside the main player instead of feeling like separate utility flows.: Streamlined desktop functionality optimized for macOS and Windows.
Display tuning is much deeper: menu bar text modes, detached window sizing, theme presets, animated artwork, artwork motion styles, and progress-strip options all live in Settings.
The app is more efficient when closed: media caches, onboarding previews, and heavy Settings surfaces can unload when they are not visible.
PlayStatus now remembers what you played, scrobbles it to Last.fm, and can be driven from Shortcuts, Spotlight, or any launcher that can open a URL.: Streamlined desktop functionality optimized for macOS and Windows.
Architecture & Technology Stack
Frameworks & UI Runtime: SwiftUI / AppKit
Build Systems & Tooling: Xcode / Node.js / Cargo
Supported Platforms: macOS 12.0+ (Apple Silicon M1-M4 & Intel x86_64), Windows 10/11 x64, Linux
System Requirements
| Specification | Minimum Requirement | Recommended Specification |
|---|
| Operating System | macOS 12.0 Monterey / Windows 10 x64 | macOS 14.0+ Sonoma / Windows 11 x64 |
| Processor Architecture | Apple Silicon (M1+) or Intel Core i5 x64 | Apple Silicon Unified Memory (M2/M3/M4) |
| Memory (RAM) | 4 GB Unified RAM | 8 GB+ High-Speed RAM |
| Storage Space | 300 MB available local disk space | 1 GB+ SSD storage |
| GPU Acceleration | Metal 2 / DirectX 12 compatible | Apple Neural Engine / Vulkan capable |
Installation & Setup Guide
macOS Installation (Recommended)
1Download the verified .dmg release installer directly from CookApps.
2Open the disk image and drag PlayStatus.app into your /Applications folder.
3Launch PlayStatus via Spotlight (Cmd + Space) or Launchpad.
Alternatively, install using Homebrew if available:
brew install --cask nbolar/playstatus/playstatus
Windows Installation
1Download the official installer package (.exe / .msi).
2Run the executable and follow the setup wizard.
3Launch PlayStatus from the Start Menu or desktop shortcut.
Building from Source (Development Setup)
git clone https://github.com/user-attachments/assets.git
cd assets
pnpm install || cargo build --release
pnpm run build
How to Use & Workflow
1Application Launch & Workspace: Open PlayStatus to load the responsive native workspace.
2Configuration & Preferences: Press Cmd + , (macOS) or Ctrl + , (Windows) to configure hardware acceleration, custom directories, and display themes.
3Primary Operation: Drag-and-drop source files or input parameters directly into the central window.
4Execution & Export: Initiate the processing pipeline and verify output files saved directly to your chosen local directory.
Troubleshooting & Common Issues
Problem: macOS Gatekeeper displays *"App is damaged and can't be opened"* or unnotarized developer notice.
Root Cause: macOS quarantine flag set on binaries downloaded outside the Mac App Store.
Resolution: Open Terminal and run:
xattr -cr /Applications/PlayStatus.app
Alternatively, navigate to System Settings > Privacy & Security and select Open Anyway.
Problem: High memory consumption during batch processing operations.
Root Cause: Large media buffers retaining uncompressed state.
Resolution: Adjust batch concurrency in settings or process assets in focused batches.