ROADMAP

v1.5.0 - Commercial Viability

One-click website publishing

  • Onboarding screen shows only logo, tagline, and "Get Started" (plus a subtle advanced menu)
  • "Get Started" creates an anonymous user in the database. Gives them access to free tier functionality.
  • Sets up workspace with default bundle. Automatically publishes their workspace as a website. Workspace contains 2-3 audience demo.

Overhaul audience filtering UI.

  • First, overhaul LeftSidebar filetree to make one-click audience filtering for files easy. Files should show their audience status somehow, perhaps with colors or icons
  • Second, introduce a "audience highlighting" UX for inline audience filtering. Click along the left side for paragraph filtering, highlight text for inline filtering. Could be stored in markdown as pandoc-style selectors:

Publish plugin

  • Phone number/SMS support
  • Alternative theming support for website publishing
  • Support rich interactive content in websites (like Ammon's demo)

Other

  • Publish Obsidian plugin
  • Make sync plugin work if not already
  • Big upgrade to plugin-import and plugin-pandoc
  • Finish TestFlight and publish to app store

v1.6.0 - Real world usability

  • Pages format—either use premium TipTap plugin, or make a bespoke one.
  • Support for arbitrary rich/CSS styling via custom markdown syntax
  • Quick notes! A key command similar to CMD+Space on Mac, or a similar "launchpad" shortcut, to record a note quickly. Needs thought for giving it a spot/attaching an audience quickly. Simplest method: pre-configured space for quick notes. Should Extism plugins be able to also be a Tauri plugin?
  • AI agents sort notes for you?

Would be cool (long term, low priority)

  • Abstract away kinds of metadata—instead of YAML frontmatter, why not TOML, JSON, or other format? Why not endmatter or an arbitrary metadata code block?
  • Integrate diaryx_sync crate. How much can go into core, how much in the plugin? Currently shared by sync plugin, share plugin, and diaryx_sync_server
  • Interactive functionality in published Diaryx
  • More servers/load balancing for diaryx_sync_server (microservices?)
  • In the marketplace:
    • UI sounds packs
    • UI/keyboard haptics packs
    • UI animations packs
    • Themes can adjust size/padding of UI components
  • Either trademark "Diaryx" so I can name my app that (taken on App Store) or take suggestions for different names. (Some have suggested "Diary-X" or "Diary X")

AI plugin

  • Pin down Diaryx philosophy with AI, brainstorm good AI integrations
  • “AI iframe” plugin, similar to Claude’s interactive diagrams?

Dreams (long term, high priority)

  • Different UI chrome. The only webview needed is for the TipTap editor—everything else could theoretically use a different UI. Possibly test with a Tauri plugin to turn sidebars into SwiftUI, similar to the mobile toolbar plugin.
  • Persistent identifier support for qualified files (ARK). Useful for academia/family history.
  • Integration with FamilySearch API for family history records—import/export
  • Per-audience workspace settings
  • diaryx_sync_server takes plugins and handles only server compute primitives, auth, and billing (sync logic owned entirely by sync plugin, publish logic owned entirely by publish plugin, etc.)

Possible Marketing Angles

  • AI-native journaling
  • CMS (compete with Substack, Wordpress, Ghost)
  • B2B (group announcements for organizations)
  • Super customization--by workspace, by audience?