I started InAppSettings about 3 months ago. On monday a friend told me about a similar project called InAppSettingsKit. I of course was curious how they went about solving the same problem, and how the two projects stacked up.
After looking at both of them here’s what I found:
UPDATE: Compile size and Build times have been added.
*The Settings.bundle from InAppSettings contains almost every combination of specifiers and values, InAppSettingsKit crashed displaying this Settings.bundle.
*UPDATE: InAppSettingsKit was updated so I was able to fully test the Settings.bundle from InAppSettings. However InAppSettingsKit does not display all the combinations of the specifiers and values correctly.
**Both projects include a sample/test Xcode project, the size of these Xcode projects is not reflected in these values.
***UPDATE: The compile size and build time was derived from a blank ‘window based’ project. The results are the build time and .app size for each project, minus the size and build time of the fresh Xcode project.
.app size with each project - .app size with a fresh window based app
time xcodebuild with each project - time xcodebuild with a fresh window based app
InAppSettingsKit uses nibs, this is one of the reasons the compiled .app is larger. Both apps were built in release mode which has a compile xibs step, this is why InAppSettingsKit’s build time is longer. But we’re talking about microseconds and kilobytes :)
Here is a comparison of the Settings.bundle from InAppSettings. Unfortunately, I was unable to take more screenshots because scrolling down caused InAppSettingsKit to crash.
UPDATE: InAppSettingsKit no longer crashes when displaying the Settings.bundle from InAppSettings.
The rest of the comparisons use the Settings.bundle from InAppSettingsKit.
Both InAppSettings and InAppSettingsKit implement the keyboard types specified in the PSTextFieldSpecifier spec, however the Settings app does not.
Thanks David for this comparison. I’ve fixed the crashing issues in InAppSettingsKit right away and will look into the other differences more thoroughly soon. The source code size difference is probably due to IASK having XIBs whereas your solution does all in code. I assume the final app bundle size won’t be that different after XIBs are compressed to NIBs.
[...] popped up this week that both show an in-app view controller to make changes in the Setting.bundle. A comparison chart and screenshots by the author of [...]
[...] comparison chart and screenshots by author of InAppSettings: http://inscopeapps.com/blog/inappsettings-vs-inappsettingskit/ « Custom URL Scheme Getting the Subclasses of an Objective-C Class [...]
[...] UPDATE: And as so strangely often seems to happen, there’s been almost simultaneously released a similarly targeted project called InAppSettingsKit. The no doubt scrupulously fair and balanced InAppSettings author has a detailed comparison here. [...]
[...] InAppSettings lives over at bitbucket, made by InScopeApps. I chose it over InAppSettingsKit, because it was just that little bit easier to use. As far as I see, they both do almost exactly the same thing. There is a head to head VS here. [...]