How do I use ISHPermissionKit with SwiftUI?

Since ISHPermissionKit uses UIKit view controllers, you need to wrap it in a UIViewControllerRepresentable for SwiftUI. The sample app is in Objective-C, so you'll have to adapt the view controller presentation in SwiftUI manually.

Is ISHPermissionKit better than requesting permissions directly in iOS?

ISHPermissionKit is better when you need to explain permissions before system dialogs or handle sequential requests. For simple, one-off permissions, direct iOS APIs are simpler and may suffice without the framework overhead.

What happens if a user denies permission with ISHPermissionKit?

The framework tracks permission states and allows custom handling through delegate methods. You can prompt users again later or guide them to settings, but it doesn't automate retries beyond the initial sequence without additional code.

Why are build flags necessary in ISHPermissionKit?

Build flags ensure only the permission categories you use are compiled, preventing App Store rejections for containing unused sensitive code. This is critical for compliance with Apple's privacy guidelines, as explained in the installation instructions.

How can I add a new permission category to ISHPermissionKit?

You need to subclass ISHPermissionRequest, implement permissionState and requestUserPermissionWithCompletionBlock methods, and wire it up in ISHPermissionRequest+All. The README provides detailed steps for contributors, including updating build flags and CocoaPods subspecs.

Does ISHPermissionKit support dark mode in custom UI?

No, ISHPermissionKit doesn't impose any UI styles; developers are responsible for making their custom view controllers support dark mode and other iOS features, as the framework leaves all chrome design to the developer.

Is ISHPermissionKit still actively maintained?

Based on the README, there's a roadmap with missing features, and updates might be infrequent. Check the GitHub repository for recent commits and issue activity to gauge current maintenance status.

Open-Awesome

ISHPermissionKit

NOASSERTIONObjective-C2.1.2

A unified iOS framework for requesting user permissions with custom UI and sequential prompts.

Visit Website GitHub

614 stars46 forks0 contributors

What is ISHPermissionKit?

ISHPermissionKit is an iOS framework that provides a unified and polite way to request user permissions for accessing sensitive data and device features like location, contacts, photos, and health data. It solves the problem of abrupt system permission dialogs by allowing developers to present custom explanatory UI first, improving user understanding and acceptance rates.

Target Audience

iOS developers building apps that require multiple sensitive permissions, especially those needing fine-grained control over permission request timing, sequencing, and user interface.

Value Proposition

Developers choose ISHPermissionKit because it offers a complete solution for permission management with custom UI support, sequential requests, and build-time safety features that prevent App Store rejections, all through a consistent API across all iOS permission types.

Overview

A polite and unified way of asking for permission on iOS

Use Cases

Best For

Onboarding flows that require multiple permissions at app launch
Apps needing to explain why permissions are required before showing system dialogs
Implementing permission request sequences (e.g., location then motion for fitness apps)
Maintaining custom UI/UX design while handling permission requests
Ensuring App Store compliance by excluding unused permission code
Supporting older iOS versions while using newer permission APIs

Not Ideal For

Apps needing only simple, out-of-the-box permission dialogs without custom UI
Projects built exclusively with SwiftUI preferring native permission handling
Teams requiring real-time permission state monitoring without manual implementation
Small apps with minimal permissions where the framework's setup overhead isn't justified

Pros & Cons

Pros

Full UI Customization

Developers provide their own view controllers for permission explanations, maintaining complete design control without imposed styles, as emphasized in the philosophy.

Sequential Request Handling

Supports asking for multiple permissions in a sequence, ideal for complex onboarding flows like fitness apps that need location and motion data together.

Build-Time Safety

Uses preprocessor flags to include only needed permissions, preventing App Store rejections for unused sensitive code, a key feature highlighted in the installation section.

Broad iOS Compatibility

Compiles with iOS 11 SDK but deploys back to iOS 9, automatically skipping unsupported categories on older versions, ensuring wider device support.

Cons

Complex Setup Process

Requires manual configuration with .xcconfig files and build flags, which can be error-prone and time-consuming compared to simpler dependency managers.

Incomplete Feature Set

The roadmap admits missing features like resetting state correctly and permission monitoring with NSNotifications, limiting dynamic permission management.

UIKit-Centric Design

Heavily relies on UIKit view controllers, making integration with SwiftUI projects cumbersome and less idiomatic for modern iOS development.

Frequently Asked Questions

Related Projects

SPPermissions

Universal API for request permission and get its statuses.

Stars5,814

Forks481

Last commit1 year ago

Permission

A unified API to ask for permissions on iOS

Stars2,890

Forks321

Last commit4 years ago

ClusterPrePermissions

Cluster's reusable pre-permissions utility that lets developers ask the users on their own dialog for photos or contacts access, before making the system-based request. This is based on the Medium post by Cluster describing the different ways to ask for iOS permissions (https://medium.com/p/96fa4eb54f2c).

Stars1,188

Forks103

Last commit9 years ago

AREK

AREK is a clean and easy way to request any kind of iOS permission (with some nifty features 🤖)

Stars949

Forks61

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub