Question 1

How do I customize the buttons in OnboardKit?

Accepted Answer

You can customize buttons using ButtonStyling closures in the AppearanceConfiguration. For example, set title colors and fonts by passing a closure that modifies the UIButton instance, as shown in the README's advanceButtonStyling example.

Question 2

OnboardKit or SwiftUI onboarding – which should I use?

Accepted Answer

Choose OnboardKit if you're working with UIKit and need deep customization with a clean Swift API. For SwiftUI projects, consider native SwiftUI solutions or libraries designed for SwiftUI, as OnboardKit is UIKit-only.

Question 3

Can I load onboarding content dynamically with OnboardKit?

Accepted Answer

No, OnboardKit requires pages to be defined statically as OnboardPage instances in code. For dynamic content, you would need to manually update the pages or extend the library to handle data fetching.

Question 4

What iOS versions does OnboardKit support?

Accepted Answer

OnboardKit supports iOS 11.0 and later, as stated in the requirements. This ensures compatibility with a wide range of devices but excludes older iOS versions.

Question 5

How to add skip button or track user progress in OnboardKit?

Accepted Answer

The README doesn't explicitly cover skip buttons or progress tracking. You might need to implement custom logic by extending the OnboardViewController or using the action button for skip functionality.

Question 6

Is OnboardKit compatible with both CocoaPods and Carthage?

Accepted Answer

Yes, OnboardKit supports installation via both CocoaPods and Carthage, as indicated by the badges and installation instructions in the README, making it flexible for different dependency management preferences.

OnboardKit

What is OnboardKit?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions