half past noon on new year's eve
EXIF.ER at 4.0, built with Claude and Codex, and the video it dated twelve hours early
On October 6, a review ran a test video through EXIF.ER and got back a file called
2024.12.31_12h30m00s.mov, half past noon on New Year's Eve. The video had been
recorded half an hour after midnight on January 1, 2025. All 569 tests had passed.
EXIF.ER names photos and videos after the moment they were taken, so a wrong date is about the worst thing it can do. It started as a bash script around Phil Harvey's exiftool for my own backups, became a Shortcut, and turned into an app during a one-week Nano Challenge at the Apple Developer Academy. I built it with Claude and Codex over 363 commits, starting in October 2025. Version 4.0 is on the App Store now, on iPhone and iPad, and as far as features go I consider it done.
Building it that way didn't leave me with less to do. Most of my time went into deciding what the app should promise, and then checking whether it actually kept those promises. That week had started with a decision of the first kind.
one photo, two files
A few days earlier, the same photo could leave EXIF.ER as two different files. The app reaches
your library two ways. With full Photos access it reads the library directly; without it, it goes
through the system's photo picker. Through the picker, a camera's IMG_2214.JPG came
out as IMG_2214.jpeg, while the library path wrote the same bytes as
.jpg. The two copies didn't even show the same dates in Files.
Fixing the extension was easy. Deciding which file the app should hand over in the first place wasn't. If you edit a photo in Photos, or correct its date there, the original on disk no longer matches what you see, and a backup tool could reasonably give you either one. That wasn't something the code could decide for me.
On October 4 I picked one. An export is what Photos shows, named from the date inside the file Photos hands over. The app now copies the original only when it's unedited and its date matches Photos, and everything else goes through Photos' own export, on both paths. Live Photos still lose their motion on the way out, and the preview tells you so.
569 tests and a wrong date
The review two days later was Codex going through the whole app with the code frozen, reporting problems without fixing any. Its test video had been recorded at 00:30 on January 1, nine hours ahead of UTC, and the app was set to name files by the time zone where they were taken.
A QuickTime file can carry two creation dates. The movie header, mvhd, stores one in
UTC with no zone attached. The camera also writes com.apple.quicktime.creationdate,
which keeps the local time and its offset. EXIF.ER's reader took the first date it recognized, the
header's, and never got to the better one. With no recorded zone to go on, it fell back to the
device's own, three hours behind UTC, and 15:30 UTC became 12:30 on December 31.
The tests weren't wrong, exactly. Every test video had the same moment in both fields, so none of them could show which one the app was reading.
That one made me anxious, because getting the date right is the whole job. I worked through it
with the model the same way I'd worked through everything else in the app, with code reviews, bug
fixes and usability audits, and the fix landed the next day. The reader now tries the keyed
creation date first, then the older ©day tag, and only then the header, and folder
copies and Photos exports get their video dates from the same function.
It wasn't the first bug like this. In August, a Claude audit found that the year in a filename followed the phone's calendar, so on a phone set to the Thai Buddhist calendar, a photo from 2018 would be named 2561. My phone is Gregorian. I'd never have seen it. Both bugs lived in setups I never use myself, and both turned up because I'd asked a model to go looking.
finished, and what I left out
Since 3.0, EXIF.ER has picked up a preview for Photos exports, saved workflows, custom naming patterns and dated folders, and the build that went to the App Store passed 609 tests. A few things I've decided not to build yet: undoing a whole batch, a share extension, stripping metadata from files. Each would be one more promise to keep.
Next is a Mac version, the same app on a new platform. The New Year's Eve video has a test of its own now, a QuickTime file stamped 00:30 in Tokyo, which the header alone would still put on December 31.