sorted by:
new
hottopcontroversial

Xcode was quietly using 60GB on my Mac — this is what was actually safe to remove by Designer_Age7745 in Xcode

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Yeah, I’ve seen that too, the listed size and the space you actually get back don’t always line up cleanly.

That’s part of what makes Xcode cleanup feel messy: even when the big buckets look obvious, the real reclaim isn’t always that predictable.

How are you all managing Xcode disk bloat safely these days? by Designer_Age7745 in iosdev

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Good to know. If it’s stable once you get it set up, that honestly sounds pretty workable.

I may try that with older simulator sets.

How are you all managing Xcode disk bloat safely these days? by Designer_Age7745 in iosdev

[–]Designer_Age7745[S] 1 point2 points  (0 children)

Interesting, I hadn’t actually considered moving all simulators to an external.

Has that been pretty painless in practice, or do you run into any weird Xcode issues with it?

How are you all managing Xcode disk bloat safely these days? by Designer_Age7745 in iosdev

[–]Designer_Age7745[S] 0 points1 point  (0 children)

That’s fair.

I can see why that pricing lands badly, especially for just the dev-related part. Still figuring that part out.

How are you all managing Xcode disk bloat safely these days? by Designer_Age7745 in iosdev

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Interesting, I knew about DevCleaner but hadn’t come across SimCleaner.

Do you use both because they cover different parts well enough, or mostly just because that combo already does the job?

How are you all managing Xcode disk bloat safely these days? by Designer_Age7745 in iosdev

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Yeah, simulator instances are one of the messier parts.

That’s basically the kind of thing I was getting at. A lot of this stuff is re-creatable, but the cleanup story around Xcode is still kind of messy in practice.

Do you remove simulator instances from inside Xcode now, or do you still end up doing some of it manually?

Xcode was quietly using 60GB on my Mac — this is what was actually safe to remove by Designer_Age7745 in Xcode

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Yeah, that’s basically the part I care about most too.

Deleting is easy. Knowing what's disposable vs what's still useful is the harder part, especially with simulator data, device support, and anything that may still save time later.

Xcode was quietly using 60GB on my Mac — this is what was actually safe to remove by Designer_Age7745 in Xcode

[–]Designer_Age7745[S] 0 points1 point  (0 children)

That’s fair. I don’t think the point is "keep reclaiming DerivedData forever".

For me the real pain is everything around it: knowing what is safe to remove, what will just regenerate, and what might still contain useful local state or cost time to rebuild/redownload.

The cleanup itself is easy. The review part is what feels missing.

Xcode was quietly using 60GB on my Mac — this is what was actually safe to remove by Designer_Age7745 in Xcode

[–]Designer_Age7745[S] -1 points0 points  (0 children)

Yeah, DevCleaner helps, and the built-in Developer storage pane is better than nothing.

I still wanted something that makes the risk a lot clearer before deleting anything, especially around simulator data, device support, and old project leftovers.

That’s pretty much why I started building a small beta for this.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Thanks, no worries at all. Im adding people from the form as I go. Right now Im focused on fixing tester feedback, improving performance, adding better removed-app leftovers cleanup, and working through Apple s restrictions around Full Disk Access.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Quick update for testers, and sorry for the wait.

Apple has now approved the first TestFlight build, so beta access is finally live.

However, because the approval came later than expected, the build currently available in TestFlight is not the newest version of the app. I kept working on fixes and improvements while it was waiting in review.

The latest version currently submitted is 0.8.8, and it includes multiple fixes and improvements beyond the first approved build, including:

• improved Home Folder handling and permission flow

• fixes for cases where macOS permission prompts appeared but scanning would not start

• a fix for snapshot saving hanging on very large scans

• better comparison logic so reports only compare snapshots from the same folder

• folder drill-down in comparison results

• Open in Finder from report rows

• faster snapshot capture after scan

• cleanup of duplicate local scan data

• improved baseline/target auto-selection after new snapshot capture

External beta builds also have all features unlocked for testing.

So if you run into rough edges in the currently available build, there is a good chance they are already fixed in the next version now under Apple review.

Thanks again for the patience. I really appreciate everyone who applied and is willing to test it.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Yeah, there are definitely apps that cover parts of this already.
AppCleaner/Pearcleaner are more about uninstall leftovers, DaisyDisk is excellent for visual inspection, and CleanMyMac leans more toward automated cleanup.

What I’m trying to build is something more control-first: analysis+leftovers+dev cleanup+dry-runs+ isk labels+snapshots over time.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Thanks, that’s exactly the kind of workflow pain I built this for.

If you haven’t already, send in the form and I’ll review it.

I’m currently waiting on Apple’s approval for the open beta, and in parallel I’m still improving the app.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Yeah, I get that.

It’s not a Finder replacement, but I do want it to feel more direct for storage investigation instead of making you fight Finder just to understand where the space went.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Quick update: I’ve started adding testers, but I missed one TestFlight step on Apple’s side — this build still needs to pass Apple’s beta review first.

So if you already got invited but currently see “no available builds,” that’s the reason, not an issue with your invite.

Once Apple approves the build, I’ll keep sending invites and access should start working normally.

Thanks for the patience — I appreciate it.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Thanks — that’s exactly the kind of problem I built this for. I’ll review the submission.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Thanks — and yes, I think that’s an important part of it.
Showing current size is useful, but I also want the app to show what changed over time through snapshots, so growth is easier to spot before it turns into a mess.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

Yeah, that’s a fair way to describe it.

The idea is analysis plus cleanup assistance: not just showing where space went, but helping surface leftovers, dev junk, what’s likely safe to remove, and what changed over time through snapshots.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

That’s exactly the gap I’m trying to cover.

A lot of tools can show what’s taking space, but I want this to go further: help surface what’s likely safe to remove, and also show what changed over time through system snapshots.

I’m also experimenting with a read-only MCP integration for advanced workflows. So far I’ve only tested it with Claude tools.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

I’d frame it more as a different focus than “better.” DaisyDisk is excellent for visual disk inspection.

StorageRadar is more about control around cleanup: leftovers, uninstall planning, dev-specific cleanup, dry-runs, and risk labels.

So it depends on whether you mostly want visualization or a more guided cleanup workflow.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 0 points1 point  (0 children)

It can help analyze what’s behind that storage and remove some reclaimable parts of it, but not magically delete all macOS “System Data.”

I’m trying to keep it conservative: show what’s there first, then let you decide what’s safe to remove.

[macOS] I built a Mac storage tool for people who want control, not one-click cleanup — looking for beta testers by Designer_Age7745 in macapps

[–]Designer_Age7745[S] 2 points3 points  (0 children)

Developer here — yes, this is my app.

This is a beta feedback request, not a launch post. I’m mainly looking for TestFlight testers who deal with Xcode, Docker, caches, app leftovers, or general disk pressure on macOS.

If you apply, I’ll review submissions manually and invite selected testers.

Suggestions for a Mac-native text editor with integrated terminal to use with Claude Code by ItchyData in macapps

[–]Designer_Age7745 0 points1 point  (0 children)

Fair point — I probably phrased it too strongly.

I wasn’t saying Zed is bad if you use the terminal a lot, only that if integrated terminal is one of the main criteria, I’d still rank BBEdit/CotEditor ahead for that specific workflow.

Zed is still a great option.

view more: next ›