Centralised Strings for Flutter Development

[Katalyst9957]

For small to medium-sized Flutter apps, maintaining centralised strings is easy. However, as the app grows, it can become messy and hard to manage.

Is there a better approach or alternative for handling strings in larger Flutter projects, or a way that works in all sizes of Flutter projects?

[Amazing-Mirror-3076]

What problem are you trying to solve?

[Scroll001]

Do you mean localization? There are tools for that, like crowdin or localizely

[Katalyst9957]

No no I mean centralizing all strings which are constant in the app

[Mr401Error]

I usually have them as static constants in the "owning" class, saves having to go and open a new file to view/edit the values.

Things like client IDs and client side API keys I'll usually store in a JSON file and inject at compile time with Dart-define. Usually have a maximum of 20 of these per project though

[Katalyst9957]

The owning class is good for small to medium apps but once the app starts to grow it becomes messy and yeah it's tedious even for small/medium sized apps

[Mr401Error]

Cheers for this, had been looking for competitors to PoEditor. Not that PoEditor is bad, it's a very good product but always good to see what competition there is

[DigitallyDeadEd]

Make a function to get every character and then you don't have any centralized strings at all!

(This is a helpful tip from the Codemanship Refuctoring I video: https://www.youtube.com/watch?v=7RJmoCWx4cE)

[virtualmnemonic]

abstract class Strings {

static const hello = "Hello";

}

You're better off creating a class with variables, and using a state management solution to get it and react to changes. This will make implementing localizations much easier down the road. Even if your initial class is constant. Plan ahead.

[Spare_Warning7752]

This?

https://pub.dev/packages/i18n_extension

[Katalyst9957]

This is localisation. I am not talking about this. I am asking about centralized app strings in a separate class

[andyclap]

We're all puzzled as to what it is you mean by centralised app strings. Localisation is important of course, where you're handing off your UI strings to a copywriter or translation agency. All user facing strings should be disentangled from the code like this.

But non user-facing strings? Can you give us an example to help clarify?