Shedi

Product Introduction

1. Definition: Shedi is a native macOS utility application designed specifically for developers and technical users. It functions as a specialized disk space analyzer and cleaner, targeting the residual files left by development tools and package managers.
2. Core Value Proposition: Shedi exists to solve the problem of "disk space bloat" on Macs caused by developer toolchains. Its primary value is providing transparent, user-controlled cleanup of Xcode caches, Docker images, node_modules folders, and other development artifacts, differentiating itself from generic "magic button" cleaners by explaining every item and prioritizing safety.

Main Features

1. Intelligent, Tool-Aware Scanning: Shedi performs a rapid (approx. 10-second) scan of known directories used by over 20 development tools and systems, including npm, Yarn, pnpm, Homebrew, Cargo, pip, CocoaPods, Xcode (DerivedData, Simulators, Archives), Docker, and various build caches (.next, Pods, .venv, target). It categorizes findings (e.g., App caches, Package caches, node_modules) and calculates their size impact.
2. Transparent Item Explanation & Safety Categorization: This is Shedi's core feature. Every discovered file or folder is clearly labeled with: its purpose (e.g., "npm's download cache"), what tool created it, and a critical "Comes back" status (Yes/No). Items are further tagged as Safe (auto-selected, refillable caches), Check first (like Puppeteer browsers or old projects), or Your files (never auto-selected).
3. User-Controlled Cleanup with Trash Workflow: No automatic deletion. Users manually select items from the detailed list. The cleanup process first moves all selected, standard files to the macOS Trash, allowing for easy recovery. For items that cannot use the Trash (e.g., Docker images, broken simulator runtimes), Shedi explicitly names the item and uses the native tool's command (like docker image rm) for removal, with user confirmation.

Problems Solved

1. Pain Point: Developers and power users accumulate gigabytes of "digital debris" from build systems, package managers, and development environments, which is tedious to find and risky to delete manually. Generic cleaners often misidentify these files or clear transient caches that refill immediately, providing no lasting value.
2. Target Audience: The primary user personas are software developers (especially those using Node.js, Swift, Python, Rust, Go), DevOps engineers using Docker, data scientists with Python environments, and technical Mac power users who run multiple development tools. It specifically targets users who understand the tools creating the files.
3. Use Cases: Essential for: 1) Reclaiming tens of gigabytes after completing or archiving large projects (Xcode builds, node_modules). 2) Periodically cleaning Docker disk usage without memorizing CLI commands. 3) Safely removing old simulator runtimes and device support files from Xcode. 4) Uninstalling applications completely by also removing their leftover Library files. 5) Gaining visibility into what is consuming space across various toolchains in one unified interface.

Unique Advantages

1. Strengths & Limitations (Pros & Cons):

   • Pros: Unmatched transparency and user control; deep understanding of developer toolchains; safe "Trash-first" workflow; one-time purchase with lifetime updates; small, native Swift app (5.3 MB); no telemetry or data collection; created by an independent developer with direct support.
   • Cons: Currently requires a manual "Open Anyway" step due to pending Apple notarization (resolves Nov 2026); requires macOS 15 or later, excluding users on older OS versions; requires Full Disk Access for complete scanning (optional but recommended); targets a niche (developers) rather than general users.

2. Key Alternatives & Differentiation:

   • CleanMyMac X (MacPaw): A generalist, subscription-based cleaner with a "one-click" approach. Shedi differentiates by being tool-specific, transparent, non-subscription, and not making generic "speed boost" claims, instead focusing on permanent space recovery from development artifacts.
   • DevCleaner (Open Source): A free, open-source tool focused on Xcode cleanup. Shedi offers a broader scope (20+ tools vs. primarily Xcode), a more polished and explanatory UI, safety categorization, and the Trash workflow, justifying its paid price.
   • Manual CLI Commands (rm -rf, docker system prune, npm cache clean): The free alternative. Shedi provides a unified, visual interface that saves time looking up dozens of commands and paths, reduces risk of accidental deletion, and offers the safety net of the Trash.

Frequently Asked Questions (FAQ)

1. Is Shedi safe to use? Will it delete my important project files? Yes, Shedi is designed for safety. It never deletes anything until you explicitly press "Clean," and standard files are moved to the Trash first for recovery. It categorizes items, and your personal project files are marked "Your files" and are never pre-selected for deletion. It does not follow symbolic links or touch files of running applications.

2. What makes Shedi better than other Mac cleaner apps like CleanMyMac? Shedi is built specifically for developers, while most cleaners are for general users. It doesn't just clear temporary system caches; it finds persistent build outputs and dependencies from tools like Xcode and Docker. It explains what each item is and if it will come back, providing education and control rather than a opaque "magic clean" button.

3. Does Shedi require an internet connection or collect my data? No. File names and paths never leave your Mac. The website sets no cookies. Only three online connections occur: the initial license validation with Lemon Squeezy, optional update checks, and anonymous usage counts (which can be disabled). The scan and analysis happen entirely locally on your machine.

4. I use Docker and Xcode. How does Shedi handle deleting their files safely? For Docker images and containers, Shedi uses the official docker CLI commands (e.g., docker image rm) after clearly telling you which image it will remove. For Xcode components like Simulators, it uses Xcode's own command-line tools. This ensures cleanup is done in the way the tools expect, minimizing risk.

5. What happens after I clean something? Won't the cache just come back? Shedi is transparent about this. It labels whether an item "Comes back: yes" or "no." Package manager caches (npm, Homebrew) will refill as needed, which is fine. The key value is removing persistent, large items that don't come back automatically, like node_modules from deleted projects, old Xcode simulator runtimes, or dormant Docker images, which permanently free up space.