A customizable Swift view for entering pins, codes, or passwords in iOS apps with support for iOS 12 one-time codes.
CBPinEntryView is a customizable Swift view for iOS that facilitates the entry of pins, codes, or passwords. It solves the problem of creating a polished and interactive input interface for authentication, verification, or secure data entry, supporting features like backspacing, keyboard dismissal, and error feedback. The view is easily integrated and customizable, making it a go-to solution for developers needing a reliable entry component.
iOS developers building apps that require secure or structured input fields, such as authentication screens, two-factor verification, or PIN-based workflows. It's particularly useful for those seeking a pre-built, customizable alternative to manual UITextField implementations.
Developers choose CBPinEntryView for its ease of customization, support for various keyboard types, and built-in features like secure entry and error display. It saves development time by providing a ready-to-use, slick component that enhances user experience without requiring extensive custom coding.
A customisable view for entering arbitrary length pins, codes or passwords in iOS. Supports iOS 12 one time codes.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports arbitrary-length pins and returns values as String or Int, making it versatile for different authentication scenarios, as shown with methods like getPinAsString().
Easily customizable via IBInspectable properties, allowing quick setup in Interface Builder without extensive code, as demonstrated in the installation instructions.
Enables secure text entry with a customizable character (e.g., ● to ✱), providing enhanced security and UI flexibility, specified in the secure entry section.
Includes an error mode that can be programmatically set and cleared, visually communicating incorrect entries to users, as illustrated in the GIF examples.
Limited to UIKit and storyboards, with no native SwiftUI compatibility, which may hinder adoption in modern iOS projects transitioning to declarative UI.
Installation is primarily through CocoaPods, which might not align with teams using SPM or Carthage, adding complexity for some development environments.
The README provides essential information but lacks advanced tutorials or best practices, potentially requiring developers to explore the source code for complex customizations.