AllComputer GigsCreative GigsCrew GigsDomestic GigsEvent GigsLabor GigsTalent GigsWriting Gigs
QA test: Orbit beta: reply cards and Later — 2026-09-17
Estimated duration
~1h
Deadline
Tue, Sep 22, 2026
Location
Remote only
PRICING
$21 fixed
USD
per approved result
DESCRIPTION
One-time QA test run for https://github.com/emma2bean-bot/orbit-releases/releases/tag/v0.2.10.
Submissions are reviewed automatically. $21.00 is released per accepted submission.
What you must do to be paid
Before you apply
- Access to a device that can open https://github.com/emma2bean-bot/orbit-releases/releases/tag/v0.2.10
- Mac on macOS 14 or newer
- Apple Messages set up on that Mac with real conversations
- Can record screen with narration
- Profile country must be one of: US, CA, GB, AU
Task
https://github.com/emma2bean-bot/orbit-releases/releases/tag/v0.2.10Orbit is a small Mac menu-bar app that reads your Messages on your Mac (locally, nothing leaves your computer) and helps you keep up with friends you have not replied to. You need: a Mac on macOS 14 or newer, Apple Messages set up on that Mac with real conversations, and permission to record your screen. Download Orbit.dmg from the page above, open it, drag Orbit to Applications, and open it from Applications. It is a beta signed by the developer, so macOS will not block it. Record your screen with narration the whole time. Privacy: you may blur or skip showing message contents; we only need to see how Orbit behaves. When done, quit Orbit from its Settings and drag it to the Trash if you like.
THIS RUN: reply cards and Later. Set up Orbit first (any choices are fine; allow Full Disk Access and notifications). Then open Orbit from the menu bar.
- If there is a card for someone, click "Open in Messages". Send them a short real text. Then switch to any other app and stop typing. Within about ten seconds Orbit should pop back up on the same card, showing "Replied" and a line saying "Sent." Did it? How long did it take? If it did not come back, open Orbit yourself and tell us what the card shows.
- On another card, click "No reply needed". What changed?
- On another card, open the "Later" menu. Pick a time about 5 minutes from now. Does the card say when it will be back? Wait for that time with Orbit closed: does a desktop notification arrive? Click it: does Orbit open on that card?
- Then try "Later" again on a card and pick the option that moves it to tomorrow. You should get NO notification for that one.
- Look at the small progress bars under the card. Can you tell which ones are replied, no reply needed, snoozed, still to do? Hover over them and read the labels.
- Is the "Later" button easy to see, or too faint? Report: answers to each item, timings, and any bug with steps. If you have no cards at all, say so and show the empty state.
Submission requirements
Video assignments require spoken microphone narration throughout. Captions, written narration, and on-screen text are not substitutes.
Each required test item must be backed by video evidence: a timestamped range in your recording or a short clip.
- 1Popup comes back on the same card after a text is sentSend a text from Open in Messages, switch apps, stop typing. Show whether Orbit returns within about ten seconds with Replied and Sent.
- 2Later at a chosen time produces a desktop notification that opens the cardPick a time a few minutes ahead, close Orbit, wait. Show the banner and what clicking it does.
- 3Move to tomorrow gives no notificationUse the tomorrow option and confirm no banner arrives.
- 4Progress bars distinguish replied / no reply needed / snoozed / still to doHover the bars, read the labels, say if the difference is clear.
- 5Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
- 6Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
- 7Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
- 8Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
- 9Map every attachment to the reportIn the same chat message as each upload, explain what every attached file shows and which tested step or finding it supports.
- 10Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
- 11Still report useful observations if nothing failedA no-issue result must still say exactly what you tested and include concrete usability observations.
REQUIREMENTS
- •
Only submit evidence you captured yourself during this run