What is it?

InAppSettingsKit is an open source solution to to easily add in-app settings to your iPhone apps. It uses a hybrid approach by maintaining the Settings.app pane. So the user has the choice where to change the settings. More details about the history of this development on the FutureTap Blog and the Edovia Blog.

How does it work?

To support traditional Settings.app panes, the app must include a Settings.bundle with at least a Root.plist to specify the connection of settings UI elements with NSUserDefaults keys. InAppSettingsKit basically just uses the same Settings.bundle to do its work. This means there's no additional work when you want to include a new settings parameter. It just has to be added to the Settings.bundle and it will appear both in-app and in Settings.app. All settings types like text fields, sliders, toggle elements, child views etc. are supported.

The License

We released the code under the liberal BSD license in order to make it possible to include it in every project, be it a free or paid app. The only thing we ask for is giving the original developers some credit. The easiest way to include credits is by leaving the "Powered by InAppSettingsKit" notice in the code. If you decide to remove this notice, a noticeable mention on the App Store description page or homepage is fine, too. To gain some exposure for your app we suggest adding your app to our list.

How to include it?

The source code is available on github. A sample app shows how to integrate InAppSettingsKit into an application.

Depending on your project it might be needed to make some changes in the startup code of your app. Your app has to be able to reconfigure itself at runtime if the settings are changed by the user. This could be done in a -reconfigure method that is being called from -applicationDidFinishLaunching as well as in the delegate method -settingsViewControllerDidEnd: of IASKSettingsViewController.


The intention of InAppSettingsKit was to create a 100% imitation of the Settings.app behavior. However, we added some bonus features for extra flexibility.

Custom inApp plists

Since iOS 4 Settings plists can be device-dependent: Root~ipad.plist will be used on iPad and Root~iphone on iPhone. If not existent, Root.plist will be used. InAppSettingsKit adds the possibility to override those standard files by using ".inApp.plist" instead of ".plist". Alternatively, you can create a totally separate bundle named "InAppSettings.bundle" instead of the usual "Settings.bundle". The latter approach is useful if you want to suppress the settings in Settings.app.

In summary, the plists are searched in this order:

  • InAppSettings.bundle/FILE~DEVICE.inApp.plist
  • InAppSettings.bundle/FILE.inApp.plist
  • InAppSettings.bundle/FILE~DEVICE.plist
  • InAppSettings.bundle/FILE.plist
  • Settings.bundle/FILE~DEVICE.inApp.plist
  • Settings.bundle/FILE.inApp.plist
  • Settings.bundle/FILE~DEVICE.plist
  • Settings.bundle/FILE.plist

Different in-app settings are useful in a variety of situations. For example, Where To? uses this mechanism to change the wording of "At next start" (for resetting confirmation dialogs) to be appropriate if the app is already running.

Variable font size

The labels in the settings table are displayed in a variable font size, especially handy to squeeze-in long localizations (beware: this might break the look in Settings.app if labels are too long!).


InAppSettingsKit adds a new element that allows to open a specified URL using an external application (i.e. Safari or Mail). See the sample Root.inApp.plist for details.


The custom IASKMailComposeSpecifier element allows to send mail from within the app by opening a mail compose view. You can set the following (optional) parameters using the settings plist: IASKMailComposeToRecipents, IASKMailComposeCcRecipents, IASKMailComposeBccRecipents, IASKMailComposeSubject, IASKMailComposeBody, IASKMailComposeBodyIsHTML. Optionally, you can implement

- (NSString*)mailComposeBody;

in your delegate to pre-fill the body with dynamic content (great to add device-specific data in support mails for example). An alert is displayed if Email is not configured on the device.


InAppSettingsKit adds a IASKButtonSpecifier element that allows to call a custom action. Just add the following delegate method:

- (void)settingsViewController:(id)sender buttonTappedForKey:(NSString*)key

The sender is always an instance of IASKAppSettingsViewController, a UIViewController subclass. So you can access its view property (might be handy to display a UIActionSheet) or push another UIViewController. The key corresponds to the "Key" attribute in the Settings plist (useful if you wanna call the same method for different keys). See the sample app for details.

Please note, this API changed in commit 6591d1. In prior versions, a class method specified in the plist was used. The old behaviour is still supported but deprecated (and it leaks memory).

The sender and key parameters are optional. The sender is always an instance of IASKAppSettingsViewController, a UIViewController subclass. So you can access its view property (might be handy to display a UIActionSheet) or push another UIViewController. The key corresponds to the "Key" attribute in the Settings plist (useful if you wanna call the same method for different keys). Please note, the action method is a class, not an instance, method because we can't reference object instances in the plist. See the sample app for details.


The FooterText key for Group elements is available in system settings since iOS 4. It is supported in InAppSettingsKit as well. On top of that, we support this key for Multi Value elements as well. The footer text is displayed below the table of multi value options.


You can specify your own UITableViewCell within InAppSettingsKit by using the type IASKCustomViewSpecifier. A mandatory field in this case is the "Key" attribute. Also, you have to support the IASKSettingsDelegate protocol and implement these methods:

- (CGFloat)tableView:(UITableView*)tableView heightForSpecifier:(IASKSpecifier*)specifier;
- (UITableViewCell*)tableView:(UITableView*)tableView cellForSpecifier:(IASKSpecifier*)specifier;

Both methods are called for all your IASKCustomViewSpecifier entries. To differentiate them, you can access the "Key" attribute using specifier.key. In the first method you return the height of the cell, in the second method the cell itself. You should use reusable UITableViewCell's. There's an example in the Demo app.

Custom Group Header Views

You can define custom headers for PSGroupSpecifier segments by adding a "Key" attribute and implementing these methods in your IASKSettingsDelegate:

- (CGFloat)tableView:(UITableView *)tableView heightForHeaderForKey:(NSString*)key;
- (UIView *)tableView:(UITableView *)tableView viewForHeaderForKey:(NSString*)key;

The behaviour is similar to the custom cells except that the methods get the key directly as a string, not via a IASKSpecifier object. (The reason being that custom group header views are meant to be static.) Again, check the example in the demo app.

Custom ViewControllers

For child pane elements (PSChildPaneSpecifier), Apple requires a "file" key that specifies the child plist. InAppSettingsKit allow to alternatively specify IASKViewControllerClass and IASKViewControllerSelector. In this case, the child pane is displayed by instantiating a UIViewController subclass of the specified class and initializing it using the init method specified in the IASKViewControllerSelector. The custom view controller is then pushed onto the navigation stack. See the sample app for more details.

Settings Storage

The default behaviour of IASK is to store the settings in [NSUserDefaults standardUserDefaults]. However, it is possible to change this behaviour by setting the settingsStore property on an IASKAppSettingsViewController. IASK comes with two stores implementations : IASKSettingsStoreUserDefaults (the default one) and IASKSettingsStoreFile, which read and write the settings in a file of the path you choose. If you need something more specific, you can also choose to create your store.

The easiest way to create your own store is to create a subclass of IASKAbstractSettingsStore. Only 3 methods are required to override. See IASKSettingsStore.{h,m} for more details.


There's a kIASKAppSettingChanged notification that is sent for every changed settings key. The object of the notification is the userDefaults key (NSString*). The userInfo dictionary contains the new value of the key.

Subclassing notes

If you'd like to customize the appearance of InAppSettingsKit, you might want to subclass IASKAppSettingsViewController and override some UITableViewDataSource or UITableViewDelegate methods. If you do subclass, make sure to override the -initWithNibName:bundle: method in any case:

- (id)initWithNibName:(NSString *)nibNameOrNil bundle:(NSBundle *)nibBundleOrNil {
    return [super initWithNibName:@"IASKAppSettingsView" bundle:nibBundleOrNil];

More information

In the Dr. Touch podcast and the MDN Show Episode 027 Ortwin Gentz talks about InAppSettingsKit.