About, and how we ship
funnyapp.org is the catalogue of macOS apps made by the small team at Chongqing Swordfish Technology — the same hands that wrote HandleLens. We keep the catalogue short on purpose and publish everything ourselves.
Who makes these
We are a software studio in Chongqing, China. We write Mac apps, mostly for people who would rather have one precise tool than a suite. There is no investor waiting for growth, no roadmap presentation, and no plan to become a platform. When an app stops being worth maintaining, it stops being sold — that is the entire business model.
Why we sell direct
Every app here is a one-time purchase, delivered as a DMG, distributed from this site. That choice has reasons, and it has costs.
The reasons. A small tool should not need a store account to exist. A one-time price suits an app that does not run on a server, and it means the app does not have to nag you to renew anything. And when a fix is ready, it goes out the same day rather than into a review queue.
The costs, paid by us. There is no store badge vouching for the download, so we sign every release with an Apple Developer ID, submit it to Apple's notary service, staple the ticket and publish a SHA-256 next to the file. There is no store handling payments, so Paddle does, and there is no store support desk, so we answer the email ourselves.
How a release is made
Same six steps for one app or for ten. Nothing is published before the last one.
01 · Build. A universal macOS binary for Apple silicon and Intel, macOS 12 or later.
02 · Sign. Developer ID certificate, hardened runtime, Sparkle framework signed with it.
03 · Notarise. Uploaded to Apple's notary service and waited on. A rejected build is fixed, not shipped with a workaround.
04 · Staple. The notarisation ticket is attached to the app inside the DMG, so the first launch works offline.
05 · Checksum. SHA-256 of the exact file, printed on the app page and in SHA256SUMS.txt.
06 · Publish. The DMG, the notes and the feed entry go up together. If the download is not on the server, the version does not exist.
Why the catalogue is short
Because of the fun test. An app needs a premise that fits in one sentence and a build that tells the truth about what it found. Most ideas are amusing for a minute and then turn out to need a cloud account, a subscription, or a confident lie in the results. Those do not get built here.
How this site is built
Hand-written HTML and one stylesheet. No JavaScript, no framework, no build step, no analytics, no cookies, no external fonts. The pages render completely before anything else loads, because nothing else loads. Machines get the same care: a sitemap, llms.txt for assistants, and an RSS feed that lists every release.
Corrections and contact
If a claim on this site is wrong, or a version number, price or screenshot is out of date, write to support@swordfishsoft.org and it will be corrected on the page it appears on. Refunds follow the published refund policy.