A transparent app store built around public releases, inspectable metadata, and automation you can actually follow.
Now fully native.

  

Sources Supported

🔍 Orion does not have any trackers!

Saw a few people asking about the 5 "trackers" flagged in App Manager or TrackerControl, so wanted to clear up what those actually are.

What they actually are:

• App Manager flags manifest activities from libraries, not active surveillance services.
• These are literally just the 5 internal screen renderers bundled inside the Unity Ads SDK:
  • AdUnitActivity: standard video playback screen
  • FullScreenWebViewDisplay: webview player for end cards and interactive screens
  • AdUnitTransparentActivity: transparent overlay screen
  • AdUnitSoftwareActivity and AdUnitTransparentSoftwareActivity: fallback renderers for devices that struggle with hardware acceleration

It is 1 single ad library split across its rendering components, not 5 separate tracking networks.

How it works in Orion:

• It only ever touches memory if you explicitly tap to watch a rewarded video in the "Fuel the Code" quest for XP.
• There are zero background services, no banner ads, and no user data collected or sent anywhere.
• If you do not care about the rewarded XP quest, you can block all 5 of them right there in App Manager. The store will still work completely fine.

Orion Store 2.0 · Native at last

Orion Store has been rebuilt from the ground up as a native Android app. The web app has been rewritten in Kotlin and Jetpack Compose on Material 3 Expressive, with spring motion, shape morphing, a new storefront and features that were never possible before. Updating from 1.x is a normal install over the old app, and your profile, XP, badges, favorites and settings come along.

Read the full 2.0.0 release notes.

Overview

Orion Store is an Android-first store client that leans on public sources instead of hiding everything behind a private service layer. The app pulls catalog data from public JSON, resolves releases from GitHub, GitLab, and Codeberg, and keeps the delivery path understandable enough that users can see where things come from and how updates are discovered.

This repository is the client application itself. The live catalog, configuration, notices, and release metadata used by the app are maintained separately in RookieEnough/Orion-Data, which keeps the UI and the store data cleanly separated.

Orion is built for people who care where software comes from, not just how quickly it downloads.

At a glance:

• Public JSON catalog with inspectable configuration
• Multi-source releases (GitHub, GitLab, Codeberg)
• Native install, update, and security tooling
• Skip Android's 24-hour unverified-app wait with built-in wireless install

What makes Orion different

The point of Orion is not to pretend infrastructure does not exist. It is to reduce hidden infrastructure and move as much of the important behavior as possible into public, inspectable layers. Catalog entries are plain data. Release sources stay visible. Automation is handled through workflows and workers that can be reviewed, rather than through a black-box backend that users have to trust on faith.

That design carries through the app. Orion tracks installed packages, surfaces updates, manages download state, installs natively, and exposes developer-facing diagnostics for people who want to see what the store is actually doing under the hood.

Feature atlas

Release intelligence Orion reads public metadata, resolves upstream releases, and keeps source provenance visible instead of burying it behind a store-owned backend. It reads your device architecture and recommends the right APK. Public JSON Mirrors Multi-source parsing ABI detection	Update center A native download engine with live notifications, a persistent queue, batch updates, and per-app ignore rules you can undo from My Apps. Foreground downloads Queue Ignored updates
Native install flow System installer, a specific installer, Shizuku silent installs, or the built-in wireless ADB installer that skips Android's 24-hour wait for unverified apps. Set it up once through a guided notification. Wireless ADB Shizuku Installer choice	Sentinel security Security tooling is built into the product: malware scans for installed apps and VirusTotal checks for any APK before it is installed. Sentinel VirusTotal Threat database
Guardian power tools Revoke risky permissions, pull the APK out of any app, and remove or restore system apps without root, rated by the Universal Android Debloater database. Permissions APK extraction Debloater	Developer visibility Mirror source, cache state, GitHub API quota, package detective, raw metadata explorer and source switching, all in Settings › Developer. Developer mode Diagnostics Metadata inspection
Orion AI Describe the app you need and Orion AI finds it in the catalog, or ask how any Orion feature works. Bring your own Gemini, ChatGPT or Claude key, or run a model right on the phone, offline. Streaming chat On-device models One-tap installs	Palettes, your way Fourteen tuned palettes plus a palette maker: pick a seed color, a style and preview every tone in Light, Dusk, Dark and OLED before you save it. Material You Palette maker Four themes

And a lot more

• Material 3 Expressive design: expressive springs, shape morphs, wavy progress, icon hand-off animations, and Material You colors.
• A real level system: every ad, download, submission and Dino Run earns XP. Pilot cards turn Bronze, Silver and Gold, and you can flip yours to sign it.
• Fuel the Code: a story-driven support quest, now in Chapter 2 · The Forkening, with bosses and badges to earn.
• Community: submit apps straight from a GitHub, GitLab or Codeberg repo, build custom bundles, and climb the leaderboard.
• Personalization: light, dark, dusk and OLED themes, custom fonts, pixel pull-to-refresh characters, layouts and visible tabs.

Screenshots

Storefront	App details	My Apps	Orion Xtra
Pilot profile	Badge archive	Fuel the Code	About
Settings	Welcome to 2.0	Dark theme	PC catalog

Official developer badges

If you are a developer, you can promote that your application is hosted on Orion Store by adding our official badge to your repository's readme or your product website.

How to Get Your Badge Integration Link:

1. Submit Your App: Submit your application to the Orion Store via this client or our repository submission form.
2. Enable Developer Mode: Once approved and live in the store, open Orion Store and tap the Orion Store title in the header 7 times to unlock Developer Mode.
3. Copy Integration Code: Open your app's detail page, expand Developer Deep Links, and copy the Markdown Badge for your repository's README or the HTML Badge for your website.

How the project is structured

Orion Store 2.0 is a single-activity Jetpack Compose app in MVVM style. A tour of the code lives in ARCHITECTURE.md.

Area	Responsibility
app/src/main/java/com/orion/store/ui/	Compose screens, the theme and motion system, and MainViewModel, which orchestrates loading, downloads, installs and overlays
app/src/main/java/com/orion/store/data/	Catalog processing, persisted settings and data stores, version logic, XP and levels
app/src/main/java/com/orion/store/platform/	Package tracking, the download service, Shizuku and wireless ADB installs, VirusTotal, and the 1.x data carry-over
tools/	Generators for the Material Symbols icon set and the color schemes
Orion Legacy/	The original React + Capacitor web app (1.x), kept for reference and for the web build

Building

You need JDK 21 (the JetBrains Runtime bundled with Android Studio works) and the Android SDK.

./gradlew :app:assembleDebug          # debug APK
./gradlew :app:testDebugUnitTest      # logic tests

Release builds read the signing key from a local keystore.properties (never committed):

storeFile=/path/to/your.keystore
keyAlias=your-alias
storePassword=...
keyPassword=...

./gradlew :app:assembleRelease

Or open the project folder in Android Studio and run the app configuration on a device.

Legacy web app

The 1.x web app lives in Orion Legacy/ and still builds as before:

cd "Orion Legacy"
npm install
npm run dev

Data, workers and automation

Orion is best understood as backend-light rather than backend-free. The catalog and remote configuration are public, but the project still uses a few narrow pieces of infrastructure where they make sense: Cloudflare worker code for leaderboard relay, image proxying, delta aggregation, submission handling and Sentinel support lives in Orion Legacy/workers/, and automation runs through GitHub Actions here and in Orion-Data.

That split is intentional. The app stays focused on the client, while the data and automation layers remain separately inspectable.

Contributing

Contributions are welcome, especially in the areas that matter most to a store client: installer reliability, release resolution, UI polish, Android behavior, security tooling, and documentation. If you are changing catalog entries or store metadata, that work usually belongs in the data repository or the submission flow rather than in this client codebase.

Start with ARCHITECTURE.md, then ui/MainViewModel.kt, data/CatalogProcessor.kt and platform/AppTracker.kt for how the store loads data, resolves releases and installs apps.

Community

The project lives across a few public surfaces:

• Website: orionstore.pages.dev
• Orion-Data: github.com/RookieEnough/Orion-Data
• Discord: discord.com/invite/CrM6y4ujnq
• Ko-fi: ko-fi.com/rookie_z
• PayPal: paypal.me/RookieEnough
• UPI ID: rookiez@ptyes

Made with 💜 by RookieZ