Introduction

Overview

Talkie is a voice-first productivity suite for macOS. Built with privacy at its core, it processes everything locally while maintaining a seamless experience across devices.

Philosophy

Talkie is designed around three core principles that guide every architectural decision. These aren't just marketing—they fundamentally shape how the app works.

Local-First

Your voice data never leaves your devices. All transcription happens on your Mac.

Privacy by Design

No cloud processing required. No accounts needed. Your data is yours.

Transparent

See exactly what's happening. No black boxes or hidden processes.

Design Principles

We treat every user as a potential developer. These principles guide how we build Talkie, giving you visibility and control over everything—with smart defaults so you don't have to think about it.

1

Everything is a file

Your data lives in readable formats on disk. SQLite databases, JSON exports, audio files—all accessible and portable.

2

Small, focused data stores

Instead of one monolithic database, each component owns its data. Memos in one place, live dictations in another. Clear boundaries, easy to reason about.

3

Data stores exposed by default

We don't hide your data in opaque containers. Browse your recordings, query your databases, export anything. Your data, your access.

4

Well-defined lifecycles

Every recording flows through clear phases: capture → transcription → routing → storage. Each phase has hooks where you can plug in custom logic.

5

Protect the critical path

Recording and transcription are sacred. Nothing should block them—not sync, not workflows, not UI rendering. The happy path is always fast.

6

Smart defaults, full control

Talkie works great out of the box. But when you want to customize—workflows, shortcuts, data locations, export formats—everything is configurable.

Local-First Design

"Local-first" means your data lives on your device first, always. The cloud is optional, not required. This has real implications:

  • Works offline — Record, transcribe, and create memos without internet
  • Instant startup — No waiting for cloud connections or sync
  • You own your data — It's in readable formats on your disk
  • No accounts required — Start using Talkie immediately

When you do enable sync (like iCloud), it's additive. The app works perfectly without it, and sync just keeps your devices in harmony.

Multi-Process Architecture

Unlike most apps that run as a single process, Talkie splits responsibilities across multiple specialized processes. This design provides reliability, security, and performance benefits.

TalkieOrchestrator
TalkieAgentEars & HandsXPC
TalkieEngineLocal BrainXPC
TalkieServeriOS BridgeHTTP
SYS.OVERVIEW.001

Why multiple processes?

  • Fault isolation — If one component crashes, others keep running
  • Security boundaries — Each process has only the permissions it needs
  • Resource management — Heavy transcription work doesn't block the UI
  • Independent updates — Components can evolve separately

How Components Communicate

The processes talk to each other using two main methods, each chosen for specific reasons.

XPC (Inter-Process Communication)

Talkie ↔ TalkieAgent ↔ TalkieEngine

XPC is Apple's secure inter-process communication mechanism. It provides automatic process lifecycle management, type-safe messaging, and sandboxing support. All native macOS components use XPC.

HTTP (Local Server)

TalkieServer ↔ iPhone

TalkieServer exposes HTTP endpoints that the iPhone app connects to. All traffic flows over Tailscale's encrypted WireGuard tunnel. This enables cross-device sync without any cloud intermediary.

Continue Reading

Ready to go deeper? The architecture docs explain each component in detail.

Architecture Deep Dive

Detailed look at each component and how they work together