Enable the keyboard
After installing your invited build, open Inkalune and follow onboarding. In iOS Settings, open General → Keyboard → Keyboards → Add New Keyboard and select the installed app name. It may still say EchoKey. Return to a plain note, focus a text field and use the globe/keyboard switcher. If the keyboard is absent, reopen the app and check installation; secure password fields may use Apple’s keyboard instead.
Microphone and Full Access
Check Settings → Privacy & Security → Microphone and allow the installed app if you wish to dictate. In the keyboard settings, Full Access is a separate, broad permission enabling capabilities beyond the restricted keyboard sandbox, including network communication. Review the build’s explanation before enabling it. It is not the same as granting microphone permission. If a managed device blocks it, ask your administrator rather than bypassing the restriction.
Standby and the orange indicator
The orange iOS indicator signals microphone use, including a ready session between dictations. Open Control Center to see which app is using it. In Inkalune, check the standby setting and use the session stop/end control when finished. If the indicator persists unexpectedly, close the app and review microphone permission in Settings. A ready session is not proof that every moment is uploaded; this website does not independently verify idle-audio handling for each build.
Action Button and Shortcuts
First confirm that your iPhone has an Action Button and that your beta build exposes an Inkalune action in Apple Shortcuts. Open Shortcuts, create a shortcut and search for the installed app’s actions. Select the available dictation action and test it from Shortcuts before assigning it in Settings → Action Button → Shortcut. If no action appears, open Inkalune once and check your build instructions. Test in a non-sensitive note: launching, returning text and clipboard delivery can vary with app state. Do not assume text was inserted until you see it.
Languages and recognition
Choose a language offered by your installed build before a short test. Automatic detection can struggle with short phrases, names and mixed languages. Try one explicit language to diagnose a mismatch. The website does not publish an unverified language-count or a tested coverage table; ask support about your language pair and build. Recognition is not a promise of translation.
Dictionary, snippets and styles
Add one non-sensitive name in the personal dictionary, then test it in a sentence. For snippets, choose a distinctive spoken cue and verify the expanded text. Select a writing style before a test draft and check that important meaning survives formatting. These tools guide output; they do not guarantee exact words or automatic learning. Labels may vary between beta builds.
Network errors and missing text
Cloud recognition and formatting need internet. Check your connection, then try a short dictation in a plain note. If interrupted, inspect recent writing/history for an available result or retry control before recording again. Keep the destination open and check whether text was copied rather than inserted. Do not assume an unsaved recording can be recovered. For missing trailing words, finish speaking before ending dictation and report the build, steps and timing without sending private audio.
Notes, history and updates
Review the scratchpad and recent-writing controls in your build. Copy important drafts elsewhere before clearing history or uninstalling. Local deletion is distinct from account deletion and provider records. Follow update instructions in your invitation; there is no public download link here. If screens differ, send support your build number and a redacted description.