Android app · Utility

StoreClear

Storage cleaning utility for clearing clutter and keeping Android space manageable.

Get it on Google Play ↗ Source on GitHub ↗

StoreClear is a privacy-first Android storage manager for finding hidden space, removing duplicate files, visualizing large directories, and securely shredding sensitive files. It runs storage analysis locally on the device and is designed for users who want practical cleanup tools without accounts, analytics, or file uploads.

The repository does not currently include CI, coverage publishing, or a LICENSE file. Update the badges after those are configured.

Project Overview

StoreClear helps Android users understand where storage space went and remove clutter safely. It combines a storage dashboard, duplicate detection, a treemap-style heatmap, empty-folder cleanup, cache review, and configurable multi-pass file shredding. The Play Store listing copy describes the app as "Find hidden space. Leave no trace."

There is no hosted demo for the Android app in this repository.

Key Features

• 📊 Storage dashboard shows total, used, and category-level storage summaries.
• 🔍 Duplicate finder buckets files by size, hashes candidates, and preselects removable copies.
• 🗺️ Directory heatmap visualizes large folders with drill-down navigation.
• 🧹 Empty-folder cleaner finds leftover directories and deletes selected items.
• 🧼 Cache cleaner reviews app/cache remnants from granted storage and usage access.
• 🛡️ Secure shredder overwrites selected files with configurable pass counts before deletion.
• ⚙️ Settings control hash algorithm, shred intensity, scan depth, system-folder exclusions, and theme.
• 🏪 Roborazzi tests generate Play Store screenshots, app icon, and feature graphic assets.

Architecture Overview

Components

presentation contains Compose screens, reusable dashboard/heatmap components, and StoreClearViewModel state flows. domain defines storage models, repository contracts, and use cases such as duplicate scanning, heatmap building, and secure shredding. data implements repositories using local data sources, Android storage APIs, and Room persistence. util handles storage-root normalization and Android permission helpers.

Data Flow

The app requests storage access, stores the chosen root locally, then uses domain use cases from the view model. Duplicate scans walk the file tree, bucket files by size, compute MD5 or SHA-256 hashes, cache hash results in Room, and return grouped duplicates to the UI. Shred jobs stream progress from the overwrite data source and persist completion history.

Design Patterns

The code follows a lightweight clean-architecture structure with Compose state hoisted through StateFlow, repository interfaces in the domain layer, concrete data-source implementations in the data layer, and dependency wiring in AppContainer.

Tech Stack & Libraries

Configuration

Configuration lives in app/build.gradle.kts, .env, .env.example, and optional signing files such as key.properties.

Runtime settings are controlled inside the app and persisted locally:

Usage / Quick Start

Build and Run

./gradlew assembleDebug
./gradlew installDebug

Open StoreClear on the device, grant media/storage access, then enable All files access if Android prompts for it.

Run Tests

./gradlew testDebugUnitTest

Generate Play Store Assets

./gradlew generatePlayStoreAssets

feature graphic.

API Reference

Not applicable. StoreClear is a local Android application and the inspected code does not expose an HTTP API, public SDK, CLI, or service endpoint.

The app does contain domain-level Kotlin interfaces that act as internal contracts:

Testing

| Manifest policy test | ./gradlew testDebugUnitTest --tests '*ManifestPolicyTest' | app/src/test/java/com/michael/storeclear/playstore/ManifestPolicyTest.kt |

Test class names currently use descriptive JUnit names such as ManifestPolicyTest, PlayStoreScreenshotTest, and PlayStoreFeatureGraphicTest. Coverage reporting is not configured in the inspected Gradle files.

Deployment

Debug builds are produced with:

./gradlew assembleDebug

Release app bundles are produced with:

./gradlew bundleRelease

Release signing reads environment variables first, then key.properties, then the default my-upload-key.jks path. Keep real keystore files and passwords out of commits.

There is no Docker or docker-compose setup for the Android app.