This media is not supported in your browser
VIEW IN TELEGRAM
App Trust Preview - what else can you learn before opening a Mac app?
https://redd.it/1wz6xzp
@macappsbackup
https://redd.it/1wz6xzp
@macappsbackup
Media is too big
VIEW IN TELEGRAM
[OS] Cling 3.0 - instant fuzzy search millions of files, 10x less RAM usage, Spotlight-like search UI
https://redd.it/1wza4h9
@macappsbackup
https://redd.it/1wza4h9
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
Askmeety : A 100% private Granola and Otter alternative. Zero cloud costs, no bots, and the v1.3 update just dropped!
https://redd.it/1wz85fm
@macappsbackup
https://redd.it/1wz85fm
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
AppRec - a tiny App Bar app which can record any application which generates sound — microphone optional —, then transcribe the text(multiple languages) and the summarize. Locally. No internet required after setup. Free. Open Sourced.
https://redd.it/1wz9ntg
@macappsbackup
https://redd.it/1wz9ntg
@macappsbackup
WDM 2.0 is here: one Mac app for downloads, media, conversion, browsing and more
https://preview.redd.it/mkpq6s0l7xth1.png?width=1576&format=png&auto=webp&s=7363ef40047df7f991943127b6266f6bdda94320
I originally built WDM because I was tired of needing a different app for every part of the same workflow.
One app for normal downloads. Another for media. Another for conversion. Another tool for saving groups of images. Browser extensions for capture. And sometimes even a separate browser just to get one stubborn download working.
For WDM 2.0, I decided I did not want to keep stacking features on the old architecture.
I rebuilt the application almost completely from scratch.
WDM 2.0 is now a native Swift/AppKit macOS application. It is no longer Electron.
And the main goal of 2.0 is not to be "another download manager."
The goal is much simpler:
For most download-related work on a Mac, you should not need another app next to WDM.
\## What makes WDM different
There are already well-known Mac apps in this space.
Downie is heavily focused on media downloading.
Folx is mainly a traditional download manager.
WDM 2.0 is built around a different idea:
Combine the entire download workflow into one application.
WDM brings together regular file downloads, browser capture, supported media downloads, a full built-in browser, a built-in converter, browser integration, batch image saving, file artwork, real media thumbnails, download history, notifications, and automatic media-engine updates.
I personally have not found another Mac download manager that combines this entire set of tools into one application.
That is really the point of WDM 2.0.
Instead of:
download manager + media tool + converter + browser extension + image saver + fallback browser
I wanted:
WDM.
\## Rebuilt from scratch in Swift
WDM 1.1 used Electron.
For WDM 2.0, I rebuilt the desktop application around Swift and AppKit.
WDM now has native builds for Apple Silicon and Intel, with support for macOS 12 or later.
The main interface, download workflow, windows, settings, converter, browser, notifications, progress handling and desktop integration were rebuilt around the native macOS version.
Both builds are signed with my Apple Developer ID and notarized by Apple.
\## Ready immediately after installation
WDM 2.0 includes its media engine inside the application.
There is no "install WDM and then wait while the rest of the engine downloads" step.
The components WDM uses for extraction, processing and conversion are already bundled.
Install WDM and it is ready to work.
The media engine can still update itself later when newer versions become available. WDM periodically checks automatically, and there is also a manual update option in Settings.
So the bundled engine gets you started immediately while future engine updates can still arrive without requiring a full WDM application update.
\## Download directly from the video
One of the browser-integration features I wanted to make especially convenient is the WDM Download button that appears directly on videos while you browse supported websites.
Instead of copying a link, switching apps and pasting it somewhere else, you can click the WDM button directly on the video you are watching and send that exact item into WDM.
The whole point is to make browser-to-download feel immediate instead of turning every download into a multi-step process.
\## WDM Browser
This is one of my favourite parts of WDM 2.0.
I did not want the built-in browser to be one of those tiny embedded web views that technically counts as a "browser" but exists only as a fallback.
I wanted it to actually be useful.
WDM Browser includes:
\- Multiple tabs
\- Address bar and search
\- Back / Forward / Reload / Home
\- Bookmarks
\- Bookmark folders
\- Bookmark editing and deletion
\- Bookmark import and export
\- Favorites bar
\- Favorites editing
\- Drag reordering
\- Browsing history
\- Open history entries
\-
https://preview.redd.it/mkpq6s0l7xth1.png?width=1576&format=png&auto=webp&s=7363ef40047df7f991943127b6266f6bdda94320
I originally built WDM because I was tired of needing a different app for every part of the same workflow.
One app for normal downloads. Another for media. Another for conversion. Another tool for saving groups of images. Browser extensions for capture. And sometimes even a separate browser just to get one stubborn download working.
For WDM 2.0, I decided I did not want to keep stacking features on the old architecture.
I rebuilt the application almost completely from scratch.
WDM 2.0 is now a native Swift/AppKit macOS application. It is no longer Electron.
And the main goal of 2.0 is not to be "another download manager."
The goal is much simpler:
For most download-related work on a Mac, you should not need another app next to WDM.
\## What makes WDM different
There are already well-known Mac apps in this space.
Downie is heavily focused on media downloading.
Folx is mainly a traditional download manager.
WDM 2.0 is built around a different idea:
Combine the entire download workflow into one application.
WDM brings together regular file downloads, browser capture, supported media downloads, a full built-in browser, a built-in converter, browser integration, batch image saving, file artwork, real media thumbnails, download history, notifications, and automatic media-engine updates.
I personally have not found another Mac download manager that combines this entire set of tools into one application.
That is really the point of WDM 2.0.
Instead of:
download manager + media tool + converter + browser extension + image saver + fallback browser
I wanted:
WDM.
\## Rebuilt from scratch in Swift
WDM 1.1 used Electron.
For WDM 2.0, I rebuilt the desktop application around Swift and AppKit.
WDM now has native builds for Apple Silicon and Intel, with support for macOS 12 or later.
The main interface, download workflow, windows, settings, converter, browser, notifications, progress handling and desktop integration were rebuilt around the native macOS version.
Both builds are signed with my Apple Developer ID and notarized by Apple.
\## Ready immediately after installation
WDM 2.0 includes its media engine inside the application.
There is no "install WDM and then wait while the rest of the engine downloads" step.
The components WDM uses for extraction, processing and conversion are already bundled.
Install WDM and it is ready to work.
The media engine can still update itself later when newer versions become available. WDM periodically checks automatically, and there is also a manual update option in Settings.
So the bundled engine gets you started immediately while future engine updates can still arrive without requiring a full WDM application update.
\## Download directly from the video
One of the browser-integration features I wanted to make especially convenient is the WDM Download button that appears directly on videos while you browse supported websites.
Instead of copying a link, switching apps and pasting it somewhere else, you can click the WDM button directly on the video you are watching and send that exact item into WDM.
The whole point is to make browser-to-download feel immediate instead of turning every download into a multi-step process.
\## WDM Browser
This is one of my favourite parts of WDM 2.0.
I did not want the built-in browser to be one of those tiny embedded web views that technically counts as a "browser" but exists only as a fallback.
I wanted it to actually be useful.
WDM Browser includes:
\- Multiple tabs
\- Address bar and search
\- Back / Forward / Reload / Home
\- Bookmarks
\- Bookmark folders
\- Bookmark editing and deletion
\- Bookmark import and export
\- Favorites bar
\- Favorites editing
\- Drag reordering
\- Browsing history
\- Open history entries
\-
Delete individual history entries
\- Clear history
\- Persistent browser state
\- Direct download handoff to WDM
\- Supported media capture
It also has a built-in local ad blocker.
The blocker is part of WDM Browser itself. It does not require a separate paid blocking application.
So if you ever need WDM Browser for a download, you are not being thrown into a stripped-down recovery window.
You still have proper tabs, bookmarks, history, blocking and normal browser controls.
\## Built-in Converter
WDM 2.0 also includes a full converter.
I did not want the converter to be a checkbox feature that exists only so I could put "Converter" on a feature list.
It supports:
\- Individual file import
\- Folder import
\- Conversion queue
\- Video to audio conversion
\- Supported video output formats
\- Supported image conversions
\- Supported document conversions
\- Progress and activity status
\- Cancelling jobs
\- Safe handling when an output filename already exists
\- Thumbnails and artwork
\- Open completed output
\- Show completed output in Finder
The converter uses the same media engine already bundled with WDM, so there is no additional setup before you can start using it.
You can also continue using the rest of WDM while conversions are running.
\## File artwork and real media thumbnails
This part consumed an unreasonable amount of development time, but I really cared about it.
WDM does not treat every download as the same generic document icon.
Normal files use dedicated artwork based on their file type.
Documents, archives, installers, images, audio, video and many other formats have their own visual treatment, with a proper fallback for unknown file types.
Media is handled differently.
When WDM has the real thumbnail or poster for the item you selected, that thumbnail has priority over generic file artwork.
I also spent a lot of time making sure the thumbnail belongs to the actual media you clicked, not a nearby recommendation, another card or the wrong item on the page.
Thumbnail loading is also independent from download execution.
If a thumbnail is slow or unavailable, the download should still start.
The same artwork and thumbnail system is used throughout confirmation, active-download and completed-download views.
\## Batch image saving
WDM also supports image-heavy pages through its browser integration.
Instead of manually saving images one by one, supported pages can send multiple images to WDM as a batch.
That makes it useful for galleries, posts and pages containing many images.
\## Normal downloading is still at the core
Under all of this, WDM is still a general-purpose download manager.
It supports:
\- Multiple connections where available
\- Pause and resume
\- Retry handling
\- Download speed
\- Progress
\- Remaining size and ETA where available
\- Save-location control
\- Download history
\- Notifications
\- Open
\- Show in Finder
\- Browser capture
A lot of my work on 2.0 was not adding flashy features.
It was fixing the boring little details that make a download manager feel trustworthy when you use it every day: progress accuracy, resume behaviour, stale jobs, duplicate capture, filenames, browser ownership and completed-download state.
\## Browser integration
WDM integrates with:
\- Safari
\- Chrome
\- Edge
\- Brave
\- Firefox
\- Other compatible Chromium browsers
Safari support is bundled directly with the Mac application.
Chromium browsers and Firefox use their WDM 2.0 companions.
\## Dark and Light Mode
WDM supports both Dark and Light Mode across the main application, settings, confirmation windows, converter and download interfaces.
\## Settings and updates
WDM has persistent settings covering download behaviour, browser integration, media handling, notifications, download folders, engine behaviour and other runtime preferences.
WDM itself has an application update system, while the bundled media components have their own managed
\- Clear history
\- Persistent browser state
\- Direct download handoff to WDM
\- Supported media capture
It also has a built-in local ad blocker.
The blocker is part of WDM Browser itself. It does not require a separate paid blocking application.
So if you ever need WDM Browser for a download, you are not being thrown into a stripped-down recovery window.
You still have proper tabs, bookmarks, history, blocking and normal browser controls.
\## Built-in Converter
WDM 2.0 also includes a full converter.
I did not want the converter to be a checkbox feature that exists only so I could put "Converter" on a feature list.
It supports:
\- Individual file import
\- Folder import
\- Conversion queue
\- Video to audio conversion
\- Supported video output formats
\- Supported image conversions
\- Supported document conversions
\- Progress and activity status
\- Cancelling jobs
\- Safe handling when an output filename already exists
\- Thumbnails and artwork
\- Open completed output
\- Show completed output in Finder
The converter uses the same media engine already bundled with WDM, so there is no additional setup before you can start using it.
You can also continue using the rest of WDM while conversions are running.
\## File artwork and real media thumbnails
This part consumed an unreasonable amount of development time, but I really cared about it.
WDM does not treat every download as the same generic document icon.
Normal files use dedicated artwork based on their file type.
Documents, archives, installers, images, audio, video and many other formats have their own visual treatment, with a proper fallback for unknown file types.
Media is handled differently.
When WDM has the real thumbnail or poster for the item you selected, that thumbnail has priority over generic file artwork.
I also spent a lot of time making sure the thumbnail belongs to the actual media you clicked, not a nearby recommendation, another card or the wrong item on the page.
Thumbnail loading is also independent from download execution.
If a thumbnail is slow or unavailable, the download should still start.
The same artwork and thumbnail system is used throughout confirmation, active-download and completed-download views.
\## Batch image saving
WDM also supports image-heavy pages through its browser integration.
Instead of manually saving images one by one, supported pages can send multiple images to WDM as a batch.
That makes it useful for galleries, posts and pages containing many images.
\## Normal downloading is still at the core
Under all of this, WDM is still a general-purpose download manager.
It supports:
\- Multiple connections where available
\- Pause and resume
\- Retry handling
\- Download speed
\- Progress
\- Remaining size and ETA where available
\- Save-location control
\- Download history
\- Notifications
\- Open
\- Show in Finder
\- Browser capture
A lot of my work on 2.0 was not adding flashy features.
It was fixing the boring little details that make a download manager feel trustworthy when you use it every day: progress accuracy, resume behaviour, stale jobs, duplicate capture, filenames, browser ownership and completed-download state.
\## Browser integration
WDM integrates with:
\- Safari
\- Chrome
\- Edge
\- Brave
\- Firefox
\- Other compatible Chromium browsers
Safari support is bundled directly with the Mac application.
Chromium browsers and Firefox use their WDM 2.0 companions.
\## Dark and Light Mode
WDM supports both Dark and Light Mode across the main application, settings, confirmation windows, converter and download interfaces.
\## Settings and updates
WDM has persistent settings covering download behaviour, browser integration, media handling, notifications, download folders, engine behaviour and other runtime preferences.
WDM itself has an application update system, while the bundled media components have their own managed
update path.
That means a component can receive an update without requiring an entirely new WDM release.
\## WDM vs Downie vs Folx
For me, this is where WDM 2.0 makes the most sense.
If all you need is a specialised media downloader, Downie may already cover your use case.
If you want a traditional download manager, Folx is a mature option.
WDM is designed to replace the collection of download-related utilities you would normally keep around them.
The advantage is not one isolated feature.
It is the combination:
general downloads + media workflows + converter + full browser + ad blocking + browser integration + in-video download controls + batch images + artwork + thumbnails + download management
inside one Mac application.
That is what I wanted WDM to become.
Not another downloader sitting next to five other utilities.
The one app you open when you need to download something.
\## Privacy
WDM processes its download and conversion workflows locally on the Mac.
Files are not uploaded to an external conversion service simply because you are converting them.
The built-in browser blocker also runs locally.
\## Pricing
WDM includes a 7-day free trial.
There is no subscription.
Solo: $17.99 one-time
1 user, 1 Mac
Duo: $27.99 one-time
Up to 2 users and 2 Macs
Family: $44.99 one-time
Members of one private household
Future WDM versions are included.
Existing WDM lifetime customers receive WDM 2.0 at no additional charge.
\## 🎁 Launch Giveaway — 5 Free Lifetime Licenses
To celebrate the launch of WDM 2.0, I am giving away 5 WDM Solo lifetime licenses.
You can contribute in any useful way: report a bug, find an issue on the website, send detailed feedback, suggest something that would genuinely improve WDM, create a tutorial or demo, or publicly share WDM and show me what you posted.
One week after this post, I will choose the 5 contributions that were the most useful to WDM and its launch.
No purchase or positive review is required. Honest criticism absolutely counts. If you find something broken or something you think should be better, I want to hear it.
\## Trust and transparency
I am Waleed Refai, founder and developer of Welaxxx and the developer behind WDM.
WDM is distributed directly through the official Welaxxx website.
Both macOS builds are signed with my Apple Developer ID and notarized by Apple.
Developer / LinkedIn:
https://www.linkedin.com/in/waleed-refai-b8a15875/
WDM 2.0:
https://welaxxx.com/wdm.html
Official website:
https://welaxxx.com
Contact:
https://welaxxx.com/contact.html
Privacy Policy:
https://welaxxx.com/privacy.html
Terms of Service:
https://welaxxx.com/terms.html
I spent months rebuilding WDM 2.0, testing it on Intel and Apple Silicon, breaking things, fixing them, and then somehow finding new ways to break them again.
It is finally out.
If you try it, I genuinely want to know:
Could WDM replace the download-related apps you currently keep on your Mac? And if not, what is the one thing still missing?
https://redd.it/1wzg5b4
@macappsbackup
That means a component can receive an update without requiring an entirely new WDM release.
\## WDM vs Downie vs Folx
For me, this is where WDM 2.0 makes the most sense.
If all you need is a specialised media downloader, Downie may already cover your use case.
If you want a traditional download manager, Folx is a mature option.
WDM is designed to replace the collection of download-related utilities you would normally keep around them.
The advantage is not one isolated feature.
It is the combination:
general downloads + media workflows + converter + full browser + ad blocking + browser integration + in-video download controls + batch images + artwork + thumbnails + download management
inside one Mac application.
That is what I wanted WDM to become.
Not another downloader sitting next to five other utilities.
The one app you open when you need to download something.
\## Privacy
WDM processes its download and conversion workflows locally on the Mac.
Files are not uploaded to an external conversion service simply because you are converting them.
The built-in browser blocker also runs locally.
\## Pricing
WDM includes a 7-day free trial.
There is no subscription.
Solo: $17.99 one-time
1 user, 1 Mac
Duo: $27.99 one-time
Up to 2 users and 2 Macs
Family: $44.99 one-time
Members of one private household
Future WDM versions are included.
Existing WDM lifetime customers receive WDM 2.0 at no additional charge.
\## 🎁 Launch Giveaway — 5 Free Lifetime Licenses
To celebrate the launch of WDM 2.0, I am giving away 5 WDM Solo lifetime licenses.
You can contribute in any useful way: report a bug, find an issue on the website, send detailed feedback, suggest something that would genuinely improve WDM, create a tutorial or demo, or publicly share WDM and show me what you posted.
One week after this post, I will choose the 5 contributions that were the most useful to WDM and its launch.
No purchase or positive review is required. Honest criticism absolutely counts. If you find something broken or something you think should be better, I want to hear it.
\## Trust and transparency
I am Waleed Refai, founder and developer of Welaxxx and the developer behind WDM.
WDM is distributed directly through the official Welaxxx website.
Both macOS builds are signed with my Apple Developer ID and notarized by Apple.
Developer / LinkedIn:
https://www.linkedin.com/in/waleed-refai-b8a15875/
WDM 2.0:
https://welaxxx.com/wdm.html
Official website:
https://welaxxx.com
Contact:
https://welaxxx.com/contact.html
Privacy Policy:
https://welaxxx.com/privacy.html
Terms of Service:
https://welaxxx.com/terms.html
I spent months rebuilding WDM 2.0, testing it on Intel and Apple Silicon, breaking things, fixing them, and then somehow finding new ways to break them again.
It is finally out.
If you try it, I genuinely want to know:
Could WDM replace the download-related apps you currently keep on your Mac? And if not, what is the one thing still missing?
https://redd.it/1wzg5b4
@macappsbackup
Linkedin
Waleed Refai - Yerevan, Yerevan, Armenia | Professional Profile | LinkedIn
Experience: Plus Markets Real Estate · Education: Zagazeeg University · Location: Yerevan · 32 connections on LinkedIn. View Waleed Refai’s profile on LinkedIn, a professional community of 1 billion members.
I tested Mac apps one by one to improve Mole. Some cleanup rules needed to remove less.
Hi r/macapps, I'm Tw93, the developer of Mole. The CLI is free and open source. This post is about the separate, paid native Mac app at mole.fit, where you can also find the privacy policy, terms, and support contact.
Problem
A cleaner needs to know what an app leaves behind, and which of those files still matter. I spent the past few weeks installing apps, opening them, granting permissions, checking updates and startup items, then uninstalling them.
That found missing leftovers, but it also caught places where my cleanup rules were too broad: shared vendor folders, data another app still uses, and files that only look abandoned. Those rules needed to remove less.
https://preview.redd.it/0wgapljdquth1.jpg?width=2584&format=pjpg&auto=webp&s=39c47bb53809e6be822023808caf862be8b12985
AI tools added another problem. Caches, coding sessions, worktrees, and downloaded models can all take up a lot of space, but losing them has very different consequences. I initially focused on regenerable caches and old CLI versions. After my own disk filled up and users reported large AI-tool folders, I installed and used a few dozen AI apps and CLIs to see what they left behind.
The AI cleanup page groups items by what removing them costs. Caches start checked; sessions and worktrees need deliberate review; unused tools stay unchecked. Local model stores are left alone. This page is still in Preview.
AI cleanup in Preview, with all rows selected for this screenshot.
Comparison
AppCleaner is a free option for removing an app and its related files. Mole also covers caches beyond individual uninstalls, disk analysis, and, in Preview, AI-tool data. The extra work here is deciding which leftovers can be offered for cleanup and which need to stay.
CleanMyMac covers a broader set of tasks, including malware scanning. Mole focuses on cleanup, app management, disk analysis, maintenance, and system monitoring, with a one-time purchase. You can review the cleanup list and protect paths you want to keep.
Pricing
Mole for Mac is $19 once for two Macs, with free updates and no subscription. You can try each paid tool twice before buying. Requires macOS 14 or later.
Mac app: mole.fit
Free, open-source CLI: github.com/tw93/Mole
What's a file or folder you've seen a cleaner mark for removal that you were glad you checked first?
https://redd.it/1wz36bh
@macappsbackup
Hi r/macapps, I'm Tw93, the developer of Mole. The CLI is free and open source. This post is about the separate, paid native Mac app at mole.fit, where you can also find the privacy policy, terms, and support contact.
Problem
A cleaner needs to know what an app leaves behind, and which of those files still matter. I spent the past few weeks installing apps, opening them, granting permissions, checking updates and startup items, then uninstalling them.
That found missing leftovers, but it also caught places where my cleanup rules were too broad: shared vendor folders, data another app still uses, and files that only look abandoned. Those rules needed to remove less.
https://preview.redd.it/0wgapljdquth1.jpg?width=2584&format=pjpg&auto=webp&s=39c47bb53809e6be822023808caf862be8b12985
AI tools added another problem. Caches, coding sessions, worktrees, and downloaded models can all take up a lot of space, but losing them has very different consequences. I initially focused on regenerable caches and old CLI versions. After my own disk filled up and users reported large AI-tool folders, I installed and used a few dozen AI apps and CLIs to see what they left behind.
The AI cleanup page groups items by what removing them costs. Caches start checked; sessions and worktrees need deliberate review; unused tools stay unchecked. Local model stores are left alone. This page is still in Preview.
AI cleanup in Preview, with all rows selected for this screenshot.
Comparison
AppCleaner is a free option for removing an app and its related files. Mole also covers caches beyond individual uninstalls, disk analysis, and, in Preview, AI-tool data. The extra work here is deciding which leftovers can be offered for cleanup and which need to stay.
CleanMyMac covers a broader set of tasks, including malware scanning. Mole focuses on cleanup, app management, disk analysis, maintenance, and system monitoring, with a one-time purchase. You can review the cleanup list and protect paths you want to keep.
Pricing
Mole for Mac is $19 once for two Macs, with free updates and no subscription. You can try each paid tool twice before buying. Requires macOS 14 or later.
Mac app: mole.fit
Free, open-source CLI: github.com/tw93/Mole
What's a file or folder you've seen a cleaner mark for removal that you were glad you checked first?
https://redd.it/1wz36bh
@macappsbackup
GitHub
tw93 - Overview
Anything added dilutes everything else. tw93 has 53 repositories available. Follow their code on GitHub.
This media is not supported in your browser
VIEW IN TELEGRAM
DockPops 6 is my biggest update ever: an Apple Intelligence assistant, live animated themes, a redesigned UI, a new theme manager, and more
https://redd.it/1wzclkp
@macappsbackup
https://redd.it/1wzclkp
@macappsbackup
[OS] ThinkTerm: free and open-source terminal multiplexer, multi-workspace, no UI framework
https://redd.it/1wzij6b
@macappsbackup
https://redd.it/1wzij6b
@macappsbackup
Reddit
From the macapps community on Reddit: [OS] ThinkTerm: free and open-source terminal multiplexer, multi-workspace, no UI framework
Explore this post and more from the macapps community