Native · Fast · GitHub-native · Verification-first
Manage GitHub from your phone: browse repositories, review issues and pull requests, monitor Actions runs, build APKs, and download files with SHA-256 verification. Open source, built with Kotlin and Jetpack Compose.
Unofficial app. Not affiliated with or endorsed by GitHub, Inc.
Releases · Issues · CI · Apache-2.0
GitHub Rock's README is the project-facing documentation entry point. It explains what the app is, how it is built, which GitHub workflows it supports, and how problems are handled during development.
The app is intended to solve real GitHub workflow problems inside a native Android experience — not hide them behind mock data or simulated success.
When a problem is found, the project follows:
Identify → Reproduce → Audit → Find the root cause → Fix → Build/Test → Verify → Commit → CI → Document
This applies to UI/UX bugs, authentication, GitHub API integration, README rendering, search, Actions/builds, downloads, releases, networking, permissions, accessibility and other supported features.
If a problem cannot be solved because of GitHub permissions, API limits, network conditions, platform restrictions or missing backend support, GitHub Rock should show a clear actionable state instead of pretending the operation succeeded.
GitHub Rock brings core GitHub workflows into a native Jetpack Compose experience instead of wrapping the GitHub website.
The product is built around three rules:
Native UI. Real GitHub data. Honest product status.
If a capability is unavailable because of permissions, API limits, platform restrictions, or missing backend support, the app should expose that state rather than simulate success.
| Surface | GitHub Rock |
|---|---|
| Home | Account overview, activity, recent repositories, issues, PRs, builds, downloads and releases |
| Repositories | Search, browse, files, README, translation, branches, releases, issues, PRs, commits and Actions |
| Issues | States, labels, assignees, comments, metadata and supported actions |
| Pull requests | Diffs, changed files, reviews, comments, reactions and supported actions |
| Actions / Builds | Workflows, runs, jobs, steps, logs, artifacts, dispatch, cancellation and reruns |
| Releases | Releases, assets, platform classification and supported downloads |
| Search | Repository, content and supported issue / pull-request search |
| Profile | Connected GitHub account, repositories, organizations and supported profile data |
Home · Repositories · Builds · Downloads · Profile
The primary navigation stays focused on GitHub work. Explore and Settings are not promoted to primary bottom-navigation destinations.
GitHub Rock follows a Liquid GitHub Luxury direction:
- Dark-first charcoal surfaces
- Native Material 3 foundations
- Rounded, structured surfaces
- Subtle glass/transparency treatment where useful
- Clear typography and information hierarchy
- Responsive phone, tablet and landscape layouts
- Light, dark and true-black appearance modes
- Reduced-motion aware transitions
- Accessible controls and readable contrast
- No visual effect used as a substitute for functionality
The visual system can evolve independently from the product contract.
Repository README content can be translated directly inside the native README viewer:
- Language picker with the supported Google ML Kit on-device translation languages
- Automatic source-language detection, including README-context fallback for short headings and labels
- Translated headings, paragraphs, bullets, tasks, quotes and supported alerts
- Code blocks, images and tables remain unchanged
- The original README is never replaced by translated content
- Model download, loading, error and retry states are surfaced honestly
- Switching back to Original restores the source README immediately
Translation is performed with the existing Google ML Kit integration; GitHub Rock does not use hard-coded or simulated translations.
Motion is treated as part of the navigation model rather than a collection of unrelated screen animations.
Micro → Quick → Standard → Smooth
Interactions are designed around continuity:
- Repository cards can transition into repository details
- Navigation selection can travel with the destination
- Search can expand from its toolbar context
- Build state can carry into build details
- Download progress can resolve into completion
- Account switching can preserve visual continuity
Animations should remain useful, short and predictable.
- Kotlin
- Jetpack Compose
- Material 3
- Retrofit
- Room
- DataStore
- WorkManager
- Android Keystore
- GitHub REST APIs
- GitHub GraphQL APIs where supported
- GitHub Actions
The Android app reuses its authenticated networking/data layers. Feature work must not create duplicate Retrofit/API clients or parallel implementations of an existing capability.
GitHub Rock uses a verification-first approach to sensitive operations.
- Android Keystore-backed authentication storage
- Explicit authentication and permission states
- Redacted network logging
- SHA-256 verification where supported
- Rate-limit and network failure states
- Offline and recovery states
- No fake success for unavailable operations
- No OAuth client secret in the Android application
- No tokens, signing keys, keystores, passwords or
local.propertiesin source control
See SECURITY.md and BUILD.md for project-specific guidance.
| Requirement | Version |
|---|---|
| Minimum Android | 10 / API 29 |
| Current project range | API 29–36 |
| Primary platform | Android |
| Build JDK | 17 |
| Android SDK | 36 |
The repository also contains companion/web and desktop-oriented components. Their capabilities are kept separate from the native Android product surface.
GitHub Rock follows a simple rule:
Only real, compatible, verifiable artifacts are documented as installable.
Supported download flows can include GitHub release assets and GitHub Actions artifacts where the current build supports them.
The companion distribution repositories are maintained for future verified artifacts:
No guessed version, URL, checksum or platform artifact is treated as a release.
- Android Studio
- JDK 17
- Android SDK 36
- Git
git clone https://github.com/Sayanthrock-Developer/GitHub-Rock.git
cd GitHub-Rock
cp local.properties.example local.propertiesConfigure the local SDK path and follow BUILD.md for authentication and release configuration.
./gradlew --version
./gradlew lint
./gradlew testDebugUnitTest
./gradlew assembleDebug
./gradlew assembleRelease
./gradlew assembleDebugAndroidTestDebug artifacts are produced under:
app/build/outputs/apk/debug/
| Document | Purpose |
|---|---|
BUILD.md |
Build, configuration, signing and release |
ARCHITECTURE.md |
Technical architecture |
IMPLEMENTATION_STATUS.md |
Authoritative implementation state |
PRIVACY.md |
Privacy information |
SECURITY.md |
Security reporting |
SUPPORT.md |
Support |
TERMS.md |
Terms |
GitHub Rock uses:
Audit → Root Cause → Fix → Build/Test → Verify → Commit → CI → Next issue
A screen, button, route, API method, mockup or roadmap entry is not proof that a capability works.
Every substantial change should preserve:
- Real GitHub integration
- Correct authentication and permissions
- Loading, success, empty, error and recovery states
- Accessibility
- Security
- Existing working functionality
- Appropriate tests
- CI verification
Detailed implementation state belongs in IMPLEMENTATION_STATUS.md.
GitHub Rock is actively developed.
This README is the project documentation and product-facing overview. It intentionally avoids presenting every planned or platform-dependent capability as universally available.
For the implementation truth, use:
Useful project links: