# rsattar/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).

Repository: https://github.com/rsattar/ClusterPrePermissions
Canonical: https://ross.abutalabs.com/products/clusterprepermissions
Language: Objective-C
License: MIT
License Family: permissive
Last push: 2017-09-26T14:22:39+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 4531, "days_push": 3263, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1189, forks 103 (observed 2026-08-28T04:03:55.423732+00:00)

## What it is
ClusterPrePermissions is an Objective-C library for iOS that shows a custom pre-permission dialog before triggering the system permission alert for photos, camera, microphone, contacts, events, and location. It helps developers avoid burning their one-time system permission request by asking users in their own UI first.

## Use cases
- ask users for photo library access with a custom dialog before the iOS system alert
- improve permission grant rates by explaining why access is needed first
- request contacts or microphone access at a better time in the app flow
- avoid permanently losing permission access when users habitually tap Don't Allow
- wrap camera and location permission requests with a pre-prompt

## When to choose
- you're building an iOS app in Objective-C or Swift that needs photo, camera, microphone, contacts, events, or location access
- you want to maximize permission grant rates with a custom pre-prompt dialog
- you want a lightweight, drop-in utility via CocoaPods or source files

## When to avoid
- you're building for Android or non-Apple platforms
- you need permissions beyond the six supported types (e.g., notifications, Bluetooth)
- you're starting a new project and prefer a Swift-native or more actively maintained permission library

## Facets
- artifact type: library
- maturity: maintenance
- function: auth, ui-components, developer-tools
- domain: mobile-development
- platform: cross-platform
- tags: pre-permissions, objective-c, ios-permissions, cocoapods, user-consent, user-experience, ios, mobile

## Member repositories
- rsattar/ClusterPrePermissions (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:03:55.423732+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:23:20.482417+00:00, confidence not recorded.
  - readme: https://github.com/rsattar/ClusterPrePermissions (fetched 2026-08-28T04:03:55.423732+00:00, sha b1d33abb0f4a)
- Data as of 2026-08-30T08:39:29.467469+00:00.