Quick to open. Deep when you want it. Easy to return to.
A browser game app for Chess, Solitaire, Theorisation, Checkers, Go, and Reversi that works on nearly any device with a web browser, including smart TVs, with controller support, fast play up front, and deeper tools waiting when you want to settle in.
Cardthropic is built to be welcoming on first launch and useful over time. You can begin in seconds on nearly any device with a web browser, including smart TVs, keep your place, and gradually discover deeper tools instead of being asked to learn everything up front.
The point is not just speed. The point is being easy to enter without becoming shallow after the first few minutes, and easy to return to later through installable progressive web app support with offline use in mind.
Games, analysis, and session data run locally on your device, not on a remote server.
Cardthropic does its work on your own device, inside your browser. Your device runs the game and analysis directly, instead of waiting on a remote server.
8x8 and 10x10 rulesets with mandatory captures, multi-jump continuation, and exact session restore
The goal is not to be a pile of random minigames. Cardthropic is meant to feel like one home for several kinds of games.
The chess side is for people who want more than just moving pieces around. You can play normally, or you can slow down and study a position in more detail.
Solitaire here is not just one disposable deal after another. You can replay the same setup, restart fast, and explore a run instead of losing it forever.
Theorisation brings a seeded hazard-grid deduction puzzle into the same product shell as the rest of Cardthropic. You can restart the same board, return to unfinished runs later, and keep the same calm session flow whether you want a quick puzzle or a longer deduction session.
Checkers in Cardthropic is built around exact engine-backed play instead of a simplified board toy.
Multiple 8x8 and 10x10 rulesets live in the same family, with mandatory captures, continuation, crowning behavior, undo/redo, and save/restore staying consistent across the whole app.
8x8 and 10x10 rulesets in one shared product shellOne of the best parts of Cardthropic is that it is built to be returned to. Your active sessions, paused games, and finished runs can all live together in one place.
Cardthropic is already usable, and it is still getting better. The goal is to keep the surface calm and approachable while adding more depth over time.
Cardthropic is a local-first browser game and study app that combines multiple game families, reproducible seeds, exact restore, and shared continuity tools in one place. Rather than treating sessions as disposable, it is designed to support both quick play and longer study in the same product.
The current families include Chess, Solitaire, Theorisation, Checkers, Go, and Reversi. Inside those families there are multiple modes and variants, including solitaire variants such as Klondike, Yukon, Scorpion, Pyramid, Spider, Forty Thieves, and FreeCell, plus Theorisation branches such as Deduction and the Triclidean modes.
Cardthropic was created by Emily Tiffany Joy. It is a single-author project with a very specific product identity, which is part of why the app tries to keep one coherent language across very different game families instead of feeling like a bundle of unrelated tools.
It is currently funded through optional donations. The app is free to use, with no account wall, no subscription gate, and no “premium analysis” split between basic and paid users at this stage.
The long-term direction is not just “more games.” It is a stronger local-first product shell: deeper shared continuity, better study tools, more polished families, and more thoughtful game-specific systems that still feel like one home instead of a pile of separate apps.
The project is built in Rust, with egui as the UI framework, glow-backed rendering in the graphics stack, and WebAssembly for the web build. That combination is what lets the same core product run as a full-featured browser app instead of a traditional server-rendered website.
The important work runs on your device. The browser loads the app, but gameplay, analysis, and normal session logic execute locally rather than waiting on a remote server to drive every move or computation. That is a major reason the app feels direct once it is loaded.
Yes. On supported browsers, Cardthropic can be installed as a progressive web app, which gives it a more app-like return path while still keeping the same browser-based foundation underneath.
It is designed to be offline-friendly once the app is already available on your device, especially through the installable progressive web app path. Normal local gameplay and session work fit that model well, while first loads, updates, and outward-facing actions such as external analysis naturally depend more on connectivity.
Yes, as long as the device has a capable enough browser. Cardthropic is meant to be useful across touch-first devices, keyboard-and-mouse setups, controller-friendly setups, and large-screen browser surfaces rather than assuming one ideal input style.
Yes. Controller support is a real part of the product, not an afterthought, which is one reason the app works unusually well on TVs, couch setups, and other browser-ready devices where a gamepad is more natural than a mouse or touch-only workflow.
Yes, if the TV has a reasonably recent smart-TV browser. Controller and remote-friendly workflows are part of the design, but older or weaker TV browsers are often the least forgiving environment, so the best results come from more recent smart-TV browsers or connected devices with stronger browsers.
A recent browser is the main requirement. Modern desktop and mobile browsers generally do best, recent smart-TV browsers can work well, and older embedded browsers are the most likely place to see rough edges first because they tend to lag on browser features and performance.
It does not require an account. You can use it without signing up, which fits the project’s local-first design and its preference for quick entry over building a hosted identity system around the whole experience.
Normal session continuity is stored locally in your browser or installed app context rather than being centered on a server-side account. In practice, that means your sessions and preferences usually travel with the browser profile or installed instance you actually used.
No account is required, and Cardthropic is not built around cloud sync. Progress and continuity are usually stored locally on the device or browser profile you used, unless you deliberately move game data through one of the supported export or sharing paths.
Not as the default workflow. Core gameplay and study are local. Data leaves your device only when you deliberately use an outward-facing path such as external analysis or another sharing mechanism that is explicitly meant to send something somewhere else.
If the same browser profile or installed app context is still there when you return, Cardthropic is designed to restore meaningful in-progress state instead of treating your session like a disposable tab. Exact behavior varies by family, but continuity is a core product goal rather than an afterthought.
Family-specific file workflows are meant to stay local-first too. When you load or work with local game files, the design goal is to let you inspect, replay, and study them in the browser without automatically turning that into a server upload workflow. The exact file tools vary by family.
Cardthropic uses its own engines, rules logic, and local automation systems. The built-in analysis layer is part of the same project rather than a thin wrapper around a stack of bundled outside engines.
No. Cardthropic’s built-in analysis and automation are native to the project. When stronger outside analysis is useful, some modes can open Web Analysis in a new tab instead of bundling heavyweight third-party engines directly into Cardthropic.
Cardthropic’s built-in analysis is designed for readable local study, not for competing with top standalone engine stacks. Its engines are aimed more at practical, intermediate-strength, human-like study inside a browser-based local app than at maximum engine strength.
It means Go records, review, and branching study are handled in a way that fits SGF-style game trees instead of flattening everything into a chess-style move list. In practice, that means Go study flows are meant to respect SGF-style review, move trees, and board analysis rather than treating every game like PGN.
Many families already support repeatable study sessions through seeds, history, exact restore, replay, and family-specific file or library tools. More structured challenge systems and authored study surfaces exist in some parts of the app and are still growing in others, so the answer is increasingly yes, though not yet as one uniform feature across every family.
It is built to support both without forcing you to pick one identity for the whole app. You can open a game quickly, keep the session simple, and leave, or you can stay with the same run and use seeds, restore, history, replay, and deeper tools to turn it into a longer study loop.
A seed is the reproducibility handle for a run. In supported families it recreates the same opening state, and in some modes it also governs future randomness such as refill or deal order, which makes retries and comparisons meaningful instead of turning every restart into a different problem.
It means returning to the real in-progress state you left, not merely reopening the same family or mode. The current position, relevant setup choices, and family-specific runtime context are restored so the resumed session still means the same thing.
No, and that is intentional. Cardthropic tries to keep unsupported tools visibly unavailable instead of faking parity. Some families already support deeper shared surfaces such as Robot, Move Palette, import/export, or analysis bridges, while newer families are narrower until those surfaces are genuinely ready.
Cardthropic can remember active sessions, finished runs, recent work, local preferences, and some game-family-specific progress such as locally cleared starter challenges. Because the app is local-first, that continuity usually lives with the browser profile or installed app instance you actually used.
They are related but not interchangeable. Magic Wand is a one-step assist, Robot is continuous automation, and Computer Player is a side assignment in supported competitive games where the computer takes White, Black, or neither as an ongoing role.
Yes. That is one of the clearest Cardthropic patterns across families. Seeds, undo/redo, restart, history, and exact restore make it practical to retry the same situation and see how different early choices change the branch instead of forcing you to accept one line and lose the rest.
In many parts of the app, yes, but the exact path depends on the family. Some modes expose PGN-style import, Copy/Paste Game, Clipboard Remote Play, Web Analysis, or other game-specific export flows, while newer families may intentionally defer those surfaces until they are truly supported.
It is generally approachable on modern devices, but the app still depends on your device because the work is local. Lighter play surfaces are easy to run almost anywhere with a decent browser, while heavier local analysis and larger browser sessions naturally ask more from weaker devices or older TV browsers.
The browser is a great portability layer, but it still imposes limits around performance ceilings, storage behavior, file APIs, and the uneven quality of embedded browsers on some devices. Cardthropic leans into the strengths of the browser while accepting that a local browser app is not the same thing as a heavyweight native desktop engine lab.
No full network-play layer is planned. Cardthropic already has Clipboard Remote Play for lightweight handoff between two copies of the app, and that fits the project much better than taking on a full online networking stack, which would add a great deal of complexity without matching the current roadmap.
Cardthropic is for people who want a game app they can open quickly, enjoy immediately, and return to later without starting over.