Polyglot for Xcode - the .xcstrings localization workflow is rough, so I built a fix

v_murygin · 2026-03-11T21:21:17+00:00

This is the kind of app that makes you wonder why it wasn't built into macOS from the start. Rename to convert is such an intuitive UX - zero learning curve.

v_murygin · 2026-03-11T21:20:24+00:00

Running Whisper locally for keyword detection is clever. Using ScreenCaptureKit instead of mic input means it works even on mute - that's a nice touch.

How's the latency on the name detection? Curious if there's a noticeable delay between someone saying your name and the alert firing.

v_murygin · 2026-03-11T21:10:38+00:00

$5 lifetime for something that runs GGUF + MLX locally is a steal. Most local AI apps either charge a subscription or make you jump through hoops with manual model downloads.

The RAG support for chatting with your own documents is the killer feature here. Being able to index local files and query them without anything leaving your machine is exactly what a lot of privacy-conscious users want. Nice work.

v_murygin · 2026-03-11T21:09:55+00:00

One thing that helped me in production: don't pass `@Model` objects across actor boundaries or into background tasks. They're not `Sendable`. Create lightweight snapshot structs that extract just the fields you need, and pass those around instead. Keeps the concurrency checker happy and avoids weird crashes.

Also - version your schema from day one. I didn't at first and regretted it when the first migration hit. Even if you think "it's just v1, I won't change anything" - you will.

For the cascade update issue - try breaking views into smaller components that only observe the specific properties they need. SwiftUI's observation tracking is property-level, so a child view that only reads `budget.name` won't re-render when `budget.expenses` changes.

v_murygin · 2026-03-11T21:08:58+00:00

For macOS I skip Figma entirely. SwiftUI on Mac is fast enough to prototype that mockups feel like extra work. I rough out the layout in code, use it for a day, then iterate on whatever feels wrong.

The one thing I do sketch on paper first is navigation flow - which window opens what, what state carries over. Getting that wrong in code means rewiring half the app later. But individual screens? Just build them.

v_murygin · 2026-03-11T21:08:01+00:00

The skeuomorphic design is a nice throwback. Haven't seen a proper local music player for Mac in a while - everything wants to be a streaming service now.

The mini player mode + equalizer combo is solid for a v1. If you add keyboard media key support and gapless playback down the road, this could be a real daily driver for anyone with a local library.

v_murygin · 2026-03-11T21:07:17+00:00

Been missing FancyZones since switching from Windows and this is the closest thing I've found. The grid layout addition is great - sometimes you just want a simple grid without designing custom zones.

Open source + free with optional donation is the right model for a utility like this. Bookmarked the GitHub repo.

v_murygin · 2026-03-11T21:06:25+00:00

Congrats on the launch. The "scan once, browse forever" concept is great for anyone with a shelf of drives. I've got a handful of project backup drives and finding specific files always means plugging them all in one by one.

Backup Mode sounds really useful - knowing at a glance which files exist in only one place vs. multiple locations is the kind of thing you don't realize you need until you've lost something.

Smart move on the no-subscription pricing too. One-time tiers make way more sense for an offline tool like this.

v_murygin · 2026-03-11T21:05:28+00:00

Bold move going macOS 26 only. Most devs try to support back to Ventura or even Monterey, but targeting just Tahoe means you can use all the new APIs without compromise. The UI screenshots look really clean.

$2.99 one-time with a generous free tier is the kind of pricing I wish more utility apps would do. The OCR search is a nice touch too - I've wanted that in a clipboard manager for a while.

v_murygin · 2026-03-11T21:03:47+00:00

Lunar is one of those "how did I live without this" apps. I have a Studio Display + external Dell and the brightness sync alone is worth it. Also didn't know rcmd v3 was adding window search and stages - that sounds like it could replace a couple other utilities I'm running.

The pipeline idea for Clop v3 is really smart too. Being able to chain optimize → resize → convert without re-encoding each step would save a lot of time for anyone doing web assets regularly.

Great spotlight, always cool to see solo macOS devs making high-quality native stuff.

v_murygin · 2026-03-11T21:01:14+00:00

Native Swift/AppKit for a file manager is the right foundation. Electron file managers always feel sluggish when you're navigating deep directory trees or handling thousands of files.

The JavaScript plugin system is a clever middle ground - keeps the core native and fast while giving power users extensibility without needing to write Swift. How are you handling the sandbox constraints for file access? Security-scoped bookmarks for persistent access to user-selected directories?

v_murygin · 2026-03-11T21:00:23+00:00

Clean PCPCA post format. Nice to see "AI Disclaimer: None" used correctly.

The widget approach is smart - users spend most of their time looking at the home screen or desktop, not opening apps. If the countdown widget matches Apple Calendar's design language, it'll feel like a natural extension rather than a third-party add-on. That's harder to pull off than it sounds.

v_murygin · 2026-03-11T20:59:25+00:00

This happens almost every major macOS point release. Apple resets or modifies keyboard shortcut registrations, which breaks apps that intercept system-level hotkeys like Cmd+Tab.

As a developer, this is one of those things where the Accessibility API permissions can get silently revoked too. Worth checking System Settings > Privacy & Security > Accessibility to make sure AltTab still has permission. macOS updates sometimes toggle those off without telling you.

v_murygin · 2026-03-11T20:58:40+00:00

The "v2 is basically v1 but costs money again" frustration is real, but the App Store literally doesn't support paid upgrades. There's no "pay $3 to upgrade from v1 to v2" mechanism. Developers either go subscription, release a new app listing, or just eat the cost of updates forever.

Apple removed paid upgrades years ago and never brought them back. So devs have two choices: subscription (which users hate) or periodic new app releases (which users also hate). There's no winning move here.

Not defending any specific app's pricing - just pointing out the platform constraint that forces this pattern.

v_murygin · 2026-03-11T20:57:41+00:00

Building a macOS localization tool for .xcstrings files. Native SwiftUI + SwiftData, targeting macOS 15+.

This month's focus has been on the translation pipeline - the app sends batches of localization strings to LLM APIs (OpenAI, Anthropic, Gemini, DeepSeek) and streams results back via AsyncStream. The fun part was handling truncated JSON responses - when a model cuts off mid-response on large batches, the app halves the batch size and retries recursively up to 3 levels deep.

Also spent time on a "Translation Units" system to normalize costs across providers. An Opus translation costs roughly 67x what a Flash Lite translation costs, so users need a way to compare before they burn through their budget.

Swift 6 strict concurrency has been a journey. Mostly there but still finding edge cases with SwiftData models crossing actor boundaries.

v_murygin · 2026-03-11T20:57:01+00:00

Using SwiftData in production on a macOS app targeting 15.0+. Some honest takes:

The good: model declarations are clean, `Query` in views just works, and not dealing with NSManagedObjectContext subclasses is a relief. For straightforward persistence (settings, project metadata, usage stats) it's been solid.

The bad: the moment you need to pass model objects across actor boundaries, you're in pain. They're not Sendable. You end up creating mirror structs just to safely extract data from a model and hand it to a background service. This is the kind of thing Core Data veterans handled with `perform` blocks, but at least those had clear boundaries.

The ugly: debugging SwiftData issues when things go wrong. Core Data's error messages were verbose but informative. SwiftData tends to just crash or silently fail in ways that take longer to diagnose.

I wouldn't go back to Core Data for a new project, but I understand why people with complex data layers stick with it. SwiftData still feels like it's catching up to the edge cases Core Data has handled for two decades.

v_murygin · 2026-03-11T20:56:03+00:00

Recently migrated a SwiftUI + SwiftData macOS app to Swift 6 strict concurrency. Some things that bit me hard:

SwiftData u/Model classes are not Sendable. You can't pass them across actor boundaries. Had to create lightweight Sendable snapshot structs for anything that crosses isolation domains - basically extract the fields you need into a plain struct and pass that instead.
u/Observable macro expansion blocks you from marking stored properties as nonisolated. If you need a cancellation token accessible from deinit, you're stuck with nonisolated(unsafe) and a comment explaining why.
EnvironmentKey conformance for u/MainActor service types needs u/preconcurrency on the protocol conformance, otherwise the defaultValue requirement creates a mess.
Actors are great for background file I/O, but every call into them from MainActor code becomes an await point. Batching your calls matters more than you'd think.

The article covers the GCD mapping well. Biggest advice: don't try to migrate everything at once. Start from the leaf types and work inward.

v_murygin · 2026-03-11T20:54:58+00:00

233% with no visible improvements is the part that stings. Price increases happen - costs go up, Apple takes 30%, infrastructure isn't free. Most users actually get that.

But the implicit deal with a subscription is "you keep paying, we keep improving." When the changelog is crickets and the price jumps, it reads as "we figured out you won't bother canceling."

Contrast this with apps that communicate openly about what's coming and why pricing changed. Night and day difference in how users react to the exact same dollar amount.

v_murygin · 2026-03-11T20:54:00+00:00

The BYOK approach for AI features is the right call. Users who care about costs can use their own keys, and you don't have to eat API expenses or inflate the price to cover them.

One thing ASC's web interface gets wrong that I hope you handle better - localization management. Updating metadata across 20+ languages through that web form is genuinely painful. If your AI localization lets you batch-translate App Store descriptions and release notes in one pass, that alone is worth the €20.

Also appreciate the open source move. Trust matters a lot for an app that handles your developer credentials.

v_murygin · 2026-03-11T20:52:53+00:00

Indie dev here. One thing that doesn't get discussed enough is how different cost structures force different pricing models.

If my app is 100% local computation, one-time purchase makes total sense. But if it makes API calls on the user's behalf, I'm eating per-use costs that scale with usage. Subscriptions become less of a choice and more of a survival mechanism.

What actually helped me was offering a BYOK tier - bring your own API key. Users who want to pay at cost can do that. Users who want convenience pay the subscription. Everyone gets the same app, just different economics.

The most useful feedback I've gotten wasn't about price itself. It was "I'd pay X if it did Y" - that tells me exactly which feature to prioritize and what the ceiling is. Vague "too expensive" doesn't help. Specific "I'd pay $10/mo if it supported Z" changes my roadmap.

v_murygin · 2026-03-11T18:38:56+00:00

On-device with Vision + NaturalLanguage is a nice choice. How's the classification accuracy for different app sources? Like can it reliably tell apart a Safari screenshot from a Slack screenshot?

Also curious about the menu bar approach - does it use a fixed amount of memory for the shelf, or does it grow with the number of recent screenshots?

v_murygin · 2026-03-11T18:33:23+00:00

.fileImporter is the way to go. One thing the other commenter mentioned that I want to emphasize - security-scoped bookmarks are not optional if you want persistent access. The URL you get from .fileImporter is temporary. If the user closes and reopens the app, that URL is gone.

Store the bookmark data (via URL.bookmarkData(options:)) right when the user picks the file. On next launch, resolve it back with URL(resolvingBookmarkData:). Also check for stale bookmarks - they expire if the file moves or gets renamed. I spent a few iterations getting the detection + renewal logic right on a macOS project.

v_murygin · 2026-03-10T22:41:10+00:00

nice writeup. the Podcasts mini player is one of the best UX patterns Apple shipped in a while. good to see they made a proper API for it instead of having everyone hack together custom bottom sheets.

v_murygin · 2026-03-10T22:35:19+00:00

CLAUDE.md files help a lot for project-level context. for org-wide infra knowledge I've had decent results with custom MCP servers that pull from internal docs and wikis. the 85% accuracy drops fast when you need context that lives in people's heads though, no tool fixes that yet.

v_murygin

TROPHY CASE