AnymeX is a Flutter tracker that syncs progress to AniList, MyAnimeList and Simkl

Three services, one list, official APIs only

AnymeX is a multiservice tracking client designed exclusively for managing and tracking anime and manga progress across AniList, MyAnimeList and Simkl, and the description calls it a multiservice tracking client.

The multi-service part is the differentiator. Most trackers integrate with one service, and if you use two you maintain two lists. AnymeX writes to all three, which means the progress you record in the app can be reflected across the services you actually use rather than the one the app happens to prefer.

The Simkl inclusion is the unusual one. AniList and MyAnimeList are both anime and manga lists with years of community metadata behind them, while Simkl covers a broader media catalogue that includes television and film. The repository topics reflect that mix, with anime, manga, novel, android, flutter, linux and windows listed.

The integration is stated as limited to the official APIs of the supported services, and that constraint is what makes the project viable at all, since a client that scraped the websites would break whenever the markup changed and would be in a legally murkier position.

The application is written in Dart with Flutter, which is visible in the repository layout: android/, ios/, linux/, macos/, windows/ and web/ directories are the Flutter platform folders, and the presence of a .fvmrc file pins the Flutter SDK version the project expects, with .metadata and .vscode/ for the editor and tooling.

The disclaimer is the product's clearest statement

The README carries a prominent IMPORTANT block, and it is worth reading as a design constraint rather than as legal boilerplate, because it tells you what the application is and is not.

AnymeX is a tracking tool only. It does not host, provide, distribute or endorse any streaming content, media or third-party extensions. It integrates only with the official APIs of the supported services, and third-party extensions are the responsibility of their creators.

Then the user responsibility clause: users are solely responsible for how they use the app and any third-party services or extensions they choose to interact with, and must comply with all applicable laws, copyright and intellectual property rights. The no liability clause disclaims responsibility for misuse, legal issues or violations arising from user actions, and says legal concerns including DMCA claims should be directed to the respective third-party services rather than to AnymeX.

The final line is the one that makes the whole thing coherent. By using AnymeX you agree to comply with the Terms of Service, which live in TOS.md, and the README asks you to review them to understand the DMCA-compliant tracking functionality and the non-involvement with any content or services beyond the three named.

This positioning is a deliberate engineering decision. A client that is unambiguously a client, talking to official APIs and shipping no content, is in a very different position from an app that bundles or links to streaming sources. The repo/ directory at the top of the tree, referenced by the iOS sideloading source URLs, is part of that: it holds a source.json for alternative app distribution, which is how sideloading works for a Flutter app on iOS.

The licence situation is split in a way worth noting. The licence is MIT, with LICENSE.md at the top level, and the Terms of Service are a separate document in TOS.md.

Distribution covers desktop, mobile, web and package managers

The downloads section shows a project that has thought about distribution per platform, and the badge row covers android, ios, windows, linux and macos.

For Windows there are two package managers, with Scoop and a Chocolatey package named com.ryan.anymex, both linking to INSTALLATION.md. For iOS the README lists sideloading sources, with an AltStore source and a Feather source, both pointing at a source.json in the repo/ directory on the main branch. There is a stable release on the main repository and a separate beta release on a preview repository, and the README links a CodeFactor grade badge.

The iOS sideloading route is the detail that reveals how the project is actually distributed. AltStore and Feather are sideloading tools for iOS, and the fact that the project publishes a source.json for them rather than only an App Store listing says the app is not in the store. That is consistent with a project that wants to distribute freely and to a wide language base without an Apple review process in the way.

The localisation is the other thing the README spends a lot of space on. The top block lists the project in more than twenty languages, with links to a translation viewer at openaitx.github.io for Arabic, Assamese, Bahasa Indonesia, German, English, Spanish, Persian, French, Hindi, Italian, Japanese, Korean, Dutch, Polish, Portuguese, Russian, Thai, Turkish, Vietnamese, Traditional Chinese and Simplified Chinese. The Weblate badge in the source is commented out, which suggests the translation platform changed, and the openaitx viewer is the current route.

For contributors, the repository has DEVELOPMENT.md, a CHANGELOG.md, a firebase.json, a fastlane/ directory, hook/ and scripts/ directories, and a packages/ directory, which is where a Flutter monorepo puts shared Dart packages.

The repository layout is a Flutter app with a plugin architecture

Looking at the top level of the tree tells you how the project is organised, and a few entries stand out.

There is a packages/ directory, which in a Flutter project means shared Dart packages rather than a single monolithic lib/. The lib/ directory holds the application code, assets/ holds images and the logo, and there are platform folders for android, ios, linux, macos, windows and web, so the app is built for all six targets from one codebase.

Two files at the top level are unusual for a Flutter project and worth understanding. package_manager.dart and version_manager.dart are not part of the standard Flutter scaffolding, which suggests the app manages its own platform packages and version numbers rather than relying on the build system alone. The scripts/ directory and the fastlane/ directory then handle the actual release work, and firebase.json points at Firebase for distribution or crash reporting.

The analysis_options.yaml and devtools_options.yaml files are the Dart and Flutter analysis configuration, and pubspec.yaml with pubspec.lock is the Dart package manifest, which is where the dependency list and the Flutter SDK constraint live. The .fvmrc file pins the Flutter version so a contributor's toolchain matches.

The chocolatey/ directory holds the Chocolatey packaging for Windows, which pairs with the chocolatey/ badge in the README, and the github_assets/ directory holds images used in the release notes and the repository itself.

The result is a project with real release engineering behind it, which is a fair amount of infrastructure for a tracker, and it reflects the fact that the app is distributed as binaries across five platforms rather than as a web page.

Where AnymeX is the wrong choice

The first limit is the one the project itself foregrounds, and it is worth restating plainly. If you want an application that gives you things to watch, AnymeX is not it. The README says it is a tracking tool only and does not host, provide, distribute or endorse any streaming content, media or third-party extensions. Anyone who installs it expecting a catalogue will find a list manager, and the README's mention of third-party extensions is about responsibility for them, not about the app providing them.

The second is that the value depends on your account, not on the app. Everything AnymeX does is mediated by AniList, MyAnimeList and Simkl through their APIs, so its features are bounded by what those services expose and permit. The README does not describe which parts of a service's API it uses, and it does not say what happens when a service changes its API or restricts an endpoint. Your progress lives in those services, and the app is a front end to them.

The third is the platform question. The project builds for six platforms, but the distribution story is uneven. Windows has two package managers and Linux has a directory in the tree with no package or install path described in the README section, so a Linux user is left pointing at INSTALLATION.md. iOS requires sideloading. Anyone expecting a uniform install story across platforms will find it does not exist.

The fourth is the account linking. The app writes to three services, which means it authenticates against three of them, and the README does not describe the credential handling, the token storage or the revocation path. The privacy claim in the README is about the developer not collecting user information, which is a statement about the project's own behaviour rather than a description of what the app stores locally.

The fifth is scope. AnymeX tracks progress for media that those services catalogue. It is not a downloader, a reader or a source aggregator, and the repository has no such code. That is a feature for the people who made it, and a limit for anyone who wants one application to do everything.

Editorial conclusion

AnymeX suits someone who keeps their list in one of the three supported services and wants a single client that writes to all of them, particularly on a platform where the official mobile apps are thin. It is the wrong tool if you expect it to provide titles to watch, because the README is explicit that it is a tracking tool only and hosts no content, and it is the wrong tool for a platform without a build, since the project ships desktop, mobile and web targets but not a Linux package you can install without reading INSTALLATION.md. Before adopting it, read TOS.md and the DMCA-compliant tracking language, since the terms are part of how the project positions itself, and verify that your account can be linked on the services you use.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. README
4. Releases
5. RyanYuuki/AnymeX on GitHub