Presumably it got developed as such, and it never got prioritized before release.

"Okay we've finished all the must-haves just in time for our release deadline but the name for our app in our code isn't really configured correctly."

"How long will it take to fix?"

"Maybe a week to update our CI environments and be confident that there aren't any regressions related to dependencies on the thing that we're changing, but we can also fix some other issues in parallel."

"What effect will changing it have?"

"Well it will conform with best practice and won't confuse future developers."

"What user-facing change will it have?"

"None."

"Nope, not worth delaying release by a week for."

I get this for a scrappy startup trying to move fast. But this app (pretty decent, btw) is 10+ years old.

It's effectively impossible to fix this once it's been shipped, though. The bundle ID is the fundamental identifier of the app to the whole system. If they were to change it, they would end up with a completely separate app in the app store. They would have no way (at least no way that's not nasty and convoluted) to move user data from the old one to the new one.

I'm very surprised Apple doesn't enforce the reverse-DNS nature of these IDs and allow all sorts of jumbled strings, let alone not verifying that your in fact own the domain.