Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
iOS keyboard extension technical limitations and workarounds. Use when planning or building iOS custom keyboards with voice/audio features, dictation, or system integration needs. Covers memory limits, sandbox restrictions, microphone access, app launching, and viable alternative architectures.
iOS keyboard extension technical limitations and workarounds. Use when planning or building iOS custom keyboards with voice/audio features, dictation, or system integration needs. Covers memory limits, sandbox restrictions, microphone access, app launching, and viable alternative architectures.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
When building iOS custom keyboards with voice/audio features, these are the hard limitations discovered through the PolyVoice project.
Keyboard extensions cannot access the microphone. AVAudioRecorder will fail with permission error SFSpeechRecognizer is unavailable No Siri integration from keyboard context Why: Apple security model — keyboards run in sandbox and could keylog audio.
Keyboards cannot programmatically open the main app or any other app. UIApplication.shared.open() returns false URL schemes don't work (myapp://) ExtensionContext.open() not available Why: Prevents malicious keyboards from launching apps without user consent.
Keyboard extensions have strict memory limits (~30-60MB). App terminated silently if exceeded No crash log, just disappears Heavy audio processing = instant death Mitigation: Record at 16kHz mono (not 44.1kHz) Use 32kbps bitrate max Immediate file cleanup after processing 60-second max recording hard limit
UserDefaults unavailable, only App Groups. Standard UserDefaults doesn't persist Must use UserDefaults(suiteName: "group.com.company.app") Requires App Group capability in both targets
API calls fail without user enabling "Allow Full Access" in Settings. User must explicitly enable: Settings → General → Keyboard → [Keyboard Name] → Allow Full Access Most users won't do this Cannot prompt or explain from keyboard UI effectively
Goal: Let user tap a button to open main app for recording. Attempt: // This does NOT work extensionContext?.open(URL(string: "myapp://record")!) Reality: Must use UIApplication.shared.open() outside extension context, but keyboards can't call this.
What actually works (with friction): User taps button in keyboard → Shows alert: "Open PolyVoice to record?" User manually switches to main app (Home button, swipe, etc.) Main app detects active session (via App Groups / shared state) Main app auto-records on appear Auto-stops on silence (2 seconds) Auto-copies to clipboard User manually switches back to target app Keyboard auto-pastes on reappear User flow: Keyboard → Tap mic → [Manual: Switch to app] → App auto-records → [Manual: Switch back] → Keyboard auto-pastes Friction points: Two manual app switches Context switching breaks flow Users forget to return Clipboard may be overwritten
Use Share Sheet instead of keyboard. Full app capabilities Can record audio Can process and return text Limitation: Not a keyboard — user must open share sheet per text field.
Don't use keyboard extension — use main app only. User opens app Records dictation Copies result Switches to target app Pastes manually Benefit: No memory limits, full mic access, reliable. Cost: More friction than keyboard.
Provide Siri Shortcuts for voice-to-text. "Hey Siri, dictate with PolyVoice" Returns text to current app Fully supported by Apple Limitation: Not instant, requires Siri setup.
ApproachMic AccessMemoryUser FrictionApple ApprovedKeyboard extension❌ No⚠️ 50MBLow (if no audio)✅ YesKeyboard + audio workaround❌ No⚠️ 50MB🔴 High✅ YesShare extension✅ Yes✅ Full🟡 Medium✅ YesFull app only✅ Yes✅ Full🟡 Medium✅ YesSiri Shortcuts✅ Yes✅ Full🟡 Medium✅ Yes
For voice dictation/AI transcription: Don't build a keyboard extension — the limitations make it frustrating Use Share Extension — Apple-supported, full capabilities Or full app — simplest to build, most reliable Add Shortcuts — for power users who want speed For non-audio keyboards (emoji, translation, etc.): Keyboard extension works great. Just avoid audio features.
Apple's official docs: https://developer.apple.com/documentation/uikit/keyboards_and_input/creating_a_custom_keyboard Custom Keyboard Programming Guide (WWDC sessions) PolyVoice project learnings (~/Projects/polyvoice-keyboard/)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.