Multi-Device Sync

Easchi adopts a storage structure of “one flashcard corresponds to one note file + one metadata file + one review record file.”

For power users with tens of thousands of flashcards, assuming 30,000 cards, that corresponds to as many as 90,000 tiny files. If traditional per-file syncing were used, it would cause catastrophic network I/O latency.

Built-in Sync

Easchi provides a specially optimized built-in sync solution:

Automatic packing and merging: Before uploading, the sync engine automatically packs and compresses the fragmented flashcard data and review history into a single efficient data packet.
Incremental and full backup: A hybrid of full and incremental backups is performed per file library, significantly improving the sync speed of small files in weak network environments.
Flexible version cleanup: Allows you to flexibly configure and clean up earlier historical versions to free up cloud space.

💡

If you absolutely do not want to use built-in sync, manually performing a full download of hundreds of thousands of fragmented files before opening the app and a full upload after exiting would result in a long wait. To pursue the ultimate sync throughput and time efficiency, we strongly recommend using the built-in dedicated sync channel.

Custom Sync

If you do not use the built-in sync feature, it is recommended to use version control software such as Git in combination with a code repository.

The reason is that the content of flashcard history files is continuously growing. If you use a sync method that lacks automatic merge capability, local flashcard data can easily be overwritten incorrectly, thereby disrupting your review plan and causing partial data loss.