Flutter - Application-Wide 'Services'
No, this methodology is fine as there's one instance only, which any change to its parameters will immediately be reflected in the other widgets/classes that use it. And it can also be accessed from anywhere in your code. One of the other great points about this approach is that you don't have to update the State of any Stateful widget which depends on this object explicitly, any change on it will fire the setState() function.