Stop letting missing localization keys break your production UI. Xcode won't warn you if a key is missing, and a single misplaced semicolon in a massive file can break your build without pointing to the error. Orphan Guard 2 is a lightweight (<30MB) native macOS utility that scans your Xcode workspace to pinpoint missing keys and syntax bugs instantly. No framework installation, no external Swift Packages—just total control over your localized strings before you ship.
Hey Product Hunt! 👋
I’m the developer behind Orphan Guard 2.
If you build apps for Apple platforms, you know the nightmare: you’re managing thousands of lines across local language files, someone forgets a single ending semicolon or an equal sign, and Xcode leaves you completely on your own to dig through the haystack. Even worse, missing keys slip into production, showing raw, ugly code strings to your users.
I built Orphan Guard 2 because I wanted a lightning-fast, zero-bloat solution. It's a completely standalone macOS desktop utility under 30 MB. You don't have to install unverified Swift Packages or alter your system environment just to check your code. It deeply parses your SwiftUI Views, UIKit, and Cocoa files, and strictly flags the exact line causing a syntax error.
Report
Congrats on the launch. As someone who's wasted hours hunting down a missing key, this looks like a lifesaver. One idea: could you add support for custom Localizable.strings file paths, so it works with projects that keep translations in subdirectories like Resources/Localization/en.lproj instead of the standard layout?
Quick Sub 2: Video Subtitling
Congrats on the launch. As someone who's wasted hours hunting down a missing key, this looks like a lifesaver. One idea: could you add support for custom Localizable.strings file paths, so it works with projects that keep translations in subdirectories like Resources/Localization/en.lproj instead of the standard layout?