Later, with no version yet

7 ideas

7 ideas with no version yet: longer-term themes, an iPhone and iPad exploration, and approaches still to evaluate.

After 1.0. Version numbers mark the intended order, not dates or paid upgrades; scope is provisional and may change with evidence and demand. Checked against the development repository on 15 October 2026.

In short

Ideas without a version number. Some wait on demand, some need evaluating before anyone commits to them, and one is a legitimate feature that simply isn’t scheduled.

Mac editing stays the priority: an iPhone and iPad version is an exploration for after macOS 1.0, and only if there’s demand.

Why it isn’t simple

  • An iPhone or iPad app isn’t a port. The Mac editor is built on the Mac’s own text and window system. An iPad version needs its own app shell, text host, touch and keyboard handling, and its own accessibility and performance proof.
  • Extensions mean running someone else’s code. Doing that safely means no access to your files, the network or the rest of the app, plus limits on time and output, and a way to decide what to trust. That’s why it starts as an evaluation.
  • Split editing of one document is subtle. Two panes on the same text each need their own scroll position, selection and layout, while sharing every edit and undo.

The 7 ideas

Theme System Refresh

Longer term

  • Separate app chrome, Raw syntax, Rendered/Table appearance and publication styles
  • Visual editor plus readable theme source where round-trip is deterministic
  • Stable portable themes, accessibility and safe existing-theme migration
  • Community sharing only after the local theme model matures

Depends on See it differently.

Product direction, October 2026Plan reference theme-refresh

Other source-backed representations

Undecided

  • JSON tree/table editing
  • YAML/TOML property views
  • Log/delimited column view
  • Source-mapped diagram interactions and front-matter metadata

Each representation must justify a useful, concrete workflow before it is committed.

Depends on See it differently.

Product direction, October 2026Plan reference later-adapters

iPhone / iPad exploration

If there’s demand

  • Identify reusable engines only against a real iPad target
  • UIKit/SwiftUI document/editor shell and TextKit host
  • Preview, math, diagrams, themes and source navigation
  • iPad files/workspaces, multiwindow, keyboard and touch
  • iPad-specific accessibility, performance and release proof

Deferred until after macOS 1.0, then subject to demand. No assigned version; Mac editing remains the priority.

Depends on Public macOS 1.0.

Product direction, October 2026Plan reference ipad

Evaluate JavaScriptCore extensions

Undecided

  • Sandboxed derived-content contributions and diagnostics
  • No filesystem/network/process or AppKit access; bounded time/output
  • Decide manifests, discovery, trust, conflicts and enablement UI

Design document only. No loader, manifest format or public API is implemented; in-process NSBundle loading is excluded.

Depends on Public macOS 1.0.

Source planPlan reference jsc

Evaluate out-of-process extensions

Undecided

  • ExtensionKit only if real demand justifies it

Depends on Public macOS 1.0.

Source planPlan reference extensionkit

Same-document split editing

Deferred

  • Shared content with independent layout/viewport ownership

Explicit legitimate post-1.0 feature; no schedule or epic commitment.

Depends on Public macOS 1.0.

Issue 112Plan reference split

Demand-led possibilities

Undecided

  • Optional local AI/semantic search
  • Plugin marketplace only if repeated demand justifies support cost
  • DOCX only after deterministic mapping from publication styles

Subject to demand; no committed scope. External CLI interoperability does not imply built-in AI or headless export.

Depends on Public macOS 1.0.

Product direction, October 2026Plan reference demand-watchlist

Open in the development repository

Titles as the developers wrote them, on 15 October 2026.

Not on the roadmap at all

  • Language-server IDE features, a terminal, a Git interface, a debugger or an AI sidebar.
  • A general plugin or theme marketplace, or a remote theme gallery.
  • A minimap, code folding, a hex editor, log tailing, SSH or SFTP, a global keyboard-shortcut editor or a Unicode inspector.
  • The full TextMate or VS Code snippet grammar.
  • Quick Look for every kind of source file, Spotlight, Share, Services or Finder Sync extensions.
  • More diagram languages, or new Markdown syntax.
  • ePub and hosted rendering. Word (DOCX) is only a later, conditional publishing candidate.
  • Windows and Linux.

What the labels mean

Longer term
an ambitious idea, not ready to build.
Undecided
needs evaluating, or a decision, before anyone commits to it.
If there’s demand
goes ahead only with clear demand and the capacity to support it.
Deferred
outside 1.0, with no schedule.