Seaworthy is in the App Store. That is the headline for this week, and it is the one I want to lead with, because getting an app from “mostly done” to “actually listed” involves a surprisingly long tail of work that has nothing to do with the app itself. Alongside that, I pushed a legal copy update across four sites, clarifying how project documents are stored depending on where a client is based. Not glamorous, but it is the kind of thing that matters when you are working with businesses in Europe.
Seaworthy Goes Live
The commit message from this week says it plainly: Seaworthy is now listed as a live app. That is a one-liner in a changelog, but it is the result of weeks of work that included Apple review, provisioning profile wrangling, and the usual App Store Connect paperwork that never gets faster no matter how many times you have done it.
Seaworthy is a macOS app. I am keeping the full feature write-up on the app page rather than reproducing it here, but the short version is that it is a native Mac client focused on a specific workflow problem I kept running into myself. Building it was the easy part, relatively speaking. Getting it into the store is the part where Apple’s signing and notarisation requirements extract their toll.
The actual submission went smoothly this time, which I am almost suspicious of. Apple review cleared without a single request for information. No rejection, no metadata quibble. It just went through. I have had reviews drag on for days over things that turned out to be nothing, so a clean pass is genuinely worth noting, even if it means I have no war story to tell.
What I did have to spend time on was the App Store listing itself. Screenshots at the right sizes for every supported display, a description that explains what the app does without sounding like a press release, and a subtitle that fits in 30 characters while still meaning something. That last constraint is more annoying than it sounds. You keep cutting words until the thing barely parses as English, then you cut one more word and it suddenly reads well again. I went through four versions of the subtitle before I landed on one I was happy with.
The listing is live now. You can find it linked from the app page on this site.
The MailerLite Cleanup and What Replaced It
While I was in the site repos, I also removed the last traces of MailerLite from the personal portfolio site. I switched newsletter tools a while back and apparently left some stale script tags and configuration references behind. Finding them required a search across the whole repo rather than a targeted edit, which tells me the original integration was more spread out than I had realised. That is the honest version: I thought I had cleaned this up, and I had not.
No functional impact. Visitors would not have noticed anything. But dead code in a static site has a way of accumulating until it becomes confusing, and removing it felt worth the ten minutes it took.
Data Routing and the Legal Copy Update
The other thread running through this week was a copy update I pushed to four separate sites, including the Civo Cloud Manager marketing site and both of my own sites. The change was specific: I added a clarification to the “Why LLC” legal section explaining how project documents are handled depending on where a client is based.
The rule I settled on is straightforward. Project documents for clients based in Europe are stored in Germany, via Microsoft 365. For clients elsewhere, they sit in the US. That is not a new practice, it is just one I had not written down clearly enough in the public-facing legal copy. Version 1.4.0 of that section is what I pushed across all four repos.
Making the same content change in four separate repos in one pass is the kind of task that sounds easy and is mostly easy, but it does require enough attention to make sure each site’s phrasing is idiomatic for its own audience. The Civo Cloud Manager site has a more technical readership than the portfolio site. The legal section on each needed to say the same thing in a way that fit its context. I spent longer on the wording than I expected to.
This is also a good illustration of why I keep asking myself whether four separate Astro sites is the right architecture for this setup. A shared content layer with per-site rendering would make updates like this a single commit. For now, I am living with the repetition, but it is a real friction point.
What Hiring a Developer Actually Looks Like Behind the Scenes
If you are considering having a custom app built, this week is a reasonable illustration of what a solo developer’s time actually looks like at the point where something ships. The code was done. What remained was App Store compliance, listing copy, legal documentation, and cleanup in the repos. None of that shows up in a feature list. All of it takes real time.
That context is part of what I try to give you through these posts. If you want to talk through what a project like this might look like for your business, the contact page is the right place to start.
Seaworthy is live on the Mac App Store. The work page has the link and the full description of what the app does.