Hermes 284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Initial import of AlgaPSA codebase from PSA server
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz

Source: /opt/alga-psa on psa.joliet.tech
2026-06-22 16:12:17 -05:00

46 lines
1.4 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Store Screenshots Capture Plan
Date: `2026-02-03`
Scope: Ticketing MVP (no Phase 2 notifications)
## Goals
- Capture consistent, readable screenshots for App Store and Play Store listings.
- Avoid PII: use a seeded/demo tenant with fake company/contact data.
## Devices / sizes
### iOS (App Store)
- iPhone 6.7" (Pro Max size)
- iPhone 6.1" (standard)
### Android (Play Store)
- Phone 1080×1920 (or equivalent)
## Screens to capture (suggested order)
1) Sign In (SSO via system browser) — emphasize secure sign-in
2) Tickets list (with filters/chips visible)
3) Ticket detail (header + key fields)
4) Comments (internal/public badges visible)
5) Status change (picker / confirmation)
6) Settings (diagnostics + account section)
## Content guidelines
- Use non-sensitive demo data:
- Ticket titles: generic (“Printer not printing”, “VPN issue”, “Password reset”)
- Company/contact: placeholders (“Acme Co.”, “Alex Example”)
- Ensure all badges and key text are legible.
- Keep brightness consistent; avoid OS banners in captures.
## Capture workflow (manual)
1) Create a demo user + seed demo tickets in a non-production tenant.
2) Install a build via TestFlight (iOS) / Internal Testing (Android).
3) Navigate to each screen above and capture.
4) Store raw captures in a private release artifact location (do not commit screenshots to this repo).