Home/ Questions/Q 6904303
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T08:02:33+00:00

Often times I initialize my model class variables in my AppDelegate so they can

  • 0

Often times I initialize my model class variables in my AppDelegate so they can be used by different ViewControllers without passing their instance across class files. However, every time I import AppDelegate into a .m file to access these variable’s data I feel like I’m doing some wrong.

Is this the the correct way for accessing these variables or should I be doing something differently?

EDIT:
My problem isn’t how to access the variables. I currently use this line of code to get my appDelegate instance:

id appDelegate = [[UIApplication sharedApplication] delegate];

Conceptually, I want to know if this is the accepted way to interact with an application’s model classes. It seems, to me, that an application’s AppDelegate manages the application overall. So it seems counterintuitive to import this class into other classes further down an application’s class chain.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Is this the the correct way for accessing these variables or should I
    be doing something differently?

    You’ll find that different people have different opinions about this. The style that I prefer is to have the app delegate pass the necessary information to the first view controller, and have that view controller pass it on to whatever view controllers it creates, and so on. The main reason for this is that it prevents child view controllers from depending on things that they have no business knowing about.

    If you have some detail editor, for example, you want to be able to pass that editor exactly what it needs to do its work. If you give it that information, the editor is completely flexible — it’ll edit any information that you give it. If the editor knows that it should get its data from some external object, like the app delegate, then it loses some degree of flexibility — it can only get data from the thing that it knows about.

    So, it’s fine to set up your data model in the app delegate. But when it comes to providing access to the model, think: tell, don’t ask. That is, have the app delegate tell the first view controller what model object to use, and have that controller tell the next one, and so on. If you have to ask, you have to know who to ask, and that’s where the dependencies start heading in the wrong direction.

    every time I import AppDelegate into a .m file to access these
    variable’s data I feel like I’m doing some wrong.

    Trust that instinct. Think about why it feels wrong.

    • 0