Hi I have multiple localized text files. I chose JsonUtility to serialize and parse them. All good. Help me brainstorm: (A) Structure - what is the recommended way to structure the data, to help redistribution? (B) Redistribution - whats the best way to redistribute the data inside the app? Also, reaction of app systems to change in data (change in language). I'm looking on suggestion for implementation. Some issues i would like to solve: (1) Tight coupling between the class that needs the data and the target data: I chose to structure the data as nested classes (branches), and public strings (leaves). This way, when parsed, i can do this to locate a text string (data bit / leaf) using code: string fileExists = localizedData.ui.validation.fileExists; which fetches a string: File with that name already exists! This way, i get code hints (yay!), reduce the clutter when asking for data in code and get a gc-free lookup (this is of importance to me). However this way also, the asking class needs to know of the data structure, thus there is a tight coupling between the fetching class and the data, which i dislike very much. Some 'solutions' to (1) that i can think of: (1A) path string to data inside Inspector, and Reflection inside the class to get to the data. Something like this inside inspector of the class: "ui/validation/fileExists" Then use Reflection to get the actual string. I dislike this, because it creates garbage every time i ask for a simple string! (1B) Using SimpleJSON. I can use string inside inspector (1A) with this. Example: Code (CSharp): var N = JSON.Parse(the_JSON_string); var fileExistsString = N["ui"]["validation"]["fileExists"].Value; EDIT: this might be cached arrays/dictionaries, which would be GC-free and exactly what i need (TODO: test). @Bunny83 Pog? (1C) Serialized dictionary, flat leaf structure. Leaf = text string. GC-free (good), can supply key inside inspector to remove tight coupling (good), RIP code-hints (meh), flat structure with long keys/property names to store all the data (meh). Also i can see, for example, when adding a function to say OnValueChanged of a UI.Toggle inside an inspector, the inspector UI actually let's me 'browse' the classes, their subclasses (..), and methods. If i could use this kind of functionality to set the path to the target data string via inspector for the target class, that would be awesome. And i guess i can do that - using reflection? Aww.. then each time i ask for such string, i get garbage. Right? I can gc-free fetch via code - since the data is strongly typed - but don't want to write the path to data inside the code! So what you folks using in terms of structure / serializer / storage type / pattern that you came to like? In fact that is all for now. Brainstorming (B) is still welcome, but (A) and (1) is much more important, so let's keep it simple.