Crystal Aether Network
Android boot animation creation, support, and creator commerce in one network.
CRYA brings Livingstone Toolkit, Boot Store discovery, creator profiles, reviewed AI help, docs, and community support into one polished home for Android modders.
Public Mission Control
Know what CRYA is, what is live, and where to go next
The homepage should feel like a product command center for users: enough context to trust the ecosystem, without exposing protected admin controls.
Start with the Toolkit when you want to create, inspect, repair, or export a boot animation.
Use the Store and Creator Hub when you want approved packs, creator credit, collections, badges, or showcase paths.
Use Docs, Status, Support, and Community when you need help, evidence, service context, or human review.
Protected admin, server, billing, moderation, AI budget, and release controls stay behind the admin boundary.
| Product | Livingstone Toolkit, Package Doctor, clean export, QMG-aware guidance, and utility pages. |
|---|---|
| Marketplace | Boot Store discovery with preview assets, access labels, creator attribution, and review language. |
| Creator layer | Profiles, badges, rankings, competitions, submission standards, and future monetization paths. |
| Operations | Public status, docs, support evidence, legal routes, maintenance mode, and portable recovery notes. |
Start here
Choose the path that matches your job
The public site speaks to users first. Admin machinery stays behind Mission Control.
Build a boot animation from artwork, ZIP sources, or prepared frames, then preview the loop before export.
Use Package Doctor language to understand broken folders, desc.txt errors, frame counts, and risky assumptions.
Browse curated packs with preview assets, creator credit, device notes, and app handoff expectations.
Prepare creator profiles, pack evidence, screenshots, compatibility notes, and review-ready metadata.
Ecosystem map
One public product, several focused surfaces
Each CRYA surface has a real user purpose and a controlled admin boundary.
The flagship Android tool for boot animation creation, preview, package diagnostics, clean exports, and safe guidance.
A catalog for approved packs, collections, creator attribution, compatibility notes, and future paid-pack discovery.
Reviewed AI support that explains errors, helps creators write better metadata, and avoids policy guessing.
Profiles, trust levels, badges, showcase pages, submission requirements, and creator-focused growth paths.
Help-center style guides organized by user task instead of internal implementation names.
Protected admin app for maintenance, permissions, releases, store review, AI controls, and server bridges.
Portable by design
Built for launch, migration, and future SaaS growth
CRYA should not be a one-off website. The public product, private admin tools, setup wizard, backups, and export packages are designed to move together when the server changes.
A repeatable bootstrap path can collect domains, SSL, mail identity, Firebase public config, first admin, cache, and backup checks.
CRYA Control stays portable between VPS moves while secrets, passwords, panel credentials, and billing keys stay out of exports.
Backups, static discovery files, mail identity, sitemap evidence, and launch checks are tracked before risky updates.
The same architecture can grow into teams, creator workspaces, usage limits, API keys, licensing, and partner tools.
Marketplace feel
Browse by outcome, style, and trust
Inspired by mature marketplace/category layouts, but hosted and branded through CRYA.
Hand-picked packs with clear previews, attribution, quality notes, and app handoff language.
OpenCyber HUDFuturistic AMOLED packsNeon, dashboard, scanline, command-center, and Samsung-friendly visual styles.
OpenDevice NotesCompatibility-first browsingBrowse by model family, size, frame behavior, boot/shutdown path, and known limitations.
OpenCreator DropsNew creator showcasesProfile-led drops with trusted links, pack history, badges, and review evidence.
OpenDocs PicksGuides people actually needInstall, diagnose, export, billing, submission, and recovery help without admin noise.
OpenUser journey
From idea to trusted pack
The flow is written for real users and creators, not system administrators.
Start from artwork, frames, or an existing package.
Check timing, size, loop behavior, and visual fit.
Fix structure and metadata before risky install steps.
Prepare creator evidence and store submission details.
Use docs, status, bot, and package reports when stuck.