LM Cards 1.0: The Full Card Studio Is Now Native to LMOS
LM Cards has moved from its separate app runtime into the shared LMOS project, account, entitlement, collaboration, feedback and recovery systems while keeping the 100-card library, handwriting engine, four-surface 3-D proof and print/export tools.
What changed
Registered LM Cards as a first-class LMOS specialist app with its own app identity and version.
Moved card project persistence to shared LMOS projects and autosave instead of the standalone card_projects table.
Moved access and billing responsibility to LMOS entitlements instead of a second Stripe/access runtime inside Cards.
Reused the shared LMOS team, task, file, conversation, notification, analytics, feedback and project-history engines.
Ported all 100 Signature Collection cards and all twenty writing personalities.
Ported Writer DNA, seeded handwriting sessions, pen profiles and humanization controls.
Ported the true four-surface 3-D card proof with Front, Inside, Back, fold animation, spin, lighting, Fit, Reset and zoom.
Ported PDF, JPEG and direct-print output.
Copied all eight Cards art backgrounds into LMOS-hosted storage so the old standalone host is not required for card art.
Moved handwriting QA/reference tables and the owner review lab into the LMOS database/control center.
Added an LM Cards How-To guide and shared product feedback path.
Lazy-loaded the Cards editor so its handwriting fonts and 100-card catalog do not increase the initial load for unrelated LMOS studios.
The architecture rule
LM Cards is now a specialist application inside the operating system. Cards owns card-making behavior. LMOS owns identity, projects, permissions, autosave, recovery, collaboration, entitlements, feedback and the wider project graph. That removes duplicate infrastructure while preserving the focused editor.
What testers should try
Create a new LM Cards project from the App Store and choose a Signature card.
Change the front wording, wait for the shared Saved state, leave the project and reopen it.
Open the card in 3-D and verify Front, Inside and Back remain independent surfaces.
Switch handwriting personality and pen profile, regenerate the hand, and verify the project reopens with the same saved seed.
Export a PDF or JPEG and inspect both outside and inside pages.
Use the project-level LMOS feedback, history, tasks, conversation and connected-project controls around the Cards editor.
Use the beta on real work.
The most useful feedback is not “I like it.” Tell us where you hesitated, what took too many clicks, what did not save the way you expected, and what would make this useful enough to return to next week.
