Han1mePlus: a Flutter Hanime1 client for Android, iOS, macOS and Windows

The gap Han1mePlus fills: a Hanime1 client that is not a browser tab

Hanime1 is a website. On a phone, that means a mobile browser, its tab management, its video element, and whatever the site's own layout does at small widths. Han1mePlus exists to replace that with a native application: the README describes it as "a Hanime1 third-party client built with Flutter" that follows Material Design 3 and aims at a modern, very smooth viewing experience. The audience is narrow and explicit. The licence section states the app is for adults aged 18 and over, and it is not affiliated with Hanime1 in any way. If you are not in that group, or you want a general-purpose browser, this is not aimed at you.

The interesting part is the platform list. Android, Windows, iOS, macOS and Linux all appear under platform support, which is the normal consequence of choosing Flutter: one Dart codebase, several shells. A client that only shipped on Android would be a much smaller project. Shipping four or five targets from one repository is a different maintenance problem, and the README's own contribution notes acknowledge the shape of that problem by saying the project is maintained by one person and intends to stay that way.

How the Flutter and Dart codebase is laid out

The repository is a standard Flutter application layout. pubspec.yaml declares the Dart package and its dependencies, lib/ holds the Dart source, and android/, ios/, macos/, linux/ and windows/ are the per-platform runner projects that Flutter generates and that you build against. assets/ holds bundled resources such as the logo referenced at the top of the README, and c/ appears as a top-level directory, which suggests some native or C-level component is compiled alongside the Dart code. l10n.yaml plus the localization setup indicates the UI strings are generated from ARB-style files rather than hardcoded, and analysis_options.yaml pins the lint rules the author expects contributors to satisfy.

Two files say a lot about how the project is built. .fvmrc means Flutter Version Management is used, so the SDK version is pinned per repository instead of being whatever happens to be on your PATH. .flutter-plugins-dependencies is a generated file that lists the plugin set resolved for the current platform. Together they mean a reproducible build depends on installing the right Flutter channel before you touch anything else. The README does not describe the data flow between the app and Hanime1, so how requests, caching or playback are handled is not something the documentation states; you would have to read lib/ to know.

Installing Han1mePlus and a first run

The README's download section is one line: go to the Releases page and download the latest version. There is no package manager, no app store listing and no install script, so the release assets are the supported path. Release v1.1.8 was published on 2026-09-02, with v1.1.7 on 2026-08-29 and v1.1.6 on 2026-08-23 before it. Pick the asset matching your platform, install it the way that platform expects, and launch it.

If you want to build from source instead, the pinned SDK is the first thing to respect. The README badges state Dart 3.0+ and Flutter 3.0+, and .fvmrc pins the version the author actually uses. The README gives no build commands of its own, so there is nothing to quote from it here. What the repository does give you is the dependency manifest and the platform runner folders: pubspec.yaml under the repository root is the file Flutter reads to resolve packages, and android/, ios/, macos/, linux/ and windows/ are the directories a build targets.

The README also does not document signing, notarization or store submission, so treat those as your own problem. On Android the README badge sets the floor at Android 8.1.

Where Han1mePlus is the wrong choice

The README's disclaimer is unusually blunt and worth taking literally. The project is provided as-is, and the developer does not guarantee continuity, stability or security of the program, and accepts no liability for loss, damage, account problems or legal disputes arising from use. That is not boilerplate you can skim past. It means there is no uptime commitment, no compatibility promise, and no expectation that a future Hanime1 change will be handled quickly.

The maintenance model reinforces this. The README states the project is maintained by one person and is intended to remain that way, and it directs all suggestions, feature ideas and bug reports to GitHub Issues. There is no contributor ladder, no release cadence commitment and no documented deprecation policy. If your requirement is a client with a support channel, a security response process or an SLA, this project does not offer one and does not pretend to. The same applies if you need to embed the client in a commercial product: AGPL-3.0 plus an as-is disclaimer is a combination you should read carefully rather than assume is fine.

There is also a scope limitation that the README never addresses: it does not explain what happens when the upstream site changes its markup, its player or its endpoints. A third-party client inherits that fragility by construction. Nothing in the repository documentation describes a fallback, a compatibility layer or a version-negotiation mechanism.

Han1mePlus compared with Han1meViewer

The README credits Han1meViewer, described as an excellent open source project that provided reference and inspiration. Both are third-party clients for the same site, so the choice between them is not about features you can read off a list. It is about the stack and the surface area.

Han1mePlus is a Flutter and Dart application with Material Design 3 styling and build targets spanning Android, iOS, macOS, Windows and Linux. That means one language across the whole UI, a widget toolkit rather than platform-native controls, and a build that depends on the Flutter SDK version pinned in .fvmrc. Han1meViewer is credited as the earlier project that inspired this one, which makes it the more established of the two in terms of lineage, though the README gives no feature-by-feature comparison and no migration guidance. If you are deciding between them, the honest answer is that the documentation here does not support the comparison. What it does tell you is that Han1mePlus chose Flutter deliberately, and that choice is the main thing you are buying: consistent rendering across five platforms from one codebase, at the cost of a heavy SDK dependency and a UI that looks like Material Design 3 rather than like each platform's native idiom.

Licence terms and what AGPL-3.0 means for a client app

Han1mePlus is licensed under AGPL v3.0, and the README points at the LICENSE file in the repository root. The README adds that users must strictly comply with the terms. The practical consequence for an application rather than a server is that if you modify the code and distribute the result, including over a network, the AGPL's source-availability obligations attach to what you distribute. Forking for personal use and building your own binary is a different situation from shipping a modified build to other people.

There is a second layer the README raises separately from the licence: it says users are responsible for their own compliance review, ensuring their behaviour matches the terms of service of the platform being accessed and applicable law. Those are two distinct obligations, and the README keeps them apart. It does not claim the app's use of the site is authorised, and it does not offer an opinion on whether it is. This is a description of what the project states, not legal advice; if the distinction matters to you, that is a question for a lawyer, not for the README.

Release cadence and the cost of keeping a fork current

Three releases landed in the eleven days before the last push on 2026-09-02: v1.1.6 on 2026-08-23, v1.1.7 on 2026-08-29 and v1.1.8 on 2026-09-02. That is a fast patch rhythm for a single-maintainer project, and it tells you something about how the code changes: small, frequent version bumps rather than long release trains.

For a user, that rhythm is cheap. You install a release and update when a new one appears. For anyone maintaining a fork, it is the opposite. Every upstream release is a potential rebase against your own changes, and because the project uses fvm with a pinned SDK in .fvmrc, an upstream Flutter version bump can invalidate a fork's build environment independently of any Dart source change. The README documents no backport policy, no long-term support branch and no changelog convention beyond the release tags themselves. If you fork, budget for tracking the pin, not just the code.

Editorial conclusion

Han1mePlus suits adults who want a Material Design 3 Hanime1 client on Android, iOS, macOS or Windows and who accept a single-maintainer project with an as-is disclaimer. It is not for anyone who needs a support contract, a stable API surface, or a client whose behaviour can be audited against a published spec, because the README documents neither. Verify two things first: that a build exists on the Releases page for your exact platform, and that you are willing to meet the AGPL-3.0 obligations if you ever distribute a modified build.

Frequently asked questions

Official sources

1. 1wc10086/Han1mePlus on GitHub
2. Issues
3. License: AGPL-3.0
4. README
5. Releases