What's new in SimDeck

Why it matters

• - Teacher and student screens hold their square-paper layout better on tablet-sized review surfaces.
• - Long game names, card names, and metadata are less likely to push controls out of their panels.
• - The SimDeck icon now matches the square visual system used across the app.
• - Visual review screenshots capture rendered pages instead of loading skeletons.

Why it matters

• - David sees explicit action labels instead of generic controls while managing cards, students, roles, approvals, and restores.
• - Students get clearer search and empty-state language when their inventory filters return no active cards.
• - The demo reads as a sample classroom run instead of a technical sandbox.
• - Not-found and deletion messages explain what happened in classroom terms.

Why it matters

• - Students must choose David, Bank, or a classmate before sending a card.
• - Stale or duplicate send forms are blocked so classroom card state stays trustworthy.
• - David sees Bank cards separately from his reserve instead of mixing both piles together.
• - David can search the selected game roster and a student's current inventory before moving, using, restoring, archiving, or banking cards.
• - Card metadata can hide student Use/send actions without changing the Appwrite schema.
• - Students who join with a preseeded email attach to the prepared roster row instead of creating a duplicate.
• - Teacher and student desk data paths avoid extra Appwrite reads and repeated scans where safe.

Why it matters

• - Future updates have one canonical operational record instead of relying on memory or ad hoc notes.
• - David and reviewers can read what changed, why it matters, and how it was verified.
• - Future agents have explicit instructions to update Linear before updating the public page.

Why it matters

• - Students can distinguish card types faster without reading every full card first.
• - David can scan card libraries more quickly during setup and live class use.
• - Loading skeletons now better match the final card shape.

Why it matters

• - David has calmer live-class controls for the moments when students are actively using and sending cards.
• - Card import and restore flows are safer to use without developer support.
• - Teacher verification and handoff workflows are easier to trust before a classroom demo.

Why it matters

• - SimDeck better matches the classroom simulation desk direction David preferred.
• - Public pages are easier to navigate and explain during handoff.
• - The release ledger is reachable from the public navigation and footer.

Why it matters

• - David can pause risky student actions while setting up or ending a simulation.
• - Mistaken sends and used cards are easier to reverse.

Why it matters

• - The app feels more like a classroom tool and less like a generic admin panel.
• - The visual system is more consistent across public, teacher, and student screens.

Why it matters

• - The app reflects David's actual Tut 2026 and Zhongguo 2025 materials instead of placeholder cards.
• - Repeated cards are easier to maintain as templates.

Why it matters

• - Shared demo links do not expose real student data.
• - The demo can still be reviewed even if the backend is paused.

Why it matters

• - Students can join with a class code and their own password.
• - David controls approval, roster cleanup, and password support.

Why it matters

• - Teachers can manage games, students, cards, roles, and activity from one app.
• - Students only see their own inventory.

Why it matters

• - Another team can run SimDeck against its own Appwrite project.
• - The classroom data model remains explicit and handoff-friendly.

Why it matters

• - Established the first usable path for replacing paper card-state tracking.
• - Seeded the classroom simulations David needed for early review.