Using NSUserDefaults to share states between two view controllers is
no better than using a global variable or a singleton, thus
introducing coupling / complicating testability, and in essence going
against the principle of inversion of control containers (aka
dependency injection). Stick to injecting a model instance and you
could have a method - (void)persistModelData within the model which
can write out to NSUserDefaults or SQLite or any other suitable
persistence medium. - Just my 2c.
On Aug 12, 12:07 am, "
lorenzo7...@gmail.com" <
lorenzo7...@gmail.com>
wrote: