Join the right session
Use a scoped QR code or link from the GM, with the recording role and verified roster kept in context.
Record and review
Mobile Recorder
Bring a phone recording into the game’s record.
Mobile Recorder connects a phone to the session’s recording workflow. A GM-provided QR code or link identifies the game and recording role, so audio can reach the right session rather than becoming an unlabelled file to sort out later.
What it helps you do
Browser microphone recording
Record supported audio formats in the foreground, with a deliberate stop action to reduce accidental endings.
Import a phone recording
Bring in an original native phone-recorder file when that is a better fit for a long session.
Check delivery before cleanup
Keep the original until a matching verified recorder receipt confirms the received file.
A scoped player companion
Where configured, link the player’s character to Runtime for public dice and movement or spell requests that the GM resolves.
Getting ready
The GM selects the game and roster and creates the session’s shared QR code or link. Open that link, choose your listed character or GM role, and confirm it. Check the session and identity before using the recorder. A character name or identifier alone does not authorise a phone to operate someone else’s character.
Choose foreground browser capture or the supported saved-file import route. For a long evening, consider the phone’s native recorder and check available storage, microphone permission, power, and the connection. Keep the original recording until the matching receiving receipt has been verified.
How to use Mobile Recorder
Join and confirm the right recording role
Use the current QR or session link rather than reusing a link from a previous night. Confirm the character or dedicated GM choice and check that the page represents the intended recording. The session link supplies scoped access; it is not a general login to all campaign recordings or a way to choose arbitrary local table services.
Record in the supported browser arrangement
Allow microphone access and keep the recorder available in the foreground. Check the recording indicator rather than assuming an enrolled slot means capture has started. Movement, dice, or spell views share the same microphone capture owner where the companion is configured. Phone and browser background restrictions still apply even when the page requests a leave warning.
End deliberately or import the native file
To finish browser capture, use the guarded end control and enter END when requested; cancel it if the game is continuing. For Samsung Voice Recorder import, open the assigned role link, select the completed original, and send it through the session workflow. The browser does not take ownership of or delete that phone file.
Resume the same transfer after interruption
If import pauses or loses its connection, retain the local recording data and select the same original file again. The workflow uses the retained parts and file identity to resume. Do not clear browser storage or create a duplicate session to make an interrupted upload look successful. Follow received-part and finalisation status separately.
Check the matching receipt before cleanup
Wait for the receiving service’s receipt for that recording and inspect the verified original size, hash, and receipt time. A last-part acknowledgment is not the same as a confirmed assembled archive. Remove the original using the phone’s own recorder only after this matching receipt exists, then check the separate Scribe handoff and processing state.
Test screenshot of the native-file upload receipt. In your game, check the receipt for your actual recording before removing the phone original. Use the companion within the GM’s binding
If the host has enabled your character’s controls, submit supported movement, public percentile or ten-sided dice, and approved spell-target requests. When a dice response is uncertain, use Retry same roll instead of asking for a new roll. A spell request can be pending, declined, resolved, or recorded; its submission alone does not move figures or establish a successful cast.
A game example
Bring a long phone recording into the correct night
For example, join the GM’s current session as your character and record the evening with Samsung Voice Recorder. At the end, select that original through your assigned import link. If the connection drops, resume the same file instead of starting another recording record. Keep the phone original until its matching verified receiving receipt appears. Scribe can then process the accepted audio for the linked night; a transfer completed tonight may still have transcription work waiting.
What you keep
Session-linked audio
A recording or imported original associated with the intended game, night, participant, and recording role.
Receiving evidence
Upload progress, retained recovery information, and a matching verified archive receipt rather than an assumed successful transfer.
Scoped player requests
Where configured, recorded public dice and GM-reviewed movement or spell requests for the host-bound character.
How it fits with the other apps
Adventure Scribe Notes Keeper
Hand off accepted audio for transcription and review.
About this appAlaric Alexa Skill
Use the configured recording control map to follow device and session status.
About this appDQ GM Runtime
Connect a scoped companion to the current game, when the local services are ready.
About this appCommon questions
Can I close or lock the phone while recording?
Do not assume the browser can record indefinitely in the background. Device and operating-system limits can interrupt capture despite page warnings. Rehearse the actual phone, or use a native recorder and the saved-file import route when it is the more reliable option.
Does a verified receipt mean the notes are ready?
It confirms the receiving archive for the original file. Scribe delivery, transcription, speaker review, and summary generation have their own status. Likewise, a demo upload used to test the connection may intentionally have no Scribe destination.
Usage guide based on the 7 October 2026 project summary, reviewed 8 October 2026. Examples illustrate possible games. Some connected features require sign-in, GM permissions, or a configured local table.