# Build brief — a focused alternative to Gojo

> **Verdict:** Partly, if you narrow it · **Buildability:** 72/100 · **Category:** Productivity Utilities
> **Source:** https://www.canitbevibecoded.com/gojo
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Gojo. Verify current pricing and capabilities before acting.

## Context

**Gojo** — Five everyday Mac tools tucked into the MacBook notch. It currently costs $4.99/mo.

A contained is enough for the useful part: a notch panel with clipboard history, a file shelf, music controls, window snapping, and screen warmth. Getting it ready for daily use takes longer because macOS permissions, dictation, multiple displays, and tiny UI details add up fast.

This brief describes a focused, single-operator replacement for the part of Gojo that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Open a small panel from the MacBook notch and jump between clipboard history, a file shelf, music controls, window snapping, and screen warmth.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- MacOS 14 or later.
- Xcode 16.
- Accessibility permission for window control.
- Apple Events permission for media control.
- Local storage.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build a small macOS notch app inspired by Gojo. Keep v1 to five tabs:

- Use Swift 6, SwiftUI, and AppKit on macOS 14. Generate an Xcode project and skip
  third-party packages.
- Make it an accessory app with no Dock icon. Find the built-in display notch and
  anchor a borderless floating panel right below it.
- Open the panel after the pointer rests at the notch for 200 ms. Close it on an
  outside click or Escape. Add Music, Windows, Clipboard, Shelf, and Display tabs.
- Clipboard: poll NSPasteboard, save the latest 100 text items in Application Support,
  add search, and copy a picked item back. Skip transient and concealed pasteboard
  types, plus apps listed in a configurable denylist.
- Shelf: accept dropped files, save security-scoped bookmarks, show file icons, and
  support dragging files into another app. Add remove and clear-all actions.
- Music: control Apple Music or Spotify through AppleScript. Show the active app and
  track title, with play/pause, previous, and next controls.
- Windows: list visible app windows through the Accessibility API. Add left half,
  right half, and maximize actions.
- Display: save each screen's gamma table, apply blackbody RGB multipliers with
  CGSetDisplayTransferByTable, and restore the original table on disable or exit.
- Save settings in UserDefaults. Leave out accounts, sync, telemetry, calendar,
  camera, dictation, battery widgets, and automatic updates.
- On first launch, walk through the permissions. Give every tab a useful empty state.
- Test clipboard deduplication, shelf persistence, and snap-frame math.
- Document setup, privacy, Accessibility and Automation permissions, and the macOS
  APIs most likely to change.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Signed and notarized builds with automatic updates.
- Smooth notch behavior across multiple displays.
- On-device dictation and its safety checks.
- Built-in calendar, reminders, webcam, and battery tools.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**Manageable.** A personal version is realistic if you test the critical journey and keep reliable backups.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Gojo source](https://github.com/rohoswagger/gojo) — The full GPL-3.0 codebase for the native app

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/gojo