Skip to main content

🚀 Roadmap

Our focus is on refining existing features to perfection while steadily expanding new functionalities on a stable foundation.

Our Principle

Less is more: Make existing features “usable, stable, and smooth” before carefully introducing new ones.

🎯 Short-Term Priorities (Ongoing)

  • Polish interaction details: consistent shortcuts, hover hints, and empty-state guidance.
  • Stability and performance: startup speed, memory usage, edge-case handling.
  • Usability improvements: clearer error messages and recovery suggestions, more complete documentation and guides.

We do not plan to add many features at once; our priority is ensuring a smooth user experience.

🧭 Planned Features (Under Evaluation)

  • Post-Parsing Text Editing
    Support in-place editing of parsed content while preserving original structure and formatting, providing common document editing capabilities.

  • AI Interpretation & Q&A
    Focused on “quick understanding” and “efficient retrieval” scenarios: e.g., question-on-selection, summary generation, key info extraction, and context-based answers (with priority on explainability and source referencing where possible).

⏱ Expected Timeline

Note

The following represents expected directions and is not a firm commitment; priorities will be adjusted based on user feedback.

  • Short term (1–2 minor releases):

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

    • Open “post-parsing text editing” experimentally to gather 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 referencing mechanisms.

🤝 How You Can Contribute

Follow Us

  • Submit feedback and use-case requests to help us prioritize effectively.
  • Point out clunky interactions or efficiency improvements; we will address them first.
  • Contribute to documentation: add examples, best practices, or FAQs.

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