Private design critique notes on Mac

Design critiques are the vital engine of quality, cohesion, and craftsmanship in digital product development. During weekly critique rituals, product designers, UX researchers, design systems engineers, and product managers assemble to review wireframes, scrutinize interactive prototypes, debate typographic hierarchy, evaluate component token inheritance, and audit WCAG accessibility compliance.

Yet documenting design critiques presents persistent operational challenges:

During an active visual critique session, the presenting designer is busy sharing their screen, zooming into Figma artboards, and navigating prototype states. Expecting them to simultaneously write comprehensive notes about rapid verbal feedback breaks conversational momentum. Conversely, inviting a third-party cloud AI recording bot into the critique creates an awkward dynamic: design critiques require psychological safety and candid, rigorous aesthetic challenge. When an automated bot sits in the participant list, team members hesitate to voice critical visual flaws.

Oyma solves this creative dilemma on macOS. Leveraging Apple’s native ScreenCaptureKit framework, Oyma captures the audio of your design critique silently, without introducing an uninvited bot into your Zoom, Google Meet, or Slack call. Transcriptions execute 100% on-device on Apple Silicon using local Whisper models, converting spoken visual critique into structured, actionable Markdown design records stored directly on your Mac.

The documentation breakdowns in modern product design

Design feedback is uniquely contextual, visual, and rapid, making manual note-taking prone to severe failure modes:

1. The lost feedback gap: A reviewer comments: “The contrast on that secondary badge fails WCAG AA on dark mode, and the padding on mobile wraps the call-to-action button awkwardly.” If not captured verbatim, the designer later recalls only that the badge needed adjustment, forgetting the exact contrast threshold or mobile padding constraint.
2. Post-critique administrative fatigue: Designers spend hours re-watching cloud video recordings at 1.5x speed just to transcribe feedback into a punch list, wasting precious creative time that should be spent iterating in Figma.
3. The chilling of constructive critique: Meaningful design reviews require honest aesthetic pushback. If team members see an AI recording bot in the participant list, they withhold difficult critiques to avoid appearing unsupportive on a permanent cloud recording.
4. Pre-release visual IP exposure: Design critiques showcase unreleased brand identities, novel UI interactions, and confidential product features. Sending this audio to multi-tenant cloud transcription services violates enterprise intellectual property protections.

The design team’s critique vault in plain Markdown

Oyma organizes design reviews directly into an interconnected, sovereign Markdown knowledge base:

vault/
├── design/
│   ├── critiques/
│   │   ├── 2026-10-02-billing-drawer.md
│   │   ├── 2026-10-05-command-palette.md
│   │   └── 2026-10-09-table-editor.md
│   └── tokens/
│       ├── typography-scale.md
│       └── color-primitives.md
└── components/
    ├── modal-dialog.md
    └── data-table.md

By connecting critique records to design token specifications and component documentation via [[wikilinks]], teams maintain an unbroken historical log of interface decisions.

Sample on-device design critique note

Here is an authentic Markdown artifact generated during a design critique session in Oyma:

---
sessionType: Technical Design Critique
date: 2026-10-09
featureArea: "[[components/data-table]]"
leadDesigner: "[[team/chloe-dupont]]"
participants:
  - "Marcus Vance (Staff Product Designer)"
  - "Dave Kaufman (Frontend Tech Lead)"
  - "Maya Lin (Product Manager)"
tags:
  - design-critique
  - figma-review
  - design-systems
---

# Design Critique: Data Table Component & Inline Editing

## 1. Context & Review Objectives
Chloe Dupont presented the updated Figma wireframes for our desktop data table component, focusing on keyboard navigation, inline cell editing, and bulk row selection states across macOS desktop and responsive viewports.

## 2. Agreed Design Decisions
- **Keyboard Navigation Model:** Adopted Excel/Numbers arrow-key navigation pattern. Pressing `Enter` opens the active cell for inline editing; pressing `Tab` advances to the next horizontal cell and commits the edit.
- **Bulk Action Toolbar:** When three or more rows are selected, the action bar will float persistently at the bottom-center of the viewport with a frosted glass backdrop filter.
- **Truncation Behavior:** Long cell text will truncate with an ellipsis (`...`) at cell boundary; hovering over the cell displays an unclipped tooltip preview after a 300ms delay.

## 3. Usability & Accessibility Concerns Identified
- **Contrast Failure on Selected Rows:** Marcus noted that the proposed light blue selection tint (`#E0F2FE`) lacks sufficient 3:1 contrast against the table border line in high-contrast macOS display settings.
  - *Resolution:* Switch selection token to `var(--surface-selected)` which dynamically adapts to system accessibility preferences.
- **Screen Reader Focus Trapping:** Dave warned that inline cell popover menus must trap focus properly so screen reader users do not tab into background rows unexpectedly.

## 4. Rejected Design Iterations & Rationale
- **Rejected Option:** Accordion drawer row expansion for nested metadata.
  - *Rationale:* Testing demonstrated that expanding rows vertically caused jarring layout shift on large tables. The team agreed on a slide-over side drawer for detailed row inspection.

## 5. Actionable Redesign Punch List
| Priority | Design Action Item | Component | Owner | Status |
| :--- | :--- | :--- | :--- | :--- |
| P0 | Update row selection token to meet WCAG 3:1 contrast requirements | Data Table Cell | Chloe Dupont | Open |
| P0 | Add keyboard focus ring spec (2px solid accent token with 2px offset) | Cell Focus State | Chloe Dupont | Open |
| P1 | Document exact CSS subgrid layout rules for column resizing | Table Header | Dave Kaufman | Open |
| P2 | Prototype slide-over drawer animation in Figma for secondary metadata | Detail Drawer | Chloe Dupont | Open |

The design critique translation pipeline: from prototype walk to code handoff

Bridging live design walkthroughs with structured frontend punch lists requires an agile documentation rhythm:

1. Silent screen and conversation monitoring

While sharing Figma prototypes over Zoom, Slack Huddles, or Meet, toggle Oyma‘s background recorder. Leveraging macOS ScreenCaptureKit at the operating system tier, audio streams record unobtrusively. Without an automated attendee bot joining the call roster, reviewers and designers debate visual hierarchies and layout tradeoffs with natural spontaneity.

2. High-fidelity design terminology recognition

Spoken critique vocabulary—including kerning, bounding boxes, flexbox wrapping, auto-layout constraints, and token references—undergoes immediate transcription via local Whisper models on Apple Silicon. Audio data stays strictly on your Mac’s physical storage.

3. Synthesizing visual punch lists and token decisions

Following the critique, execute Oyma‘s design review extraction prompt via on-device Ollama models or your private API key. The summary engine extracts:

• Inspected artboards and interactive prototype flows
• Confirmed design token adjustments and typographic scales
• Flagged usability bottlenecks and accessibility contrast concerns
• A prioritized redesign punch list with assigned designers

4. Direct integration into design system repositories

The structured Markdown critique memo saves directly into your local design repository. Through bidirectional wikilinks, feedback maps to component specifications and design tokens in Obsidian, ready for immediate frontend developer review.

Safeguarding unreleased visual intellectual property

Product design reviews reveal the upcoming visual identity and competitive roadmap of your company:

• Protection of unreleased IP: Design critiques discuss unannounced branding, user interface innovations, and proprietary product concepts. Storing these discussions on local encrypted storage prevents intellectual property leaks.
• Permanent design history: While Figma comments are frequently resolved and archived, local Markdown critique notes remain permanent, searchable artifacts that explain the historical evolution of your interface.
• Air-gapped review: With Local-only mode, designers can synthesize critique notes and review design system dependencies completely offline.

To learn more about our local audio architecture, read about botless meeting recording, explore spreadsheet-like Markdown tables, or review our zero-leak privacy architecture.