Roadmap
Ecosystem direction
Section titled “Ecosystem direction”High-level, non-dated intentions (details live per product):
- Multi-vendor RFID → TigerData — retrieve the data from manufacturer tags (Bambu Lab, Creality, Elegoo, Anycubic, Snapmaker, Qidi, OpenSpool) and convert it into TigerData digital spools, so other brands’ filament can be scanned and managed in the ecosystem; the read-only specs are already documented (compatibility). Direct in-app decoding is deliberately not integrated until the interoperability model is settled.
- More printer integrations — Klipper/Moonraker as the next natural transport (Klipper page).
- A distributor map (planned) — official distributors are growing beyond Atome3D; a map will show where to buy TigerTag chips locally.
The— shipped in Tiger Studio v2.14.0: the.ttagportable file.ttagformat (export + import, all three spool tiers).- TigerTag for resins — extending the protocol to resin containers for resin 3D printers, bringing the same open identity to a whole second family of machines.
- TigerHub growth — the ecosystem site at tigersystem.io: richer social-sandbox features (wishlists, friends, sharing).
- Documentation — fill the TODO placeholders across this repo (tutorials, guides, manufacturer onboarding, RFID payload summary).
- Documentation languages — the wiki at wiki.tigersystem.io ships in English and French first: English is the source of truth, French is derived from it and reviewed. Once both are complete and the pages have stopped moving, the remaining tigersystem.io locales follow — German, Spanish, Italian, Polish, Chinese, and Portuguese in both its Brazilian and European variants, which the ecosystem treats as two separate locales — so the documentation lines up with the rest of the ecosystem. Adding them earlier would mean maintaining nine copies of pages that are still being written.
- Beyond the current locales — the list is not capped at what tigersystem.io serves today. Japanese, Korean and Russian are the strongest candidates after it: all three have active maker communities, and all three are places where English-only technical documentation is a genuine barrier rather than a mild inconvenience. Russian also reaches well beyond Russia. Note that a language can be worth documenting even where the shop cannot ship — the protocol is open, any blank NTAG chip works, and nothing in the ecosystem requires buying anything.
Which languages are actually added should be settled from the wiki’s own
traffic once it has some, not from guesswork. It also need not be
all-or-nothing per language: the user-facing sections (tutorials, FAQ,
products, compatibility) earn a translation long before
developers/ does, whose readers already work in
English.
Detailed roadmaps
Section titled “Detailed roadmaps”| Product | Where |
|---|---|
| Tiger Studio | ROADMAP.md in the app repo — grouped by domain, with sizing and risk notes |
| Other products | > TODO: publish public roadmaps as the repos open up |
Note: this page states direction, not commitments or dates.
Related: Products, Compatibility