Skip to content
TAA

Article

MacBusinessSuite Is Live: Adding a New App to the Roster

MacBusinessSuite hit the Mac App Store this week. Here is what it took to get it listed across two sites, plus a small Civo Cloud Manager release.

, Marcel R. G. Berger, 5 min read

  • macos app development
  • macbusinesssuite
  • civo-cloud-manager
  • build-in-public
  • astro
  • solo-developer
Share

MacBusinessSuite is now listed in the Mac App Store. That is the concrete change this week, and it touched more moving parts than a simple “add an app” commit would suggest. Getting a new app surfaced correctly across two separate sites, with store links that actually resolve, turned out to involve a workaround I had not anticipated. Alongside that, Civo Cloud Manager picked up a small metadata-only release. Neither of these is a major version story, but together they make for an honest picture of what maintaining a portfolio of macOS apps actually looks like week to week.

The first thing I did was add MacBusinessSuite to the app grids on both theapparchitect.com and my personal portfolio site. That part was straightforward: add the entry, wire up the store link, make sure it appears in every context where the other apps appear. Two commits, both on the same day, done in a couple of hours.

What was not straightforward was the App Store lookup. Both sites use Apple’s public iTunes Search API to pull live metadata for listed apps: the icon URL, the app name, the current version. It is a sensible approach because it means the displayed data stays current without me having to update it manually every time I ship a new build. The problem is that Apple does not always surface a freshly listed app in the developer-level query immediately. The API endpoint that lets you fetch all apps by a developer ID sometimes lags behind the actual App Store listing by hours, occasionally longer. MacBusinessSuite was live and purchasable, but the developer query was returning everything except it.

The fix I landed on is a two-stage lookup. If an app is missing from the developer query, the site now falls back to querying that specific app by its App Store ID directly, which resolves reliably even when the broader developer endpoint has not caught up yet. And if even that fails, there is a local fallback record that keeps the page from showing a broken tile. It is not elegant, but it is honest about the fact that Apple’s API has its own schedule and there is no way to force it. I would rather have a working site with a belt-and-braces fallback than a site that breaks silently whenever Apple is slow to index something.

The thing I am not fully happy with is that the local fallback record means I have app metadata in two places: the live API and a static file. If I ever change the app’s icon or rename it on the store, the fallback record will drift. I know this. The right fix is a smarter cache-and-refresh layer that automatically invalidates the local record once the API catches up. I will get to that, but it was not the priority this week. Shipping a working page was.

Civo Cloud Manager v2.1.3: Metadata Only

Civo Cloud Manager also got a version bump this week, to 2.1.3. I want to be upfront about what that means: no new features, no bug fixes. This was a metadata-only release pushed to the Mac App Store to update the listing copy. Screenshots, app description, keywords. The kind of update that is invisible to anyone already using the app but matters for discoverability.

I do these periodically when I notice the listing has drifted from where the app actually is. Civo Cloud Manager has grown quite a bit since the last time I updated the store copy properly, and the description was underselling features that have been there for several versions: the Touch-ID-protected credential store, the S3 file browser, the Object Store pause and resume controls, the live pod log streaming. If someone lands on the listing and reads a description that does not mention those things, that is my fault, not Apple’s.

The commit message says “metadata-only release” and the version bump to 2.1.3 reflects that. App Store Connect requires a new version submission even for copy-only changes, which is one of those Apple rules that always feels slightly absurd but is non-negotiable.

The Scheduled Rebuild Problem, Again

There is a commit in this week’s activity that I have written about before and need to write about again, because it is still not fixed. The YouTube data refresh on the client site built with Astro: I pushed it manually, same as the last time, and the time before that. The site has no scheduled rebuild pipeline. Every refresh is a manual push.

I mentioned this in the September post. I mentioned it again in November. I am mentioning it now because I think leaving it in the record is more honest than quietly fixing it and pretending the problem never persisted this long. The right solution is a cron-triggered build on the hosting side. It is probably two hours of work. I have just kept deprioritising it in favour of things that feel more urgent. That is a decision I keep making, and I should own it plainly.

What This Looks Like from the Outside

If you are considering having a macOS app built, this week is a reasonable illustration of what the ongoing side of that work looks like. Shipping a version is one moment. Keeping it correctly listed, correctly described, and correctly surfaced across multiple places is a continuous low-level effort. The App Store API fallback I built this week would have been easy to skip. The page would have still worked most of the time. But “most of the time” is not a standard I am comfortable with for something a potential client might be looking at. If that kind of attention to the unglamorous parts of software ownership matters to you, take a look at what I offer.

You can find MacBusinessSuite and Civo Cloud Manager on the work page, with direct links to their Mac App Store listings.

Share