Orbit 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 with Apple silicon 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 signed and notarized by Apple, so macOS will not block it. Record your screen with narration the whole time and say out loud what you expect versus what happens. 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: the full flow, start to finish, about 30 to 40 minutes. You have 6 hours from accepting, so start only when you have the time.
Install and launch. Walk through every setup screen. On the Full Disk Access step, click the button that opens System Settings and switch Orbit on; if macOS offers Quit & Reopen, choose Later. Does the setup window come back on its own?
Allow Contacts, Send through Messages (Automation), Notifications and Calendar when asked. After each Apple dialog closes, does the Orbit window come straight back? Note any step where Orbit seemed to disappear.
On 'Who do you want to keep up with?': read the ring legend (Inner, Close, Wider, New). In your own words, what does each ring do? Pick 5 to 15 people and give each a ring.
On 'Pick your notification times': read 'How a batch works' and tell us in your own words who gets a card and when. Set one time about 10 minutes from now.
Finish setup. IMPORTANT: when the setup window closes, does the Orbit popup open by itself from the menu bar? Yes or no, and what you saw.
On a card, type a short real reply in the box and press Send. You get 1.5 seconds to undo. Did the message really send (check Messages)? Did the next card come up right away? Any freeze or spinning wheel?
On another card press 'No reply needed'. Does the card's bottom button turn into Next, and does the card move on by itself after about a second? Try 'Later' on a third card.
If someone you replied to had an unread blue dot in Messages, open Messages afterwards: is the dot gone?
Open Orbit's Settings. Press 'Check for updates now' at the top: what does it say? Switch Appearance between System, Light and Dark: does everything change at once and stay readable?
Wait for the notification at your chosen time. Did a banner arrive, and does clicking it open Orbit on today's cards?
Report: a yes/no answer to every numbered item, a bug list with steps to reproduce, and the three most confusing sentences you saw, quoted, with how you would rewrite each.
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.
1The Orbit window comes back after every Apple permission dialogSay for each of Full Disk Access, Contacts, Automation, Notifications, Calendar whether Orbit came back on its own.
2The Orbit popup opens by itself when setup finishesYes or no, and what you saw on screen.
3Rings and 'How a batch works' are understandableExplain each ring and who gets a card, in your own words.
4A reply typed on a card really sends, with no freeze, and the next card comes upConfirm in Messages. Note any spinning wheel.
5No reply needed turns the button into Next and the card moves on; Later worksDescribe what changed on the card.
6Check for updates now and Appearance workQuote the update line; try Light and Dark.
7A banner arrives at the chosen time and opens OrbitNote the time it arrived.
8Complete the assigned test stepsFollow every instruction above. If a step is blocked, name the exact step and explain what prevented it.
9Describe test coverageList the steps, pages, controls, devices, and paths you actually tested.
10Report concrete resultsExplain what happened, what worked, and any confusing or poor experience you observed.
11Provide the required video evidenceAttach an MP4, MOV, or WebM screen recording no larger than 512 MB, plus at least one representative screenshot.
12Map 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.
13Make every issue reproducibleFor each issue, include a short title, severity, expected behavior, actual behavior, and exact reproduction steps.
14Still 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