Show HN: CompressX, my FFmpeg wrapper for macOS

Original Article ↗ Hacker News Discussion ↗

Overview & Reception

  • Many commenters praise the app’s clean macOS-native UI, good polish, and automation features (e.g., folder watching, Raycast integration).
  • Several people say it’s a good purchase and well-suited for non-technical users or relatives who can’t handle ffmpeg CLI.
  • Others view it as “just” a simple frontend and downplay its novelty.

Use Cases vs Existing Tools (HandBrake, CLI, other UIs)

  • HandBrake is repeatedly mentioned as the main existing alternative.
    • Some say HandBrake’s presets are enough and see little reason to switch.
    • Others argue HandBrake’s UI and settings are overwhelming for beginners, while this app intentionally shows only a few high-level controls.
  • Some note that ChatGPT can generate ffmpeg commands, further reducing the need for a GUI for power users.
  • Consensus: advanced/CLI users may not need it; casual or design-focused users might value the streamlined workflow.

Licensing, Open Source, and Upstream Support

  • Discussion on FFmpeg’s GPL/LGPL licensing:
    • The app does not bundle FFmpeg; users install and link it separately, which multiple commenters say avoids GPL obligations for the app itself.
  • Some argue that, in the spirit of GPL and commons, the app “should” be open source.
  • The developer reports donating 10% of recent revenue to FFmpeg, which several see as responsible behavior.

Telemetry, Privacy, and GDPR

  • The website shows live stats (files/GB compressed), powered by telemetry from the desktop app.
  • Commenters raise concerns about:
    • Lack of clear disclosure in the ToS/privacy policy.
    • Non-optional tracking and potential GDPR non-compliance.
  • In response, the developer commits to:
    • Adding in-app opt-in/opt-out for anonymous telemetry.
    • Updating the site and policies, and removing the intrusive stats popup.

macOS Ecosystem, UI Quality & Electron

  • Large subthread on why many polished indie tools target macOS:
    • macOS users are perceived as more willing to pay and more design-conscious.
    • Apple’s AppKit/UIKit and HIGs make it easier to build consistent, accessible UIs quickly.
  • Heated debate over Electron:
    • Some say it’s perfect for cross-platform GUIs like this; others criticize its bloat, non-native feel, and poor UX polish.
    • One example of an Electron-based ffmpeg tool (LosslessCut) is mentioned as specialized for lossless trimming.

Technical Questions & Capabilities

  • App currently calls ffmpeg via CLI, not via libraries.
  • Uses H.264 for many recompression cases; examples of up to ~90% size reduction from unoptimized sources are cited, but typical savings are acknowledged as likely lower.
  • Current version does not support lossless trimming without re-encoding.
  • Questions raised about:
    • Lack of explicit codec selection in the UI and resulting compatibility concerns (e.g., TVs without HEVC).
    • Meaning of quality settings and CPU vs efficiency trade-offs.
  • Comparisons vs AVFoundation note FFmpeg’s broader format support; some discussion of encoder quality (x264/x265 vs OS encoders, Apple AAC).

Marketing & Monetization

  • Marketing strategy: build an audience on Twitter, share development and SEO learnings publicly, then launch on Product Hunt and other directories.
  • Several commenters ask about replicating this approach for their own products.
  • Pricing copy drew scrutiny: a “50% savings” claim for a two-license bundle was called misleading; it was updated to a fixed-dollar savings.

General Reflections on Value

  • One recurring theme: the real value of this product is not new algorithms but UX work that makes a powerful open-source tool accessible.
  • Some developers see selling such a frontend as fair entrepreneurship; others resent profiting atop free software without full open-sourcing, despite the donation.