About

About Chargeberry

Chargeberry is a small, pay-once battery app for the Mac by Ayesha Gagan, who also makes Shelfy and Invoicewell and builds them all in public.

By , who makes Chargeberry · Published · 3 min read

The maker

Ayesha Gagan makes small, pay-once Mac apps: Chargeberry, Shelfy and Invoicewell. Chargeberry is written in Swift, every charging feature is tested on a real MacBook before it ships, and the whole build is shared in public on X. You can find more at ayeshagagan.com, and the day-to-day on X, @ayeshagagan.

Made by
Ayesha Gagan, mac app developer
Other apps
Shelfy (a file shelf beside the Dock) and Invoicewell (invoices you ask an AI for)
Chargeberry started
October 21, 2026 (first commit)
First release
October 25, 2026
Current version
1.1.2, November 1, 2026
Support
adgan.business@gmail.com

Why Chargeberry exists

Most MacBooks spend their lives plugged in, charged to 100% and warm, and that’s exactly what wears a battery out fastest. The Mac Chargeberry was built on, a MacBook Air (M1, 2020), shows it: 83% of its original capacity after 353 cycles. A charge limit is the simple fix, and Chargeberry is meant to be the one you set once and forget: a limit, a pause when it’s hot, a full battery when you need one, and a clear view of how the battery is doing. For a one-time price, without a subscription.

How it’s made

  • Native. Written in Swift and SwiftUI. A menu bar app, a Settings window and a welcome; no Electron, no web view.
  • A small helper does the charging. macOS asks you to approve it once. It only ever changes charging, checks the app’s signature on every connection, and holds your limit with the app closed.
  • Built to fail safe. If anything holding the charging switches quits or crashes, normal charging comes back. Delete the app, and the helper restores normal charging and leaves.
  • Private. No account, no analytics or tracking in the app. Battery data stays on your Mac.

How it’s tested

Every charging feature is tried on a real MacBook before it ships, not just in code: the hardware self-test really stops charging, cuts the charger, drains, calibrates and kills the app mid-way, and after each test reads the battery controller to confirm charging is back to normal. Bugs found this way get fixed before release, like a calibration that, in testing, let a Mac sleep on its battery with the charger plugged in.

According to Chargeberry’s own tests, when the process holding a charging switch was killed, normal charging came back within 1 second, and the app uses about 0.1% CPU (0.13% on average, 0.4% at its busiest moment) and 13 MB of memory while it sits in the menu bar, and its helper about 0.03% CPU and 7 MB.

Measured by Chargeberry: Chargeberry’s crash-safety test, part of its hardware self-test, run on a MacBook Air (M1, 2020) on October 28, 2026: a client holding the charge switch, then the charger switch, was killed with kill -9 while the switches were read back from the battery controller. A development build of Chargeberry 1.1.2 (the same code as the release, without its compiler optimizations) on a MacBook Air (M1, 2020) with macOS 15.7.4, sampled with top every 5 seconds for 10 minutes (120 samples), the helper for 1 minute, and memory read with footprint, on November 6, 2026. Your numbers will vary with your Mac.

About this site

The guides and comparisons here are written by the maker of Chargeberry. Facts about other apps come from their developers’ own sites, GitHub pages and release notes, with the date they were checked, and each comparison says plainly where the other app is better. If you spot something wrong or out of date, email adgan.business@gmail.com and it’ll be fixed.