// Pulsar haptics implementation for iOS apps using the Swift SDK. Use when the user is writing Swift/SwiftUI/UIKit code and needs haptics, CoreHaptics wrapping, PatternComposer, RealtimeComposer, or migration from UIKit haptics.
| name | pulsar-haptics-ios |
| description | Pulsar haptics implementation for iOS apps using the Swift SDK. Use when the user is writing Swift/SwiftUI/UIKit code and needs haptics, CoreHaptics wrapping, PatternComposer, RealtimeComposer, or migration from UIKit haptics. |
Swift SDK built on CoreHaptics (iOS 13+). Wraps CHHapticEngine lifecycle, pattern compilation, and player management behind a simple preset and composer API. Audio simulation is enabled by default in debug builds so haptic patterns can be heard on the iOS Simulator.
api-overview.md — Load to know how to use the library API, and library capabilities.
presets-guide.md — Load when choosing a preset for a specific interaction / emotion / use case in the app.
../common/design-principles.md — Load to understand how to use haptics in mobile apps, and how to design custom patterns. It covers best practices and guidelines.
gesture-haptics.md — Load when implementing gesture-driven haptics. Also load ../common/gesture-haptics.md for the full design principles and patterns.
Pulsar haptics implementation for Android apps using the Kotlin SDK (com.swmansion:pulsar). Use when the user is writing Kotlin/Android code and needs haptics, CompatibilityMode, VibrationEffect, RealtimeComposerStrategy, or PatternComposer.
Pulsar haptics implementation for React Native and Expo apps using react-native-pulsar. Use when the user is writing TypeScript/React Native code and needs haptics, presets, worklet-compatible haptic calls, usePatternComposer, useRealtimeComposer, or migration from expo-haptics.
Expert guide for implementing haptic feedback using the Pulsar SDK across iOS (Swift), Android (Kotlin), and React Native (TypeScript). Use this skill whenever the user is working with haptics, vibrations, tactile feedback, or the Pulsar library in a mobile app — including preset selection, custom pattern composition, real-time gesture-driven haptics, migration from expo-haptics or UIKit/CoreHaptics, CompatibilityMode handling, and haptic design decisions. Always use this skill even if the user only mentions "vibration", "buzz", "taptic", "rumble", "pulse", "motor feedback", "tactile", "shake", "UIFeedbackGenerator", "CHHapticEngine", or "VibrationEffect" — or wants their app to "feel right". Vague phrases like "make it feel more responsive" or "add some feedback" in a mobile context should also trigger this skill.