Daily overview
Material balance changes, freshness, depegs, failed imports, concentration moves, and unresolved alerts.
AltcoinTrack mobile
A mobile tracker should make risk visible at a glance.
A design framework for iOS and Android altcoin tracking that prioritizes read-only access, privacy, clear alerts, offline resilience, accessibility, and separation from transaction signing.
Product blueprint
No app-store claim
The delivered static website does not include an iOS or Android application. This page defines the information architecture and security expectations for a future read-only mobile experience.
Mobile information architecture
Prioritize the next decision, not every metric
Portfolio
Owned accounts, holdings, protocol positions, liabilities, liquidity states, and look-through exposure.
Scanner
Saved universes, reproducible signals, liquidity filters, quality warnings, and alert evidence.
Research log
Asset notes, assumptions, source dates, thesis changes, event timelines, and next review.
Read-only by default
Monitoring should not require signing secrets
A mobile tracking app can use public addresses, limited account records, or other read-only sources. Seed phrases and private keys should never be requested. If a transaction handoff is designed later, the wallet should perform authorization in its own trusted interface.
Privacy settings should explain what address sets, account labels, device identifiers, analytics, and network information are shared. Users need a way to remove a source and understand whether cached data remains.
Mobile security checklist
- Biometric or device authentication for local access
- Encrypted local cache and protected backup policy
- Read-only connection scope shown before approval
- No seed phrase, private key, or recovery-word entry
- Session and device revocation
- Privacy mode for balances and notifications
Alert anatomy
- What changed and by how much
- Which asset, account, venue, or protocol is affected
- Observed event and publication time
- Source and freshness
- Liquidity or operational context
- Reason the alert was triggered
- Review link and acknowledgement state
Notifications with evidence
A push message should invite review, not panic
Price change alone creates noisy alerts. Combine movement with portfolio weight, liquidity, data quality, depeg duration, withdrawal status, or another material condition. Let users choose quiet hours and escalation tiers, and keep every notification in a history with evidence.
For scanners, show the signal definition and quality flags. For portfolios, identify whether a change came from price, quantity, an import correction, or a newly discovered account.
Resilient mobile design
Readable, accessible, and useful with imperfect connectivity
Accessible color
Do not rely on green and red alone. Use text labels, shapes, and contrast for gains, losses, severity, and freshness.
Offline clarity
Show when data last synchronized and which views are cached. Never present an offline balance as current without a timestamp.
Reduced motion
Respect system motion settings, support large text and screen readers, and keep controls reachable without precision gestures.
Keep custody separate from visibility.
The hardware-wallet guide explains watch-only monitoring, address discovery, privacy, labels, reconciliation, and transaction-verification boundaries.