Hackable color picker library written in Swift 5 that can be easily extended and customized. It aims to provide great UX and performance with stable, quality code. Includes controls for both HSB and RGB color models.

• supports HSB and RGB color models, both radial and rectangular hue/saturation palette
• there is ready-to-use view controller if you need quick, simple solution
• freely combine, leave out or add your own picker components when you need flexibility
• well documented
• highly customisable
• storyboard support with design time preview and customisation directly from storyboard
• library consists of small classes and robust, easy to understand code
• can be used without subclassing specific controller
• hackable: protocols for adding custom picker controls, open classes ready for subclassing

1. plug & play color picker that works great out-of-box
2. agile library that supports components positioning with autolayout and customisation directly from storyboard
3. framework that allows adding your own sliders, palettes & previews or modifying existing ones without changing the code of the library
4. combine 3 approaches above freely to get the level of customisation that you need

In XCode 11 and above click File → Swift Packages → Add Package Dependency... → choose target to add FlexColorPicker to → enter https://github.com/RastislavMirek/FlexColorPicker, press next → set version prefference and confirm.

Alternativelly, if you are using Package.swift just add this dependency:

dependencies: [
    .package(url: "https://github.com/RastislavMirek/FlexColorPicker.git", from: "1.3.1")
]

Add this to your podfile:

pod 'FlexColorPicker'

You can also try the Demo project with following command:

pod try FlexColorPicker

If you are not Cocoapods or SPM user you can clone the color picker from repository with this command:

git clone https://github.com/RastislavMirek/FlexColorPicker

Alternativelly, you can download latest release as ZIP from releases.

Then open the cloned/downloaded project in XCode and compile target FlexColorPicker. File FlexColorPicker.framework will be created in Products directory. Open project that you want to add the color picker to in XCode, select project file, select your application's target on the left side, select General tab and add FlexColorPicker.framework under Embedded Binaries section.

The fastest and simplest way to add color picker to your project is using DefaultColorPickerViewController. You can add it either via storyboard or via code. In both cases you will need to implement ColorPickerDelegate protocol to receive update when a user selects color using the DefaultColorPickerViewController:

// MyController is the controller that presents DefaultColorPickerViewController
extension MyController: ColorPickerDelegate {

    func colorPicker(_ colorPicker: ColorPickerController, selectedColor: UIColor, usingControl: ColorControl) {
        // code to handle that user selected a color without confirmed it yet (may change selected color)  
    }
    
    func colorPicker(_ colorPicker: ColorPickerController, confirmedColor: UIColor, usingControl: ColorControl) { 
        // code to handle that user has confirmed selected color
    }
}

Both functions in ColorPickerDelegate are optional. You can only use one of them or both in conjuncion.

In storyboard, FlexColorPicker can be used by specifying Class of a view controller to be DefaultColorPickerViewController. That is done in Identity Inspector in right panel under Custom Class. Basic customisation of the controller is supported in storyboard via properties in Attributes Inspector. Delegate of DefaultColorPickerViewController can only be set in code:

class MyController {
    @IBOutlet var pickerController: ColorPickerController!
    
    override func prepare(for segue: UIStoryboardSegue, sender: Any?) {
        if let destinationColorPicker = segue.destination as? ColorPickerControllerProtocol {
            destinationColorPicker.delegate = self
        }
    }
}

DefaultColorPickerViewController can be displayed like this if using a navigation controller:

let colorPickerController = DefaultColorPickerViewController()
colorPickerController.delegate = self
navigationController?.pushViewController(colorPickerController, animated: true)

Replace the 3rd line of the above snippet with following code to display color picker modally:

let navigationController = UINavigationController(rootViewController: colorPickerController)
present(navigationController, animated: true, completion: nil)

All the above code should go to handler that triggers color picker display (e.g. handler of "Pick Color" button press).

If preffered, you can use following code to set DefaultColorPickerViewController to use rectangular, rather than radial hue-saturation pallete. See third animated image on this page for example.

colorPickerController.useRadialPalette = false

You can also set 3 additional properties that influence how color picker looks when rectangular palette is used (rectangularPaletteBorderOn, rectangularPaletteHueHorizontalInPortrait and rectangularPaletteHueHorizontalInLandscape). See in-code documentation for details. For more customisation please refer to section Customisation below.

DefaultColorPickerViewController is plug & play option (see Basic Usage) with limited customisation. It is a convinince "ready-to-use" view controller which makes use of FlexColorPicker's color controls and color picker controllers. Color controls are UIViews that (usually) subclass UIControl and allow user to pick desired color and color picker controllers manage them. If more flexibility than what DefaultColorPickerViewController provides is needed, you can use them dirrectly:

1. If custom layout of color controls is needed, read Custom Layout.
2. If custom look or behavior of color color controls is needed, read []
3. If both custom layout and behavior/look of color controls is needed, combine the above two approaches.

Provided color controls include hue/saturation palettes (circular or rectangular), sliders for saturation, brightness and for RGB components and a picked color preview control.

Additional can by added by implementing ColorControl protocol.

Each color control has some properties (some of them can be set in storyboard) that can be used for customisation of that control's look and feel. This is the list of included color controls:

ColorPreviewWithHex RadialPaletteControl RectangularPaletteControl SaturationSliderControl BrightnessSliderControl RedSliderControl GreenSliderControl BlueSliderControl

If you want to customize your color picker, you can choose and lay out color controls that you want, set their properties if needed and connect them by adding them to the same color picker controller.

In storyboard, lay out color controls and set their classes in Identity Inspector to classes of controls you want to use. For example, set class field in in Identity Inspector to text "RadialPaletteControl". Then set controller's class to CustomColorPickerViewController, open its Connection Inspector (right side of this image) and connect corresponding outlets the controls. The same can be done in code simply by assigning color controls to appropriate properties of CustomColorPickerViewController.

If you cannot subclass CustomColorPickerViewController e.g. because your controller is a subclass of another class use ColorPickerController instead. It can also be used in storyboard as interface builder custom object. It has same properties as CustomColorPickerViewController (actually, CustomColorPickerViewController is just a convenience wrapper for ColorPickerController). You can also add color controls to it via ColorPickerController.addControl(:) so you are not limited to properties.

Once added to a color picker controller (e.g. ColorPickerController) a color control will be synchronized with other controls managed by the same controller together selecting a single color.

FlexColorPicker is made to be tweaked and extended with minimum effort. You can add you own color control by implementing ColorControl protocol or extending one of following subclass-ready classes:

• AbstractColorControl - aways subclass if possible
• AdjustedHitBoxColorControl - provides extended hit box margin around the control
• ColorSliderControl - e.g. if you need sliders for another color model then HSB or RGB
• ColorPaletteControl - if you want to create another color palette

In many cases there will be no need to subclass ColorSliderControl or ColorPaletteControl. They both relay on their color delegates in how they handle color updates, present themselves and how they interpret user interactions. Therefore, you can instead implement ColorSliderDelegate or ColorPaletteDelegate protocols respectively to change look and behavior without changing the code of the control itself.

Demo project has good examples on both approaches (overriding and composition) and their combination, feel free to check it.

When subclassing AbstractColorControl or AdjustedHitBoxColorControl directly ( not via ColorSliderControl or ColorPaletteControl) you might want to override gestureRecognizerShouldBegin(:). By default, no UIPanGestureRecognizer is allowed to recognize any gesture on instances of AbstractColorControl. Depending on type of your custom color control you might want to allow UIPanGestureRecognizer to recognize the gesture in some (or all) cases. For example, horizontal slider will want to prevent UIPanGestureRecognizer from recognizing horizontal pan gesture because that means changing slider's value. In the same time, it may allow UIPanGestureRecognizer to recognize any vertical pan gesture as by those user probably ment to scoll the superview of the slider (it might be UIScrollView), not changing slider's value.

All classes and functions of FlexColorPicker have great in-code documentation. It is there to help you when you are unsure about that class or function's purposer or usage.
☛ Just option-click name of any FlexColorPicker class or function in XCode to display detailed documentation.

When setting up slider controls in storyboard it is a good practise to set its background to be transparent. Alignment rectangle (rectangle that autolayout uses to lay out the control) is smaller than the actual frame of the slider to allow for extra hit box margin as well as background framing of the slider. Therefore, if background is solid white it can overlap other views close to it.
☛ If you do not want this behavior, set Hit Box Inset to 0 in Attributes Inspector or set hitBoxInset to 0 in code.

ColorPreviewWithHex can be tapped. When it it tapped, ColorPickerController calls ColorPickerDelegate.colorPicker(_:selectedColor:usingControl:) on its delegate.
☛ You can communicate this feature to your users or opt out by setting ColorPreviewWithHex.tapToConfirm to false.

When you create your own color controls that do not inherit from AbstractColorControl and add use them with a modally presented UIViewController, their pan gestures may conflict with dismiss modal gesture on iOS 13. The pan gesture may also conflict with scrolling when they are subclass of UIScrollView.
☛ Solve this by adding following code to the view that receives touches (bottom most one in view hierarchy) of your custom color control:

override func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool {
    return !(gestureRecognizer is UIPanGestureRecognizer)
}

Implementation of all provided color controls (including AbstractColorControl and AdjustedHitBoxColorControl) overrides gestureRecognizerShouldBegin(:) in order to ensure that the color controls work correctly when embeded inside UIScrollViews and iOS 13 modal view conctollers presented modally. The implametation prevents instaces of UIPanGestureRecognizer from recognizing any gesture if some condition is met. In some rare cases this may interfere with custom UIPanGestureRecognizers that you add to view hierarchy.
☛ Solve this by subclassing the color control that you want to use with your UIPanGestureRecognizer and overriding gestureRecognizerShouldBegin(:) so that the gesture is recognized.

When you add a subview to a color control (either your custom color control or any of the provided ones), that subview has user interaction enabled and the color control is embedded inside a UIScrollView or iOS 13 modally presented view controller you may experience following issue when panning/swiping that subview: Panning/swiping meant to interact with your control control might be interpreted as scrolling/dismissing the controller or vice-versa.
☛ Solve this by adding following code to the subview that you added to the color control and setting the delegate to the color control itself:

weak var delegate: LimitedGestureViewDelegate?

override func gestureRecognizerShouldBegin(_ gestureRecognizer: UIGestureRecognizer) -> Bool {
    guard let delegate = delegate else {
        return !(gestureRecognizer is UIPanGestureRecognizer)
    }
    return delegate.gestureRecognizerShouldBegin(gestureRecognizer)
}

If you like it, have a question or want to hire iOS developers shoot me a message at

[my first name, see profile] at [epytysae spelled backwards] dot [first 4 letters of word information]

Emails go directly to author of FlexColorPicker, cryptic format is just spam bot protection.

Suggestions, feedback, bug reports & pull requests are very welcomed.

Visual of slider control was inspired by popular Objective-C library HRColorPicker. Thank you for using FlexColorPicker! If you just have 3 seconds to give back, please star this repository.