Product vision¶
Moto X Dashboard is an intentionally small household appliance rather than a general-purpose revived smartphone.
Primary modes¶
- Night clock: quiet, very dark, glanceable, and always available.
- Information display: brief calendar, weather, sports, news, or family photo updates selected by the server.
- Music player: large local-library controls for a paired Bluetooth shower speaker, with optional Internet-radio presets later.
Clock themes¶
Clock presentation is themeable without changing timekeeping, scheduling, burn-in protection, or accessibility behavior. Local day/night scheduling and manual theme overrides are implemented. Server-managed theme settings remain future work.
Nixie night theme¶
The overnight default should evoke a handmade Nixie-tube clock:
- warm amber/orange illuminated numerals;
- near-black surroundings with restrained red and copper undertones;
- individual tube-like digit chambers rather than a flat generic digital font;
- subtle glass, wire, metal, and imperfect glow cues;
- high legibility at low brightness;
- no cool-white panels or conventional light-mode surfaces.
The reference images supplied during project setup communicate mood and material treatment, not assets to copy. Final artwork must be original or properly licensed.
Split-flap day theme¶
A daytime or manually selected alternative should evoke mid-century split-flap clocks and airport departure boards:
- matte black mechanical cards with clean white numerals;
- a visible horizontal split through each digit;
- restrained hinge, axle, housing, and card-depth details;
- optional short flip transitions when a digit changes;
- high contrast and a quieter, more utilitarian character than the Nixie theme.
Motion must remain lightweight on the old device and must not queue missed animations. Accessibility and a reduced/no-animation option take precedence over mechanical simulation.
The display must also protect the Moto X AMOLED panel. Digit chambers and other persistent elements should shift position subtly, brightness must remain low, and long-lived layouts should alternate without creating distracting motion.
Deliberate exclusions¶
- no WebView-based application shell;
- no third-party OAuth secrets on the device;
- no attempt to recreate a full modern smartphone environment;
- no administration website until device and API fundamentals are working.