Been googling for info on this and found the [Best practice using NSLocalizedString - Stack Overflow](http://stackoverflow.com/q/9895621/1380781) question. 

Are there any suggestion in this that would be worth it for us to adopt?
Do you think any of what is mentioned there is worth the trouble?

For example:

* Group the different UI text constants in the same `.h` file? Could allow for easier maintenance, identification of possible reuse cases (and maybe of missing or old translations?)

* Using non literal text for the actual key so that it doesn't become "weird" if we later change the UI text?
```objc
/*
So we would have something like this:
*/
static NSString *const NCSignUpFirstViewControllerTitle = @"SIGN_UP_TITLE"; // code
"SIGN_UP_TITLE" = "Sign Up"; // en
"SIGN_UP_TITLE" = "Registo"; // pt
/*
Instead of this:
*/
static NSString *const NCSignUpFirstViewControllerTitle = @"Sign Up"; // code
"Sign Up" = "Sign Up"; // en
"Sign Up" = "Registo"; // pt
```

* Using `#define` for the entire localized expression instead of `const` just for the key?
```objc
/*
i.e. doing something like this:
*/
#define NC_SIGN_UP_TITLE NSLocalizedString(@"Sign Up", nil); // code
NSLog(@"%@", NC_SIGN_UP_TITLE); // usage
/*
i.e. instead of doing:
*/
static NSString *const NCSignUpTitle = @"Sign Up"; // code
NSLog(@"%@", NSLocalizedString(NCSignUpTitle, nil)); // usage
```