Skip to main content

Roadmap

The 0.3.x line established the public API, documentation, web support, animation pipeline, and stable selection behavior needed by streaming apps.

0.3.0​

Complete:

  • Semantic public API names.
  • Public Dartdoc improvements.
  • Package logo.
  • Migration notes for 0.2.x users.

0.3.1​

Complete:

  • Internal code restructure for contributors.
  • Clearer parser, renderer, model, native, and worker layers.
  • Smaller renderer modules.

0.3.2​

Complete:

  • Docusaurus documentation site for samnn.dev.
  • Package metadata links for documentation.
  • Contributor-facing documentation.

0.3.3​

Complete:

  • AnimatedStreamingMarkdown.fromMarkdown for complete Markdown snapshots.
  • MarkdownSyncParser for short Markdown without isolate startup.
  • Shared parser warm-up API.
  • Parser benchmark demo comparing pure Dart, sync native, and isolate worker rendering.
  • GFM block content golden tests for sync Dart parser output.

0.3.4​

Complete:

  • Opt-in code block copy button.
  • Native parser release verification gate.
  • Zero-config Tree-sitter WASM build, verification, and published web loader.
  • KaTeX-compatible LaTeX rendering for inline and display math.
  • Static Flutter web chatbot demo embedded into the docs site.
  • Streaming table and chat demo stability fixes for the release line.
  • Parser benchmark publishing guidance.
  • iOS and macOS podspec metadata cleanup.

0.3.5​

Complete:

  • Flutter web platform metadata hotfix for the published WASM-backed build.

0.3.6​

Complete:

  • Render-backed selection with source-anchored ranges instead of a visual overlay-derived selection range.
  • Partial table-cell selection and dragging through tables into later blocks.
  • Vertical viewport and horizontal table edge auto-scroll while selecting.
  • Token compaction after animation settlement without layout jolts.
  • Gravity animation example with Fade restored as the default demo effect.

Next Priorities​

  • Optimize parser and renderer performance, especially stable-content render cost, token compaction, scrolling, and measurable benchmark coverage.
  • Develop new functionality in response to real application requirements and user feature requests, rather than committing early to speculative APIs.

Roadmap items can change based on package users, issue reports, and API risk.