trinea/android-common

Android common lib, include ImageCache, HttpCache, DropDownListView, DownloadManager, Utils and so on

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 12 minutes ago
Type:Library / SDKCategory(s):AndroidMobile & Desktop
Added to GitGenius on September 13th, 2026
Created on June 19th, 2012
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 2,586
Total Stargazers: 4,997 (+0)
Total Subscribers: 484 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Trinea Android Common is a collection of reusable Android libraries that provides cache components, UI widgets, and utility helpers for building stable mobile applications.

The project addresses the friction of building Android apps from scratch by bundling solutions for problems that recur across projects. It supplies in-memory and disk-based image caches with configurable eviction policies, HTTP response caching, pull-to-refresh and infinite-scroll list views, download management, and a broad set of utility functions for working with files, JSON, strings, collections, packages, and system resources. Developers integrate the library as a module dependency and then call its APIs directly in their application code.

The tool suits teams building consumer Android applications who want to avoid reimplementing pagination, caching, and download logic. It is particularly useful for projects that need stable, battle-tested implementations of common patterns rather than cutting-edge features. The README does not position the project against named alternatives, so no comparative guidance can be offered.

The codebase has experienced quiet periods but remains actively used in production applications across the community. The maintainers have signaled intent to modernize the toolkit through AndroidX migration, expanded test coverage, and improved documentation, though this work has not yet materialized at scale.