TreeMap
무료 오픈소스 디스크 사용량 시각화 도구로, 사각형 트리맵·중복 파일 탐색·디스크 가득 예측·정리 시 파일을 휴지통으로만 이동한다
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기A fast, native Nextcloud client built with Flutter
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A fast, native Nextcloud client built with Flutter
and Material 3.
Noo is a clean, modern way to browse and manage the files on your own
Nextcloud server: files, photos, shares, activity, and trash in one app,
themed to match your device and laid out for both phones and tablets.
Noo is an independent, unofficial client. It is not affiliated with or
endorsed by Nextcloud GmbH.
Self-hosting gives you control over your files. Noo makes that cloud easy to
use day to day, whether you're opening a file, sharing a folder, or taking
your photos offline.README 전문 보기 ↗A fast, native Nextcloud client built with Flutter and Material 3.
Noo is a clean, modern way to browse and manage the files on your own Nextcloud server: files, photos, shares, activity, and trash in one app, themed to match your device and laid out for both phones and tablets.
Website: https://noo.ayushya.dev
Noo is an independent, unofficial client. It is not affiliated with or endorsed by Nextcloud GmbH.
Self-hosting gives you control over your files. Noo makes that cloud easy to use day to day, whether you're opening a file, sharing a folder, or taking your photos offline.
Prerequisites:
^3.12.2)flutter pub get
flutter run
On first launch, enter your server's address. Noo opens your browser to finish signing in.
flutter build apk # Android (debug-signed unless you configure a key)
flutter build ios # iOS
Release builds read signing details from android/key.properties or from
RELEASE_KEYSTORE_* environment variables (see android/app/build.gradle.kts).
Neither the keystore nor key.properties is, or should ever be, committed.
Without them, release builds fall back to debug signing.
Flutter with Material 3, provider for
state management, and http/dio talking directly to Nextcloud's WebDAV and
OCS APIs, with no bundled Nextcloud SDK. Android has native workers for
transfers and background sync.
Contributions are welcome. Please read CONTRIBUTING.md
first. In short:
flutter test # run tests
flutter analyze # static analysis / lints
Architecture, server integration, styling conventions, and code standards are
documented in CLAUDE.md and .claude/context/, written for
both human and AI contributors.
Noo talks only to the Nextcloud server you point it at. It has no analytics and no third-party tracking. Read the full privacy policy.
Typefaces Instrument Sans and Schibsted Grotesk are bundled under the SIL Open Font License, and icons are from Lucide. Those keep their own licenses; the license below covers Noo's own code and assets.
Noo is source-available under the PolyForm Shield License 1.0.0. In plain terms: you may read, build, run, and modify the code, and contribute changes back, but you may not use it to make a product or service that competes with Noo. Please do not republish it as your own app.
Contributions are welcome under the terms in
CONTRIBUTING.md.
I want the code to be open to read, learn from, build, and improve, while keeping anyone from lifting it and shipping a competing copy of the app. Permissive licenses (MIT, Apache) allow exactly that, and copyleft ones (GPL) still allow a rebranded fork. PolyForm Shield sits in between: it is not an OSI "open source" license, and I'm not claiming it is, but it keeps the code available while protecting the project.
The source of truth is a self-hosted Gitea instance, and this GitHub
repository is a read-only mirror plus the public issue tracker. I keep it
that way so that I own my hosting, builds, and release credentials rather
than depending on a third party for them. You don't have to use Gitea:
open issues and pull requests here as usual. Open PRs are imported to my
instance, reviewed and merged there, and main is mirrored back here, so a
merged PR may show as closed with a link to the commit instead of "Merged".
See CONTRIBUTING.md for details.