---

Now, about data storage, you have two options:

1.) store data on your server (not recommended) and hand out the ticket* to the user to use in a URL. Pros: can open the same project on any device. Cons: someone would have to pay for storage, would have to fend off abuse or introduce data expiry, and so on (huge hassle).

2.) store data in user browser's local storage (recommended) and hand out the ticket to the user to use in a URL. Pros: your server has to store no data. Cons: once created, the flashcard player can only be used on that one browser/device. No big deal, if needed on another device, the user can start the data-ingestion flow again from that other device and thus get another ticket* and run the playback of the same flashcard set on another device.

*ticket would be just a random string that would identify the dataset and would be a query parameter in the URL. It would be up to the user to bookmark that URL and give it a sane name.

---

Now, to answer your questions:

> 1.) the main need is to have a link you can prepare in advance and revisit anytime, so you can review flashcards fullscreen, one by one, from any device (like a phone or tablet)?

Yes. A phone, a tablet, a TV, an e-ink panel, a raspberry Pi device... any device that has a decent enough browser. That's why the flashcard page itself has to be as simple as possible. Maybe a set title, the card number out of total number, and that's it. The only possible interaction should be a click anywhere on the screen.

> 2.) would you use it as your main way to study, or more as a casual daily reinforcement tool?

Casual daily reinforcement tool.

Thanks.