In general, we recommend that you avoid doing your own localisation infrastructure. For an explanation as to why, see this post.
If you choose to do this anyway, you will definitely end up needing a bunch of extra code. There’s two basic strategies you could use:
Subclass the common UI elements and have those subclasses talk to your localisation infrastructure to decide what to display
Have your localisation infrastructure ‘reach in’ to the on-screen UI to fix up the localisation
All of this will require you to work against, rather than with, the frameworks, and you will encounter problems you can’t solve. Hence the recommendation with which I started this response.
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"