Trending Articles, Demos and tech notes
Building for One, Part fourteen: four rejections, and Apple were right every time
Building for One, Part one: a calm iPad display for someone living with dementia built a calm daily tablet display for someone in the early stages of dementia. Building for One, Part thirteen: the rejection that made it better told how Apple’s first two rejections gave the app a welcome page, accounts from the tablet and better settings. This last part is about the two rejections that followed, and the email at the end of them.
On 19 October, App Store Connect sent the email every developer waits for: “The following app is ready for distribution.” Daysome 0.6.3, with its household plan, is approved for the App Store. It took four rejections in ten days, and we’d like to mark it, because a lot of small things had to go right to get there, and every one of them made the app better.
TL;DR – Apple were right every time they turned Daysome down, and each rejection left the app more complete than it found it. Patience and politeness got it through, as they always have.
- Details
- Written by: Angus Fox
Read more: Building for One, Part fourteen: four rejections, and Apple were right every time
iPhone 18 Pro Max: Which Features Actually Justify an Upgrade
iPhone 18 Pro Max: A Flagship Built for Selective Upgraders
Apple's iPhone 18 Pro Max arrives as one of the most specification-dense handsets the company has produced, yet its headline advances are unlikely to resonate equally for every iPhone model user. For industry professionals evaluating device refresh cycles and fleet investment decisions, the central question is not whether the hardware is impressive, but whether the improvements are substantive enough to justify the cost relative to the iPhone users already carry.
- Details
- Written by: Angus Fox
Read more: iPhone 18 Pro Max: Which Features Actually Justify an Upgrade
What a Joomla developer learned modernising a WordPress site
I build and maintain Joomla sites. Earlier this year I took on the migration of a members' organisation's WordPress site: old hosting, an ageing PHP version, and a custom theme written in 2012 that nobody had touched in a decade. It is live now, on current WordPress and PHP, and the whole thing took days rather than weeks.
TL;DR – What surprised me was where the difficulty actually sat. I was never unclear about what I wanted. I could describe every outcome precisely. What I could not do was name the thing I was looking for, or guess where WordPress had put it. That gap turned out to be the whole job.
- Details
- Written by: Angus Fox
Read more: What a Joomla developer learned modernising a WordPress site
Building for One, Part five: everybody read it before her
Building for One, Part one: a calm iPad display for someone living with dementia built a calm daily display for someone in the early stages of dementia, and Building for One, Part four: the £200 tablet that just worked put it on a £200 tablet. In between, two parts on turning it into one command that ships to both stores and on how much of the design real tablets proved wrong. This part covers the week after that: twenty-five beta builds, and the same app sitting in three review queues at once.
Almost none of that week was spent on the thing the app does. It was spent on the fact that three different people read this app before the person it is for ever sees it (an app reviewer, a tester, and the family member doing the installing), and each of them needs different words.
TL;DR – Getting those words wrong does not produce a bug report. It produces a rejection, or worse, a person reading something about themselves that nobody meant them to read.
- Details
- Written by: Angus Fox
Read more: Building for One, Part five: everybody read it before her
Building for One, Part three: what a real iPad changed
Building for One, Part one: a calm iPad display for someone living with dementia built a calm daily display for someone in the early stages of dementia. Building for One, Part two: what it costs to buy one command spent two days turning it into one command that ships to both stores. This part is about the afternoon it finally ran on a real iPad, and how much of the design turned out to be wrong.
Not broken, just wrong in the way things are wrong when you have only ever seen them on a desktop display.
TL;DR – A simulator tells you whether something fits. Only a device tells you whether it reads. And only a person tells you whether any of it was the right idea.
- Details
- Written by: Angus Fox
Read more: Building for One, Part three: what a real iPad changed
Building for One, Part two: what it costs to buy one command
Building for One, Part one: a calm iPad display for someone living with dementia ended with an app that ran. A calm iPad display for someone in the early stages of dementia — what day it is, what is happening now, what is next, and what is for tea. Tested, documented, and living entirely on one laptop. If you are less interested in the tooling feel free to skip to Building for One, Part three: what a real iPad changed
TL;DR – Part two is about the two days spent turning that into this:
git push origin v0.1.0-beta1
One command. It runs the audit, builds both platforms, archives and signs iOS against a pinned certificate, signs Android with its own upload key, and delivers to TestFlight and Google Play internal testing. Both stores, from one tag.
- Details
- Written by: Angus Fox
Read more: Building for One, Part two: what it costs to buy one command
Building for One, Part one: a calm iPad display for someone
This is the first part of a build-in-public series about an app we have been thinking about for a year or more, finally started work on, and are still building. It is called Daysome, although the icon reads My Day. It shows one person, on one iPad, what day it is, what is happening now, what is coming next, and what is for tea. That is the whole thing.
We are writing this up as we go rather than after the fact, partly because the interesting decisions are the ones that get forgotten once a product looks finished, and partly because we are looking for a small number of families and care professionals to test it on real hardware. If that might be you, there is a note at the end.
Daysome - a calm iPad display for someone living with dementia


TL;DR – Part one covers the first few days: where the idea came from, why we chose the stack we did, how the requirements arrived, one small development tool that saved more time than anything else we built, and the point at which we put it under version control and pointed it at TestFlight, Apple's app testing system for the App Store.
- Details
- Written by: Angus Fox
Read more: Building for One, Part one: a calm iPad display for someone
When Vendors Retrain on Your Data Without Asking Permission
The Quiet Rewrite: How Vendors Are Claiming Your Data for AI Training

Photo: Angus Fox — via admin.atlassian.com — CC BY 4.0
Across enterprise software, a structural shift is underway. Vendors that once positioned themselves as custodians of customer data are quietly rewriting the terms of that relationship, amending service agreements to permit the use of customer-generated content for AI model training. The mechanism is rarely dramatic. It arrives as a terms-of-service update, or buried in a changelog or communicated through a notification most users dismiss without reading.
TL;DR – You should demand that software agreements include an explicit AI training opt-out that is active by default, not buried in settings or dependent on a user locating a consent toggle.
- Details
- Written by: Angus Fox
Read more: When Vendors Retrain on Your Data Without Asking Permission
Xcode simulators can be very nearly impossible to delete
The Hidden Storage Hog Living Inside Your Mac
If you have been using Xcode for any meaningful stretch of time, there is a good chance your Mac is quietly running out of room — and you may have no idea why. Xcode simulators are one of the most persistent and underappreciated causes of ballooning disk usage on a developer's machine, accumulating gigabytes of data in the background without ever surfacing a single warning or prompt.
The problem compounds itself in two distinct ways. First, simulator runtimes themselves take up significant space — each iOS, watchOS, or other platform simulator you have ever downloaded leaves behind a substantial footprint. Second, Device Support files pile on top of that. These are files Xcode writes to ~/Library/Developer/Xcode/iOS DeviceSupport and equivalent directories for every device and OS version combination you connect or target. Neither category cleans itself up reliably, and neither is especially visible in day-to-day use.
To put a real number on it: I freed up 150GB of disk space after running cleanup commands on a machine with. 1TB SSD. That is not years of neglect — that is less than a year of ordinary Xcode use silently consuming the equivalent of thousands of photos or hours of video.
- Details
- Written by: Angus Fox
Read more: Xcode simulators can be very nearly impossible to delete
Disk full on a Mac? Check for old iOS backups hogging space
Why iOS Backups Are Silently Eating Your Mac's Storage
Every time you connect an iPhone or iPad to your Mac and sync it through iTunes (on older macOS versions) or Finder (on macOS Catalina and later), your Mac quietly creates a full local backup of that device. These backups are designed to be a safety net, but over the years, they have a habit of becoming a hidden storage crisis.
The problem compounds with each device upgrade. When you move from one iPhone to the next, a new backup is created for the new device, but the old backup is rarely deleted automatically. After two, three, or four device cycles, you can easily have a collection of backups sitting on your Mac that you have completely forgotten about. Each individual backup can run to tens of gigabytes depending on how much data, photos, and app content was on the device at the time it was created.
- Details
- Written by: Angus Fox
Read more: Disk full on a Mac? Check for old iOS backups hogging space
Rotating the root of trust — break-glass key rotation
If you sign your extension’s subscription-validation responses with an RSA key, that private key is the root of trust for every copy you’ve ever shipped. So what do you do when it might have been exfiltrated? You can’t just mint a new one and swap it in — the instant you do, every customer’s extension rejects the new signature and in our case drops to the free tier limiting functionality they paid to subscribe to.
TL:DR – This is how I rotated a possibly-compromised signing key across a live Joomla subscription system without breaking the field, plus the one design idea that made it safe.
- Details
- Written by: Angus Fox
Read more: Rotating the root of trust — break-glass key rotation
- Why Chrome couldn't reach my LAN web server on macOS, and
- GitHub Copilot’s Data Policy Shift: What It Means for
- From Local Builds to Production DevOps: Automating Joomla
- Running Gitea with Let’s Encrypt on macOS via Homebrew
- Running Homebrew Apache with Let's Encrypt SSL on macOS
- Beyond the glimmer of Liquid Glass is a sparkle concealing
- Grab some useful apps with Amazon Coins before they expire!
- Disk Recovery Success Using GNU ddrescue on Ubuntu Linux
- All-new Apple Watch Series 12 or the Ultra 4?
- Headless Remote Desktop on Ubuntu - working reliable
- Use and scroll with Apple Magic Mouse on Windows 11 PC
- New Cassette deck in 2026