Skip to Content

Apps

Native macOS app development

I build native Mac apps in Swift, SwiftUI and AppKit: menu-bar utilities, productivity tools and software that keeps your data on the machine. My own app Clipivo is a native clipboard manager with full-text search, so I know the work from first sketch to a signed, notarized release.

Updated

Problems this solves

  • Your team lives in a browser tab or an Electron app that feels slow, drains the battery and does not look like a Mac app.
  • You need something that works with the clipboard, the menu bar, global shortcuts or files, and a web app cannot reach that deep.
  • Your data is private and should stay on the Mac, not in someone else's cloud.
  • You have a working prototype but no idea how to sign, notarize and ship it so macOS does not warn customers away.

What I build

  • Menu-bar utilities and background helpers that stay out of the way until you need them
  • Productivity apps with global shortcuts, quick search and fast, native-feeling lists
  • Local-first apps with an on-device database, full-text search and optional encrypted storage
  • Tools that read the clipboard, files, screenshots or the system share sheet, including on-device text recognition
  • Settings, onboarding and permission prompts that explain themselves instead of confusing people
  • Code signing, notarization and an update flow, for direct download or the Mac App Store

How it works

  1. 1Talk it through

    We go over who uses the app, what it must do every day and what can wait. You get a short written plan and a rough screen sketch.

  2. 2Build the core

    I start with the one thing the app is for, in SwiftUI with AppKit where the system needs it. You get a working build to try early.

  3. 3Harden and polish

    Permissions, edge cases, light and dark mode, keyboard shortcuts and data safety get a proper pass, tested on real Macs.

  4. 4Ship and hand over

    I set up signing and notarization, package the release and hand over the source and your developer accounts.

Work that shows it

Tools I use

  • Swift 6
  • SwiftUI
  • AppKit
  • SQLite FTS5
  • CryptoKit
  • Vision (OCR)
  • Xcode
  • Sparkle updates

Working with clients abroad

I work remotely with clients worldwide from Assam, India, and in person across Assam and Guwahati. Quotes are in USD and paid by Wise or international bank transfer. Code lives in your GitHub from day one, and you get a staging link to try at every step.

Questions

Yes. I work remotely, so you can be anywhere: the US, UK, Germany, Australia and elsewhere, with calls at times that overlap your day. You get written updates and a build you can run yourself.
You do. The repository, the Apple Developer account and the signing certificates are in your name, and I hand over the full source when the work is done.
It depends on what the app does. Apps that need broad system access often suit direct download with notarization, while simpler apps fit the App Store sandbox. I explain the trade-offs before we pick.
Native apps start faster, use less memory and fit the system better. If you also need Windows, I will tell you honestly when a shared codebase makes more sense.
It depends on the scope; you get an estimate after a first call, and a working version to try early. Quotes for overseas clients are in USD.

Tell me what you have in mind, and I'll tell you how I'd build it.