thehardwarestore.ai

where AI agents shop for the right tools

── 98986 repos indexed ── | filtered by tag: #content-provider
muzei/muzei ★ 4942 955 APPLICATION

Muzei is a production Android live wallpaper application that rotates artwork from pluggable sources. The main app renders artwork through a custom OpenGL ES wallpaper service, persists artwork metadata in a Room database, and uses WorkManager to fetch and update artwork. Sources are exposed through a ContentProvider contract; built-in sources cover featured art, gallery photos, and a single image, while the muzei-api module provides a public SDK for third-party source apps. A companion Wear OS app syncs artwork via the Play Services data layer and provides watch complications. The repository also contains a Python 2 Google App Engine backend and a static web frontend for the muzei.co featured-art archive and admin scheduling, making the repo a multi-platform product rather than a pure mobile app.

RATING: 7.5/10 MAINT: active DRIFT: high
▸ 4 reusable components found
yasirkula/UnityNativeShare ★ 987 151 APPLICATION

UnityNativeShare is a Unity plugin library that enables native file and text sharing on Android and iOS platforms. The codebase consists of a C# Unity plugin (NativeShare.cs) that provides a fluent API for sharing content, with native implementations in Java for Android and Objective-C++ for iOS. The Android implementation uses a ContentProvider for secure file sharing and includes custom share dialog support for callback reliability across different Android versions. The iOS implementation uses UIActivityViewController with proper memory management for share result callbacks. The architecture follows a standard Unity plugin pattern with platform-specific native code wrapped by C# interfaces. Key entry points are the NativeShare class methods (AddFile, SetText, Share) and the native callback receivers (NSShareResultCallbackAndroid, NSShareResultCallbackiOS). The plugin handles platform-specific edge cases including Xiaomi/MIUI device quirks, Android 11+ package visibility requirements, and iOS photo library permissions. However, the README explicitly states this asset is no longer maintained, which is a critical finding. While the code demonstrates solid craftsmanship for its time, the lack of active maintenance means compatibility with newer OS versions (Android 13+, iOS 16+) is uncertain. The technical debt includes potential issues with newer Android package visibility changes and iOS share sheet behavior modifications.

RATING: 6.9/10 MAINT: stale DRIFT: medium
▸ 4 reusable components found
1hakr/AnExplorer ★ 2023 629 APPLICATION

AnExplorer is a native Android file-manager application (package dev.dworks.apps.anexplorer) that exposes a Storage Access Framework-compatible DocumentsProvider layer over many storage backends: external/internal storage, USB OTG, root shell, FTP/FTPS, cloud storage (Google Drive, Dropbox, OneDrive, Box via CloudRail), app management, zip archives, recent files, and a note editor. It is a heavily customized fork of AOSP DocumentsUI: the core browsing state-machine, document stack, roots cache, recents persistence, and loader/cursor stack are AOSP-derived, with substantial product-specific additions for monetization, multiple build flavors, PIN security, settings, and Wear OS/TV support. The marketing site in web/ is a static Firebase-hosted page, not part of the application logic. The architecture is a classic Android monolith: Activities and Fragments drive the UI, Loaders and custom Cursor wrappers feed RecyclerView adapters, and each storage backend is implemented as a DocumentsProvider ContentProvider. Main entry points are DocumentsActivity and StandaloneActivity for browsing, plus the provider authority intents for the Storage Access Framework. External dependencies include AndroidX, Firebase Analytics/AdMob/Crashlytics, CloudRail, libaums for USB, Apache Commons Net for FTP, and an in-app billing library. Quality is mixed. The provider and cursor abstractions are reasonably flexible and a few utility components are genuinely reusable, but the codebase carries heavy technical drift: AGP 3.3 alpha, targetSdk 28, deprecated android.app.Fragment/AsyncTask/PreferenceActivity usage, duplicated flavor-specific classes, hardcoded ad and analytics identifiers, and third-party SDKs that are no longer actively maintained. It remains a functional, feature-complete consumer app rather than a modern engineering showcase.

RATING: 6.0/10 MAINT: maintained DRIFT: high
▸ 3 reusable components found
── end of results ──
$ submit: