futuretap/InAppSettingsKit

This iOS framework allows settings to be in-app in addition to or instead of being in the Settings app.

View on GitHub ↗Jump to charts ↓

futuretap/InAppSettingsKit has 3k+ stars and 500+ forks on GitHub, is written in Objective-C, and was last pushed on May 4, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on January 12th, 2010
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 539
Total Stargazers: 3,214 (+0)
Total Subscribers: 101 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.6 days
Mean response time: 119.5 days
90th percentile: 73.2 days
Tracked items: 21

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 440 days
Stale 30+ days: 3
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • CouldNotReproduce (1)
  • FeedbackWanted (1)
  • MoreDetailsNeeded (1)
  • NiceToHave (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

InAppSettingsKit is an iOS framework that enables developers to present application settings within the app itself rather than exclusively through the system Settings application.

The framework addresses the limitation that iOS Settings app integration requires users to leave the application to adjust preferences. InAppSettingsKit provides an alternative by allowing settings interfaces to be built and displayed directly within the app. It works by offering UIKit components and a settings editor that developers can integrate into their application's user interface, giving users immediate access to configuration options without navigation away from the app.

Developers should choose this framework if their iOS application needs flexible settings management that keeps users engaged within the app experience. It suits projects where in-app settings are preferable to system Settings integration, or where applications want to offer both options simultaneously. The framework is built on UIKit, making it appropriate for iOS and iPad applications using that framework.

The project maintains active development with regular updates to its codebase. The framework has evolved through multiple major versions, indicating sustained refinement of its API and capabilities. Development activity shows consistent engagement with the codebase through commits and updates to keep the tool functional with current iOS development practices.