Configurations in, settings out
In designing iOS, Apple created a somewhat controversial and confusing design decision with regards to application settings.
iOS has been created from the ground up with the fundamental philosophy that instructional manuals and help menus are a design constraint of the past. This requires that our work be somewhat limited in feature set, in order to minimize the barrier of entry. To accommodate for this sense of minimalism, we must often limit the number of settings or configurations presentable inside of an app.
Through the developer SDK, Apple offered the ability for an app to store its configurable settings inside of the actual Settings application, as opposed to inside the application itself. So if the user needed to change a specific setting, they were required to leave the application, go to Settings, and make the appropriate change.
As one can imagine, this leads to a bit of user confusion. What's the best way to go about managing this and eliminating...
