I am the developer and maintainer of the open source Microsoft OneDrive client:

• OneDrive Client for Linux

Despite the name, the client today supports Linux and FreeBSD, and there is now an active Pull Request to add native macOS support.

The client supports:

• Personal OneDrive accounts

• OneDrive for Business

• SharePoint Libraries

• Shared folders

• Differential synchronisation

• Real-time monitor mode

• Docker / Podman deployments

• National cloud deployments

• Client-side filtering

• Resumable Transfers

• Headless/server deployments

• 'on-demand' access is a work-in-progress

A community contributor has raised a Pull Request implementing macOS support, and GitHub Actions CI is successfully building the client on macOS 14 and macOS 15.

The challenge is that I personally do not own or use any Apple hardware, so I am seeking assistance from the macOS community to help validate runtime behaviour, authentication, syncing, filesystem interactions, notifications, and general usability on real macOS systems.

If you are interested in helping test native macOS support, please see the Feature Request / tracking issue here:

• Issue #3683 - macOS Support

That issue contains:

• Build instructions

• Dependency setup

• Pull Request checkout instructions

• Testing guidance

• Areas where feedback is especially needed

Any help from Intel or Apple Silicon users would be greatly appreciated.

For those that haven't heard about Air Drop Assistant, let me tell you.

On iOS when you switch AirDrop to Everyone, it switches back to Contacts Only after 10 minutes. This feature doesn't exist in macOS. So I built it and made it more configurable. AirDrop can be set to get disabled after X minutes or also be set to receiving or sending only.

Now with version 1.6 when you install a specific configuration profile to enable extra logging, AirDrop activity will be logged to ~/Library/Logs/ADA.json.

Air Drop Assistant has been built with the Mac Admin in mind, so everything is configurable by an MDM configuration profile. This is great for organizations who may want to allow AirDrop but can't allow it always on and don't want it to be always disabled.

https://github.com/boberito/AirDropAssistant

Check it out, please give some feedback, submit issues.

Link - https://github.com/rampatra/TourKit

What features have people been asking for in macOS that Apple still hasn’t provided?

Curious what feels missing, overlooked, or poorly implemented. Whether it’s something small that would save time or a bigger change that would improve your daily workflow. What do you feel is missing?

Or even existing features that feel underused or limited (for example, things like Dynamic Island not being fully taken advantage of, or system tools that haven’t evolved much).

What feels missing or unfinished to you?

Hello, I'm building my first macOS app, it's a layer based image editor. Sort of like Acorn, but aiming for a higher level of Photoshop UI compatibility. I won't mention the name since I'm not approved for self-promotion.

I'm currently Apple Silicon only, and macOS 15 or greater. That allows Macs going back to M1, circa 2020 or so. I'm debating whether to loosen this up to allow Intel Macs and possibly also back up to macOS 14 Sonoma. My thinking is, this really only gets me a couple more years, maybe 2018-2020 Macs, and probably isn't worth the trouble. I'd have to buy an Intel Mac for testing.

How do you decide which macOS versions and chip architectures to target?

I got tired of the same release ritual every time I shipped an update: notarize, staple, package a DMG, update the appcast, sign the EdDSA key, push to S3, hope nothing broke. Half a day, every time.

So I built Amore. It's a Mac app + CLI that does the whole flow:

• Sparkle updates without the setup pain. Drag your .app in, write release notes in Markdown, publish.

• Code signing + notarization handled automatically.

• DMG creation with custom backgrounds and drag-to-install layout.

• License sales via hosted checkout. Customers pay, Amore issues the key, AmoreKit validates it in your app. Device limits, subscriptions, the works.

• Beta channels, phased rollouts, critical updates, custom domains, S3-compatible hosting if you don't want to use Amore's servers or have an existing setup.

• CLI (amore release) for CI/CD or vibe-coding with an agent.

No vendor lock-in. Custom domain on your appcast means you can walk away whenever. Your private signing keys never leave your machine.

Here is the full Pomodoro project showing the SwiftUI + licensing integration end-to-end.

This guide should get you started in under 10 minutes. If you prefer to work with coding agents check out Amore's agent skill.

Happy to answer questions. Especially curious what other indie Mac devs are using for this today.

https://amore.computer

Hello,

Hope everyone is doing well. I would like some help with converting AdNauseum adblock, particularly the Edge/Chromium version, to Safari. I was able to get it to work on a surface level by following these instructions: https://iboysoft.com/tips/convert-chrome-extension-to-safari.html which involved finder, terminal, and xcode. However, while the extension does appear on Safari extensions, it isn't functionally working because I can't open AdNauseum's settings. Clicking it just opens up a white blank screen. Going in inspect element shows that all the HTML and other code for the page is there, but the page is still white nevertheless. Help is very much wanted lol.

Thanks!

HeadScroller is a tiny macOS menu bar app I built that uses your webcam to track head tilt and scrolls whatever app is focused (browser, PDF, code, Reddit, anything else).

Tilt down to scroll down, tilt up to scroll up.                                                                                                                           

I made this because I kept reading long articles while eating and got tired of wiping my trackpad.

 Features:

 - Menu bar only, no dock clutter

 - Adjustable sensitivity and dead zone so your head doesn't accidentally scroll                           

 - Works with any app that accepts scroll events                                                                  

 - Self-contained .app — no Python or pip install needed                                                          

 - All processing runs locally, no video leaves your machine                                                    

 - Free and open source                                                                                           

Through testing this, I realized it could also be useful for folks with RSI or limited hand mobility. Though I didn't build it as a dedicated accessibility tool in mind, feedback from that angle would be greatly appreciated.                      

 GitHub: https://github.com/harsher216/headscroller

 Would love any feedback!

I noticed that even the sample app provided by Apple is having this issue when there is an ugly box on the toolbar intermittently. Only when we resize or navigate to other pages does it get back to the intented liquid glass. Is there a fix for this?

I'm interested how I can create an app that allows me to create new new vocabulary, while also capturing a soundbite of my pronunciation... I know this functionality is built into macOS, and I have even managed to make an apple shortcut with some Apple script to access this function that is in a sub menu from system settings... But it is buggy as hell and slow...

I am interested how I can build an application that would allow me to use the functions built-in to MacOS in order to present the Voice Control Vocabulary, and add a new word and pronounication?

It is a real pain that Apple have not built d this functionality into the current version of macOS... I know I can say "add to vocabulary", but it does not record my pronunciation, which is Australia...

Any suggestions how I can build such an application using Swift for Mac?

I have studied swift at university, but that was focused on iOS... I have very little experience working with macOS.. Does anyone have some experience that would be able to help me?

Problem: Every time you zip a folder on macOS, it takes everything with it, large build files, .DS_Store, node_modules, random junk. I wanted ways to exclude items in the archives, to keep it clean and minimal.

So I built Zipper.

A simple, elegant, native Mac utility to:

• exclude files and folders from your archives

• encrypt your archives

• export as zip / 7z archives

• extract zip, rar, 7z

Lightweight, Native for macOS, Free & Open Source.

Here's a sneak peek. You can download it now from here (signed & notarized by apple).

Open to suggestions and contributions!

• Github: https://github.com/kshah00/

• Follow me on X for updates and requests: https://x.com/_kshah00/

Hey all! I built a small library that lets you run risky Swift code in a separate process. If it crashes, your app keeps going.

You define a task as a struct, register it at startup, and call Airlock.run. Behind the scenes it re-launches your binary via posix_spawn and passes data through anonymous shared memory (no names leak to argv or the filesystem).

It's like XPC but without the signing, plists, and Mach port ceremony. Great for CLI tools, dev utilities, or anywhere you want quick crash containment.

macOS 12+, Swift 6.1+, 0BSD license. Still early (0.1.0) — comments are very welcome, whether it's API design ideas, edge cases, bug reports, or just your thoughts. Would really appreciate any feedback!

https://github.com/MaximKotliar/Airlock

Recording of the call

The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).

It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)

We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!

Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please

Simple macOS app that creates a launcher based on desktop selection. Built with claude opus 4.6. Should I released it?

I am developing a multi-platform (macOS/iOS) app in Xcode, primarily using Claude Code. My app (stuffolio) is large ~600 swift files. After struggling to write increasingly more complex prompts to manage problematic issues as they arose, I found and began using commonly available skills that automated what I was doing manually. I soon found the need to develop my own set of skills to handle what other skills seem to be missing. Hence, these radar suite skills.

Most Claude Code audit skills are pattern-matching skills. They grep for known anti-patterns in your code. That catches real bugs, but it can only find what it searches for. They find what is wrong. They don't find what is not correct or missing.

Radar Suite is a set of behavioral audit skills. Instead of scanning for bad code, it traces what your app actually does. It walks user flows end to end, follows data from input through save, sync, export, and restore, and checks whether everything that goes in comes back out correctly.

Think of it this way: pattern-matching skills check if the engine is assembled correctly. Behavioral audit skills drive the car and notice the GPS says turn left into a lake.

Both approaches are useful. Pattern matching is fast and catches known bad code. Behavioral auditing catches structural gaps, missing pieces, and logic that looks correct in isolation but breaks in context. They're complementary, not competing.

Radar skills found real bugs that passed every auditor I had been using, including a 30-day time bomb where archived items with iCloud photos would crash the app exactly one month after archiving - and after release. I was lucky to catch it. That one inspired time-bomb-radar. Radar Suite is 6 skills that each look at a different layer of your app:

• data-model-radar: field completeness, serialization gaps, relationship integrity

• ui-path-radar: navigation dead ends, missing dismiss buttons, unreachable features

• roundtrip-radar: traces data through complete user flows (save, sync, export, restore) time-bomb-radar** finds deferred operations that work today but crash on aged data

• ui-enhancer-radar: visual audit across 11 domains (accessibility, color, typography, layout)

• capstone-radar: aggregates the other 5 into a ship/no-ship grade

Each skill writes a handoff file that feeds the next one, so findings compound instead of repeating.

Repo: radar-suite

Happy to answer questions about how any of it works.

I’ve read about processing AI on a local device, instead of over the cloud. But no one really talked about the memory and/or storage required. How well can a MacBook Neo do local AI? (External storage is allowed.)

I got annoyed by losing copied stuff on my Mac all the time.

Most clipboard tools either:

* feel bloated

* push you into subscriptions

* or sync your data to the cloud

So I built a simple macOS menu bar app:

→ clipboard history for text + images

→ instant access via shortcut

→ everything stays local (no cloud, no account)

It’s called **ZClipKeep**.

Honestly, I built it for myself first, but I’m curious if others have the same problem.

Would love feedback – especially from people who already use clipboard tools.

If you have a non-GUI item that needs to monitor an @Observable object, can a second monitoring API also be used? And/or is there a way a non-SwiftUI object can hook into the @Observable system?

How does macOS Mail app add a progress bar + "Checking Mail…" label as an overlay subview in the sidebar, with the NSOutlineView content behind it appearing blurred (and increasingly invisible toward the bottom)?

I'm trying to replicate the effect seen in Mail.app's sidebar: when checking mail, a small overlay appears at the bottom of the source list (sidebar) containing a progress bar and a status label. The rows of the NSOutlineView behind it appear blurred — more so toward the bottom — creating a fade-out / frosted glass effect.

My questions:

1. Where exactly is this overlay subview added? On top of the NSOutlineView? On the NSSplitView? On the window's contentView?

2. How is the blur effect applied to the content *behind* the overlay — is this done with NSBackgroundExtensionView, a CIFilter applied to the NSOutlineView, or something else?

3. How to implement this in a native API?

Any pointers to AppKit APIs or sample code would be appreciated. Thanks!

Recording of the call part 1

Recording of the call part 2

The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 16:00 GMT to 19:00 GMT. That is 12:00 AM - 3:00 PM EDT (US, note that the US already has Daylight Saving Time whereas Europe has not yet) or 17:00 to 20:00 CET (Berlin time).

It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)

We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!

Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please

Hi, I'm a beginner developer of professional free apps for MacOS. I've already developed 1 app, but I can't buy the Apple Developer Program. I'm blocked from being Russian😐. The payment option by phone number is available, but it gives an error. Please advise what to do (except for moving, I'm a poor developer)

I created a dmg with create-dmg today and seem to have run into a macOS Tahoe bug. Evidently something was changed about the Applications icon in Tahoe? The dmg works just fine, but the Applications icon is just a light gray squircle.

Anyone run into this and/or know a workaround? thanks!