Skip to main content

🚀 Roadmap

We focus on refining existing features to perfection while steadily expanding new capabilities on a stable foundation.

Our Principle

Less is more: Perfect the current features to be "usable, stable, and smooth" before cautiously introducing new ones.

🎯 Short-Term Focus (Ongoing)

  • Refine interaction details: consistent shortcuts, hover tips, empty state guidance.
  • Stability & performance: startup speed, memory usage, edge case handling.
  • Usability improvements: friendlier error messages and recovery suggestions, complete documentation and guidance.

We don’t plan to add a large number of features at once; our priority is making the experience smooth and seamless.

🧭 Planned New Features (Under Evaluation)

  • Post-Parsing Text Editing
    Allow in-place editing of parsed content while preserving the original structure and formatting as much as possible, with common document editing capabilities.

  • AI Interpretation & Q&A
    Designed for "quick understanding" and "efficient retrieval" scenarios: e.g., contextual Q&A, summary generation, key information extraction, and answering questions based on context (with controllable explainability and source referencing as a priority).

⏱ Timeline Expectations

note

These are expected directions, not firm commitments; priorities will adjust dynamically based on user feedback.

  • Short term (1–2 minor releases):

    • Deep refinement of existing features and bug fixes.
    • Add operational tips and guidance, improve observability (logs and error messages).
  • Medium term (2–4 minor releases):

    • Release "Post-Parsing Text Editing" experimentally to collect real-world feedback.
    • Adjust interactions and data models based on feedback.
  • Long term (after more feedback):

    • Continuously iterate AI interpretation and Q&A capabilities, exploring more natural interactions and robust source referencing.

🤝 How You Can Participate

See: 《Follow Us

  • Submit feedback and usage scenarios to help us prioritize effectively.
  • Highlight inconvenient interactions or improvement suggestions; we will address these first.
  • Contribute to documentation: add examples, best practices, or FAQs.

Thank you for your attention and support! Every piece of feedback directly influences the direction of our next improvements.