🧩

Dayze Apps

Apps that belong on your life graph — not another feed. Create something to track, connect a partner, and let Dayze remain the system of record.

The framing

Dayze is a Life OS. The timeline, Day Cards, people, money, and Dayze Agent are the operating system. Everything else should feel like an app on that OS — an icon, a purpose, and a clear place its data lands.

That is the product noun: Dayze Apps. Some apps are built by Dayze. Some are partners (Coincess, Tiger Brokers, Spotify). Soon, some will be created by you — to track climbing sessions, job hunts, kids' sleep, a side project, or anything else that deserves a durable place in your days.

Note: Dayze Apps are not a competing app store for chatbots. They are lightweight systems that write structured life data into your graph, with permissions you can revoke.

Where it lives in the product

Users discover and manage apps in one place: /integrations. That grid is the Life OS app shelf — brand icons, Connected badges, and a detail sheet for what the app writes and how to connect it.

🏪

Integrations hub

Browse first-party, partner, and (later) user-created apps as icons — same mental model as Strava or Finance partners.

🔑

Scoped API keys

Apps push via dayze_k_… keys with scopes like activity and networth. Revoke the key = disconnect the app.

🗓️

Timeline & Day Cards

Apps write events and snapshots into your life graph. Dayze Agent can reason over them without retyping.

💰

Net Worth & Finance

Finance apps (Coincess, Tiger) update portfolio NAV beside everything else — still just Dayze Apps with a money destination.

How Dayze Apps relate to existing concepts

Keep the vocabulary sharp so we do not invent parallel platforms:

Trackers — first-party habit widgets inside Dayze (gym, water, reading). Fast check-ins; not third-party products. See Trackers.
Integrations — the UI shelf and connection flows (OAuth, upload, partner push, iOS). See Integrations.
Life Modules — the technical extension contract (manifest, scopes, consent). See Life Modules.
Dayze Apps — the product frame for anything that shows up as an app icon and writes life data. Trackers can graduate into Apps; partners already are Apps; user-created Apps complete the story.

Tip: Say “Dayze Apps” to users. Say “Life Modules” to developers when talking about manifests and scopes. Say “Integrations” for the page at /integrations.

What an app is (thin by design)

Every Dayze App is a small package, not a mini product pile:

Identity — name, icon, short description, category
Write contract — activity types and/or metrics it may create (e.g. climb:session, job:application)
Scopes — what it can touch (activity, networth, later read scopes)
Destination — Timeline, Day Cards, Net Worth, or both
Optional surface — logging UI can live in Dayze, in the partner product, or both — Dayze stays source of truth

Note: Prefer typed activity kinds and optional metric series over free-form blobs. Schema discipline keeps the timeline readable and the agent useful.

Roadmap — three phases

Phase 1 — Now

Partner Apps on the shelf

Coincess, Tiger Brokers, Spotify, Gmail, Strava, and export uploads appear as icons on /integrations. Finance partners connect with a Dayze API key (activity + networth); Dayze marks Connected once data arrives.

Phase 2 — Next

Private Apps you create

Anyone can create a private app: pick a name and icon, define a few event types, get a scoped key (or log inside Dayze), and see it on their Integrations shelf. Examples: climbing log, job hunt CRM, book club, apartment hunt, training block.

These apps are private by default — only your account. No directory listing required.

Phase 3 — Later

Templates & public directory

Publish a template others can install (“Sobriety companion”, “New parent sleep log”). Review, abuse controls, and clear permission copy come before a free-for-all store. Platform vision lives under Platform vision.

Trust rules (non-negotiable)

Least privilege — apps ask only for scopes they need
Attribution — every write knows which app authored it
Revocable — disconnect / revoke key stops new writes
Private by default — user-created apps stay private until explicitly published
No second OS — apps do not replace People, Calendar, or Finance; they feed them

Deeper privacy posture: Privacy & Data and Trust & Security.

Example stories

🧗

Climbing log

Private Dayze App logs sessions, grades, and gym vs outdoor. Streaks on home; sessions on the timeline; Agent answers “how often did I climb in March?”

🧳

Job hunt

Applications and interviews as activity types. People links for recruiters. Dayze Agent drafts follow-ups from Response Queue context.

💹

Coincess

Partner finance app: closed fills → timeline, portfolio NAV → Net Worth. Connected badge appears when Dayze receives data.

🎵

Spotify

Partner enrichment app: recently played on Day Cards — same shelf, different destination.

For makers (preview)

Building against Dayze today uses the same rails partners use:

Create an API key at Settings → Agent access with activity and, if needed, networth
POST /api/v1/activity with a stable source (your app id) and typed activity_type
Optionally POST /api/v1/networth for portfolio-style snapshots
Appear on /integrations once we register the app catalog entry (partners now; self-serve create next)

API reference: API docs. Extension contract: Life Modules.

Tip: The winning sentence for Dayze Apps: “Build systems for your life; Dayze keeps the memory.” The shelf is the brand. The graph is the moat.

Integrations Life Modules