AllComputer GigsCreative GigsCrew GigsDomestic GigsEvent GigsLabor GigsTalent GigsWriting Gigs
QA test: Orbit beta: install and setup — 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: install and setup. Cover, in order, and say out loud what you expected vs what happened.
- Open the DMG, install, launch. Does a small Orbit icon appear in the menu bar near the clock?
- Walk through setup. On the step that asks for Full Disk Access: click the button that opens System Settings, switch Orbit on in the Full Disk Access list. If macOS offers "Quit & Reopen", choose Later. Does the Orbit setup window come back on its own and say access was granted, without Orbit quitting or disappearing? This is the main thing we are testing here.
- The Contacts step: allow or decline, and tell us whether the list of people afterwards shows names or just phone numbers.
- Pick 5 to 15 people and give each a ring. Was it clear what a ring means?
- Notification times: remove one of the default times, then use "Add a time" to add a new one. Was that obvious? Then allow notifications when macOS asks.
- Read every screen's text and tell us any sentence you had to read twice. Report: a bug list with steps to reproduce, plus your answer to each numbered item.
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.
- 1Full Disk Access step comes back on its own without Orbit quittingAfter switching Orbit on in Full Disk Access (choose Later if offered Quit & Reopen), the Orbit setup window should return by itself and say access was granted. Show whether it did.
- 2People list shows names (after Contacts) or numbersSay whether the people list shows real names or bare phone numbers, and whether you allowed Contacts.
- 3Remove a default notification time and add one with Add a timeShow removing a chip and adding a time from the list. Say whether it was obvious.
- 4Quote any sentence you had to read twiceFor each setup screen, quote text that was unclear or too long.
- 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