White screens hurt your eyes and your battery. Tiny sounds do the opposite.
A pure white screen is one of the most expensive and least friendly things you can show a user.
A short, well-designed sound is one of the cheapest — and one of the most human.
Why white screens are a problem
For the eyes
- High luminance causes more strain, especially in low-light environments.
- On OLED devices the entire panel is driven at maximum brightness for every pixel.
- Prolonged exposure contributes to visual fatigue and reduced comfort.
For energy
- OLED: every white pixel is fully lit → significantly higher power draw.
- LCD: the backlight stays at full intensity.
- The cost is continuous for as long as the white content remains on screen.
White screen vs. Sound effect
| Aspect | White screen | Short Web Audio click (as used at Iana.IO) |
|---|---|---|
| Power draw | Continuous (high on OLED) | Extremely brief (~0.1–0.17 s) |
| Typical battery impact | Noticeable | Essentially zero for normal UI use |
| Hardware involved | Full display | Tiny CPU + oscillator only |
| Network / decoding | None | None |
| Ongoing cost | High while visible | Near-zero (created on gesture, then discarded) |
| Effect on user | Strain + fatigue | Confirmation + “alive” feeling |
Why the difference is so large
On modern OLED phones a pure white screen keeps every pixel fully lit. Even on LCDs the backlight runs at full brightness.
The click system we use is a pure Web Audio oscillator. It runs for a fraction of a second, performs microseconds of work, and is immediately garbage-collected. There is no permanent AudioContext, no file download, and no decoding. Real-world measurements show the battery impact of occasional UI clicks is effectively zero.
Bottom line
Keeping a white screen visible for any meaningful time costs orders of magnitude more energy than playing these short, sparse sounds. The audio approach is already one of the cheapest interactive feedback mechanisms available.
Why sound makes interfaces feel better
Sound is one of the fastest channels humans have for recognising that something happened.
A tiny click:
- Gives instant confirmation (even before the visual response appears)
- Makes the interface feel responsive and alive
- Creates a subtle emotional hierarchy (different tones for different actions)
- Helps users who are not looking directly at the screen
- Signals care and quality when used with restraint
People notice sound. When it is short, quiet, and purposeful, it makes digital products feel more human.
How we do it at Iana.IO
We use three lightweight oscillator variants (no audio files):
- default – classic mid-tone (Customers, Logout)
- start – softer, lower “launch” feel (Get Started)
- menu – short, high, crisp click (mobile hamburger)
Each lasts 0.09–0.17 seconds and is created only on a real user gesture.
Looking ahead — Energy Technology
Energy efficiency is becoming a first-class product requirement.
In the coming months we will expand this thinking into a full Energy Technology section in the Iana.IO Playbook, covering:
- Display power (dark mode, OLED considerations, avoiding large white areas)
- Micro-interactions that feel rich but cost almost nothing
- Network and computation costs
- Measuring real-world battery impact
Tiny, intentional details — like a well-tuned click instead of a bright white flash — are often the highest-leverage places to start.
Energy-safe by design. Easier on the eyes. Better for the battery.