ddlmanus/MacOptimizer: Open-Source macOS System Utility with SwiftUI

ddlmanus/MacOptimizer: Open-Source macOS System Utility with SwiftUI

Mac users accumulate digital debris fast. Developer environments, browser caches, abandoned app remnants, and forgotten large files quietly consume storage and degrade performance. Commercial cleanup tools exist, but many developers prefer transparent, auditable solutions they can inspect, modify, and extend. ddlmanus/MacOptimizer enters this space as an open-source alternative built with modern Apple technologies, offering eight functional modules through a native SwiftUI interface.

What is ddlmanus/MacOptimizer?

ddlmanus/MacOptimizer is a system optimization and application management tool designed specifically for macOS 13.0 (Ventura) and later. The project, maintained by GitHub user ddlmanus, has accumulated 1,540 stars and 106 forks as of its last commit on May 23, 2026. It is written primarily in Swift 5.9 and uses SwiftUI 4.0 for its interface, following an MVVM architecture pattern.

The tool distinguishes itself from command-line utilities like brew cleanup or rm -rf incantations by providing a graphical interface that reduces the risk of accidental system damage. It also goes beyond single-purpose scripts by consolidating multiple maintenance tasks—system monitoring, app uninstallation, junk cleaning, startup management, large file detection, trash management, deep cleaning, and file exploration—into one application.

The repository includes build scripts for both Apple Silicon (arm64) and Intel (x86_64) architectures, though the default configuration targets Apple Silicon. The project is released under the MIT License according to its README badge, though the GitHub API lists the license as "Not specified"—a minor discrepancy developers should note when evaluating compliance requirements.

Key Features

MacOptimizer organizes functionality into eight core modules, each addressing a specific maintenance domain:

Console (System Monitor) provides real-time CPU usage tracking, memory status display with used/available breakdowns, visual disk space percentage, and process management with one-click termination. This serves as a lightweight alternative to Activity Monitor for quick checks.

App Uninstaller performs smart scanning of installed applications and detects associated residual files across eight categories: Preferences, Application Support, Caches, Logs, Saved State, Containers, Launch Agents, and Crash Reports. It supports complete uninstallation or selective residual-only deletion, with safe "Move to Trash" recovery options.

Junk Cleaner targets system caches, application caches, browser caches (Safari, Chrome, Firefox), and log files with categorized display and selective cleaning. This addresses the common developer pain point of Docker^{↗ Bright Coding Blog}, Xcode, and browser cache accumulation.

System Optimizer manages startup items, provides one-click memory release, and applies system acceleration tweaks. The memory release function is particularly relevant for developers running memory-intensive local servers or containerized environments.

Large File Finder scans the home directory to locate space-consuming files with visual size display and direct cleanup actions. This complements command-line tools like du with a more navigable interface.

Trash Manager offers trash content browsing, space statistics, and one-click emptying—functionality that extends beyond macOS's native trash with size awareness.

Deep Clean performs orphaned file scanning to find residuals from previously uninstalled apps, with automatic exclusion of Apple system files to prevent accidental deletion. It categorizes findings by type and supports selective cleanup with trash-based recovery.

File Explorer provides full disk browsing with breadcrumb navigation, path input supporting ~ expansion, file operations (create, rename, delete), hidden file toggling, and Terminal integration for the current directory.

Multi-Language Support (added in version 2.2.0) provides English and Chinese localization with persistent preference storage and full UI coverage.

Use Cases

Development Environment Maintenance Developers frequently install and uninstall tools via Homebrew, npm, Docker, and direct downloads. MacOptimizer's App Uninstaller and Deep Clean modules identify leftover configuration files and caches that manual uninstallation misses, particularly for apps that scatter data across ~/Library/Application Support, ~/Library/Caches, and ~/Library/Containers.

Pre-Release Storage Recovery Before shipping builds or creating VM snapshots, reclaiming disk space matters. The Large File Finder identifies unexpected space consumers—old Xcode archives, forgotten downloads, or accumulated Docker images—while the Junk Cleaner targets cache directories that grow unbounded during development cycles.

System Performance Troubleshooting When macOS feels sluggish during local development, the Console module provides immediate visibility into CPU and memory pressure. The System Optimizer's startup item management helps identify applications that unnecessarily consume resources at boot, and the memory release function offers a quicker alternative to restarting when swap pressure builds.

Shared Machine Hygiene On team laptops or CI/CD Mac runners that see varied usage, the Trash Manager and Deep Clean modules provide standardized cleanup procedures that reduce the risk of manual rm errors. The File Explorer's hidden file visibility and Terminal integration support administrative tasks without leaving the GUI.

Cross-Platform Team Localization Teams with both English and Chinese-speaking members benefit from the persistent language switching, reducing friction in shared documentation and support scenarios.

Installation & Setup

MacOptimizer supports three installation methods with distinct trade-offs.

Homebrew Installation (Recommended)

The README documents a Homebrew tap for streamlined installation:

# Add the custom tap and install via Cask
brew tap ddlmanus/macoptimizer
brew install --cask macoptimizer

Alternatively, install from a local cask file if you have cloned the repository:

brew install --cask ./homebrew/macoptimizer.rb

Pre-built DMG Download

For users preferring direct distribution, GitHub Releases provides architecture-specific DMGs:

• Apple Silicon (M1/M2/M3/M4): MacOptimizer_vX.X.X_AppleSilicon.dmg
• Intel: MacOptimizer_vX.X.X_Intel.dmg

Download from GitHub Releases and mount the DMG normally.

Build from Source

Building requires macOS 13.0+, Command Line Tools (full Xcode not required), and appropriate architecture support:

# 1. Clone repository
git clone https://github.com/ddlmanus/MacOptimizer.git
cd MacOptimizer

# 2. Run build script
chmod +x build.sh
./build.sh

# 3. Launch application
open build/Mac优化大师.app

Intel Mac Modification: The default build.sh targets arm64-apple-macos13.0. For Intel machines, edit the script:

# Change this line in build.sh
-target arm64-apple-macos13.0
# To this line
-target x86_64-apple-macos13.0

The build produces Mac优化大师.app (Chinese name) in the build/ directory. The repository includes release_package.sh for creating distributable packages.

Real Code Examples

The README provides limited explicit code snippets, reflecting the project's application nature rather than library usage. The following examples are reproduced directly from documentation:

Build Script Architecture Target

The build.sh script demonstrates Swift compiler invocation with platform targeting:

# Default Apple Silicon target
-target arm64-apple-macos13.0

# Intel alternative
-target x86_64-apple-macos13.0

This explicit architecture specification matters for universal binary creation and CI/CD pipelines where build machines may differ from target deployment hardware.

Project Structure Reference

The documented directory organization reveals the modular SwiftUI implementation:

MacOptimizer/
├── AppUninstaller/              # Source code root
│   ├── AppUninstallerApp.swift  # App entry point
│   ├── ContentView.swift        # Main view composition
│   ├── NavigationSidebar.swift  # Sidebar navigation
│   ├── LocalizationManager.swift # i18n coordination
│   ├── Models.swift             # Shared data models
│   ├── Styles.swift             # Global SwiftUI styling
│   │
│   ├── MonitorView.swift        # Console module UI
│   ├── SystemMonitorService.swift # CPU/memory/disk backend
│   ├── ProcessService.swift     # Process enumeration/termination
│   │
│   ├── AppScanner.swift         # App detection logic
│   ├── AppDetailView.swift      # Uninstaller interface
│   ├── ResidualFileScanner.swift # Leftover file detection
│   ├── FileRemover.swift        # Safe deletion implementation
│   │
│   ├── JunkCleaner.swift        # Cache/log identification
│   ├── JunkCleanerView.swift    # Cleanup UI
│   │
│   ├── SystemOptimizer.swift    # Startup/memory optimization
│   ├── OptimizerView.swift      # System tuning interface
│   │
│   ├── LargeFileScanner.swift   # Size-based file search
│   ├── LargeFileView.swift      # Results presentation
│   │
│   ├── TrashView.swift          # Trash browsing UI
│   ├── DiskSpaceManager.swift   # Storage calculations
│   ├── DiskUsageView.swift      # Visualization
│   │
│   ├── DeepCleanScanner.swift   # Orphaned file detection
│   ├── DeepCleanView.swift      # Deep clean interface
│   │
│   ├── FileExplorerService.swift # Directory traversal
│   ├── FileExplorerView.swift   # File manager UI
│   │
│   ├── Info.plist
│   └── AppIcon.icns
│
├── build.sh                     # Compilation script
├── release_package.sh           # Distribution packaging
└── README.md

This structure demonstrates MVVM separation with *Service.swift files handling business logic and *View.swift files managing presentation. The naming inconsistency (AppUninstaller/ containing all modules) suggests evolutionary development where the project scope expanded beyond its original uninstaller focus.

Homebrew Cask Local Installation

For custom or offline installation scenarios:

brew install --cask ./homebrew/macoptimizer.rb

This pattern is useful for [INTERNAL_LINK: internal-tool-distribution] scenarios where teams maintain forked or patched versions.

Advanced Usage & Best Practices

Based on the tool's documented design, several practices maximize safety and effectiveness:

Prefer "Move to Trash" over immediate deletion. The README explicitly recommends this workflow: move files to trash first, verify system stability, then empty trash. This is especially important for Deep Clean operations where "orphaned" files might still be referenced by infrequently used applications.

Verify architecture before distribution. The default build.sh produces Apple Silicon binaries. Teams with mixed hardware must maintain separate build pipelines or create universal binaries by combining both architectures—an enhancement not currently documented.

Understand localization scope. While version 2.2.0 claims "full coverage," developers extending the tool should verify LocalizationManager.swift handles new string additions. The persistent preference storage suggests UserDefaults or equivalent, but custom extensions should test language switching edge cases.

Monitor Console during heavy operations. The System Monitor module provides real-time feedback during cleanup operations. Running it concurrently with large deletions helps identify if cleanup processes themselves cause resource contention.

Review startup items before disabling. The System Optimizer's startup management requires understanding which background processes support development workflows (Docker Desktop, VPN clients, sync tools) versus true bloat.

Comparison with Alternatives

MacOptimizer occupies a middle ground: more accessible than raw terminal commands, more transparent than commercial utilities, and more integrated than single-purpose open-source tools. Its SwiftUI implementation and MVVM structure also make it more approachable for iOS/macOS developers wanting to contribute or fork.

FAQ

Is ddlmanus/MacOptimizer free? Yes, the project is open-source under MIT License per README badge. No pricing or subscription is mentioned.

Does it work on Intel Macs? Yes, but you must modify build.sh to use -target x86_64-apple-macos13.0 instead of the default arm64 target.

What macOS version is required? macOS 13.0 (Ventura) or later, due to SwiftUI 4.0 dependencies.

Is it safe to use on production machines? The README includes a disclaimer recommending backups and trash-based deletion first. The Deep Clean module excludes Apple system files automatically, but user data should always be backed up.

Can I contribute to development? Yes, the project accepts pull requests. The repository includes standard GitHub contribution workflow documentation.

Why does the built app have a Chinese name? build/Mac优化大师.app reflects the project's bilingual nature. The English name "MacOptimizer" is used in repository branding.

Are there known limitations? The roadmap indicates scheduled cleanup, menu bar widget, auto-updates, duplicate file finder, and privacy protection features are not yet implemented.

Conclusion

ddlmanus/MacOptimizer serves developers and power users who want transparent, auditable macOS maintenance without commercial tool costs or command-line complexity. Its SwiftUI-based interface and modular architecture make it particularly relevant for Apple platform developers who can leverage their existing Swift knowledge to extend functionality.

The tool is best suited for: individual developers managing personal workstations, small teams needing consistent cleanup procedures, and anyone preferring open-source infrastructure they can inspect and modify. It is less ideal for users wanting fully automated maintenance or enterprise deployment with centralized management.

With 1,540 stars and active development through May 2026, the project demonstrates sustained community interest. The bilingual support and architecture flexibility suggest thoughtful attention to real-world deployment scenarios.

Ready to clean up your macOS environment? Explore the source, build locally, or install via Homebrew at https://github.com/ddlmanus/MacOptimizer.