Sure, but that was an isolated mistake, whereas using NSLocalizedString() just becomes habit after a while.

It's jarring when you see hard-coded English strings in any iOS code. Android does a much better job of pushing developers to localizing strings.

One big thing I don't like about iOS is even if you have a base language, you need to duplicate all strings in any subsequent languages. (I often have a "US English" and "Australian English", so trivial changes require changes in two files).

On Android, the language files extend the base file, so you can just override favourite/favorite labour/labor type strings without having to duplicate everything.

(Obviously you can script / auto-generate language files, but that's not the default position).