Feature shape
Live Notifications
Live Notifications should make CRYA feel responsive while respecting user consent, Android notification rules, quiet hours, and admin-controlled messaging.
Export, package repair, demo import, and store upload states can stay visible without trapping the user.
Private support replies, store review changes, and account actions should be routed safely.
Maintenance, app releases, status changes, and community announcements need admin-controlled wording.
Opt-in channels, cooldowns, quiet behavior, and notification categories protect trust.
| Best use | Task progress, support replies, store state changes, maintenance, release notes, and important account notices. |
|---|---|
| Play-safe language | Notifications should be opt-in, relevant, easy to control, and not misleading. |
| Private data | Avoid sensitive account, billing, or moderation details in public lock-screen text. |
| Admin control | Announcements, maintenance notices, and push channels belong in Mission Control. |
| Support evidence | Failed or missing notifications should include app version, device/build, channel settings, and time. |
User workflow
How this utility should feel in the app
A CRYA utility should be useful, explicit about risk, and connected to support evidence when something fails.
Choose relevant CRYA notification categories.
Export, upload, review, support, or release workflow begins.
Notification reflects progress or next action.
Cooldowns and categories prevent spam.
Tap through to app, support, store, or status context.
Related CRYA surfaces
Continue safely
Utility pages connect users to Toolkit workflows, docs, policies, and support without exposing protected admin controls.