---
title: "Feature ideas backlog"
url: https://memory.wiki/wyULEr1h
updated: 2026-05-14T18:15:49.480Z
hub: https://memory.wiki/hub/demo
concept_count: 12
source: "memory.wiki"
---
# Feature ideas backlog

> Ranked by gut-feel value:effort. Not committed to any of these.

## Top 5 — high value, manageable effort

1. **Inline graph_data in bundle URL** — already shipping. The decision write-up is at `demo-dec-bundle-graph-inline`. This is the load-bearing feature for the cross-AI thesis.
2. **Custom hub theme** — let users pick an accent colour and a typeface. Modest engineering effort, real perceived-quality bump. Ship-able in a week.
3. **Slack capture** — send a Slack DM to a bot, get a permanent mdfy URL back. Reuses the existing capture pipeline. Two weeks of work, mostly OAuth dance.
4. **Email-in capture** — forward any email to a magic address, get a mdfy URL back. Cheaper than Slack because there's no OAuth, but spam-protection matters.
5. **Hub-to-PDF export** — generate a single PDF of all public docs in a hub. Useful for portfolio-mode users. Most of the work is print CSS, which we already have for individual docs.

## Mid-tier — interesting but later

- **Concept-page editing.** Right now the concept index pages are auto-derived. Letting the user pencil-edit a concept's description is a big-feel feature with light engineering cost.
- **Per-bundle layouts.** Bundle owners pick how the canvas paints (timeline / tree / grid). Adds dimensionality to the bundle as a surface.
- **Embed a doc inside another doc.** The `{{include: doc-id}}` macro. Useful for compositional notes. Engineering risk is recursion.
- **Activity dashboard.** Per-hub views/fetches/captures. Currently planned as a Pro feature.

## Bottom of mind — fun, not strategic

- Mobile native app.
- Apple Watch app.
- Voice capture with Whisper.
- AR document spatial layout. (Joke. Mostly.)
- AI-generated cover images for hubs.
- Custom CSS per hub.

## What I'd kill from the backlog

- Real-time collab. The cost is enormous; the demand signal is weak.
- Tasks / kanban. Different product.
- Notion-block-style embedded widgets. Different product.

## Decision rule

Anything in "top 5" only ships if the feedback from launch tells me it's the right next thing. The plan is a hypothesis; users will tell me which item to lift to actual roadmap.


---

## Concepts in this document
- **Real-time collaboration** _(entity)_
  Explicitly deprioritized due to enormous implementation cost and weak demand signal.
- **Inline graph_data in bundle URL** _(entity)_
  Load-bearing feature for cross-AI thesis; already shipping and documented in decision write-up.
- **User feedback validation** _(concept)_
  Core decision rule treating backlog as hypothesis requiring user signals to confirm roadmap priority.
- **Custom hub theme** _(entity)_
  Accent colour and typeface customization delivering perceived quality with one week of engineering effort.
- **Slack capture** _(entity)_
  DM-to-mdfy-URL feature reusing existing capture pipeline with OAuth complexity as main effort.
- **Email-in capture** _(entity)_
  Magic email address forwarding with spam protection as key differentiator from Slack approach.
- **Value-effort prioritization** _(concept)_
  Ranking framework organizing backlog into tiers based on gut-feel value and engineering effort balance.
- **Hub-to-PDF export** _(entity)_
  Portfolio-mode users need single PDF of all public hub docs using existing print CSS.
- **Concept-page editing** _(entity)_
  User-editable concept descriptions with light engineering cost enables bigger perceived feature impact.
- **Doc embedding macro** _(entity)_
  Include macro for compositional notes with recursion as primary engineering risk.
- **Activity dashboard** _(entity)_
  Per-hub metrics view planned as Pro feature with views/fetches/captures tracking.
- **Per-bundle layouts** _(entity)_
  Canvas painting options (timeline/tree/grid) add surface dimensionality for bundle owners.

## Concept relations (within this doc's concepts)
- **Inline graph_data in bundle URL** exemplifies top tier **Value-effort prioritization**
- **User feedback validation** governs feature selection **Value-effort prioritization**
- **Custom hub theme** exemplifies top tier **Value-effort prioritization**
- **Real-time collaboration** fails validation criteria **User feedback validation**
- **Slack capture** related alternative approach **Email-in capture**

_Hub canonical:_ https://memory.wiki/hub/demo
_Concept digest:_ https://memory.wiki/raw/hub/demo?digest=1&compact=1