Google really fucked up with localization for Flutter!
We need to create a getter for each translated string? For real!!

Please tell me I understood it wrong :|

I saw into the docs. Fucking YES.

Sounds like overusing OOP ideas where they don't really belong.

I used languages in my own local JSON files translation
and just define the file in the main and switch the languages in my App

@mohammedbabelly @powerfulparadox @stop

I ended up going the iOS way:
CoreLocalization.of(context)
.translate('label_register')

in Swift we do:
NSLocalizedString(name: "label_register", comment:"")

Found it to be easier but in React or Android it is easier as I don't have to memorize, I just choose from the list