How do I set up SwiftRater in a SwiftUI app?

Since SwiftRater requires AppDelegate, create a custom AppDelegate class using @UIApplicationDelegateAdaptor in SwiftUI, then configure SwiftRater there as shown in the README's SwiftUI example.

Can SwiftRater work on macOS?

Yes, SwiftRater supports both iOS and macOS, with similar usage and prompts tailored for each platform's App Store, as indicated in the README's requirements and demo.

SwiftRater vs Apple's StoreReviewController: which is better?

SwiftRater offers more configurable triggers and manual control, while StoreReviewController is built-in but less flexible. Choose SwiftRater for fine-grained timing, but note it may have limitations on newer iOS versions.

How to test review prompts without waiting for actual usage days?

Enable debug mode in SwiftRater, which makes prompts appear every time you call check(), allowing you to simulate conditions during development without delays.

Does SwiftRater let me customize the look of the review dialog?

No, SwiftRater only allows text customization; the UI is handled by iOS's system prompt, so you cannot change colors, layout, or add custom elements beyond the standard alert.

What happens if SwiftRater can't find my app's App Store ID?

SwiftRater attempts to fetch it from the bundle ID automatically, but you can explicitly set the appID property to avoid issues, especially if the bundle ID is incorrect or during testing.

Open-Awesome

SwiftRater

MITSwift2.2.2

A pure Swift utility for iOS/macOS apps that reminds users to review the app on the App Store.

GitHub

379 stars49 forks0 contributors

What is SwiftRater?

SwiftRater is a Swift library for iOS and macOS apps that automates the process of asking users to leave App Store reviews. It solves the problem of low review rates by prompting users at strategic moments based on customizable criteria like usage frequency and significant actions.

Target Audience

iOS and macOS developers who want to increase App Store reviews for their apps with minimal code and configurable timing.

Value Proposition

Developers choose SwiftRater because it's written in pure Swift, offers fine-grained control over prompt triggers, supports both UIKit and SwiftUI, and integrates easily via SPM, CocoaPods, or Carthage.

Overview

A utility that reminds your iPhone app's users to review the app written in pure Swift.

Use Cases

Best For

Increasing App Store review rates for iOS apps
Implementing smart review prompts based on user engagement
Adding customizable review reminders in macOS applications
Testing review prompt behavior during development with debug mode
Localizing review prompts for specific countries or languages
Triggering review requests after significant user actions

Not Ideal For

Apps not distributed through the App Store (e.g., enterprise or TestFlight-only builds)
Projects requiring fully custom review prompt UI beyond text localization
Teams needing server-side control to adjust review prompt logic dynamically
SwiftUI-only apps without an AppDelegate, as setup requires AppDelegate integration

Pros & Cons

Pros

Easy Integration

Supports SPM, CocoaPods, and Carthage, with setup requiring just a few lines in AppDelegate or SwiftUI adaptor, as shown in the README examples.

Flexible Trigger Logic

Allows multiple conditions (days, launches, significant actions) with .any or .all modes, enabling precise control over when prompts appear.

Localization Support

Customizable alert texts and country code restrictions make it easy to tailor prompts for international apps, as detailed in the README's customization section.

Built-in Debugging

Debug mode shows prompts every time during development, simplifying testing without waiting for real usage conditions to be met.

Cons

iOS Version Limitations

Features like showLaterButton and daysBeforeReminding are only effective for iOS 10.2 or earlier, reducing control on newer iOS versions where Apple's SKStoreReviewController handles reminders internally.

Architectural Constraints

Requires AppDelegate setup and calling check() in viewDidAppear, which may not align with modern SwiftUI or MVVM patterns, adding complexity for some projects.

Configuration Risks

Debug mode must be manually set to false for App Store submission; forgetting this can cause prompts to appear incorrectly in production, as warned in the README.

Frequently Asked Questions

Related Projects

SwifterSwift

A handy collection of more than 500 native Swift extensions to boost your productivity.

Stars15,194

Forks1,660

Last commit1 month ago

R.swift

Strong typed, autocompleted resources like images, fonts and segues in Swift projects

Stars9,560

Forks776

Last commit1 year ago

Periphery

A tool to identify unused code in Swift projects.

Stars6,182

Forks245

Last commit27 days ago

swift-protobuf

Plugin and runtime library for using protobuf with Swift

Stars4,962

Forks538

Last commit1 day 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