Skip to content

Latest commit

 

History

History
57 lines (47 loc) · 2.46 KB

VISION.md

File metadata and controls

57 lines (47 loc) · 2.46 KB
Raw

Vision

This document describes our initial ideas and roadmap for developing Embroidery Studio.

If you have any ideas, don't hesitate to contact the author via email or in Telegram chat. We are open to any contributions.

Features

Here is a list of features we will implement one day. It is not a complete list; it will grow over time. You can suggest your ideas, too.

  • Support the most popular desktop platforms:
    • Windows 10/11 via the .msi installer
    • Linux
      • Debian-based via the .deb package.
      • RPM-based via the .rpm package.
      • Other distros via AppImage/Flatpak/Snap.
    • MacOS via App Bundle.
  • Support the mobile platforms:
    • Android via Google Play.
    • iOS via App Store.
  • Support the most popular cross-stitch file formats:
    • OXS (in progress)
    • XSD (in progress)
    • XSP
    • PAT
  • Support the most popular cross-stitch progress formats:
    • DIZE
    • SAGA/CSS
  • Support importing patterns from PDFs.
  • Provide the ability to design cross-stitch patterns (in progress).
  • Provide the ability to convert patterns.
  • Provide the ability to export patterns into PDF.
  • Provide the ability to export patterns into various machine embroidery formats.
  • Provide the ability to track the progress during cross-stitching.
  • Provide the ability to convert images into cross-stitch patterns.
  • Provide the ability to generate patterns using AI.
  • Provide the ability to distribute cross-stitch patterns in the store.
  • Provide the ability to collaborate with other cross-stitchers on the shared pattern in real time.
  • Provide the ability to store patterns in cloud storage (Google Disk, OneDrive, etc.) and in our custom cloud.
  • Make it possible to extend functionality using plugins.
  • Make it possible to encrypt patterns so users can safely share copyrighted patterns over the net.

And many, many more...

Plan

First, basic features must be implemented to make the application useful as soon as possible and start growing the user community. Then, we will have to stabilize the API and release it stably. After that, we can continue implementing all other fantastic ideas.

It will take a long time for us to release a stable version. But we are not afraid of that; we are encouraged by it.

We want to engage more and more people in developing so it can ship updates quickly.