info.arnao.ai: clean start, with one Customize button
_Proposal only. Nothing is built yet. v2, 2026-10-11, revised from your feedback on v1._
The idea
When the page opens, your voice intro plays and the screen shows only the card, a 🔍 search button, and a small ⚙ Customize pill on the right. Everything else lives inside Customize. Gestures, mic, cameras and shake start off, and nobody gets a permission pop-up until they turn one on.
Mockup (live site)
| 1 · Opens | 2 · Tap ⚙ Customize |
 |  |
| Card, search, and Customize. No filters, launch pill, side rail, mic, version stamp or sensor icons. | Browse: Apps / Content and Latest / 24h / 7d / 30d / All. View: Display, Grid, Full screen, Help. Experimental: four switches, all off. |
Full size: 1 · opens · 2 · customize · today's first screen
Your voice at start: one honest limit
Phones and Chrome block sound until a visitor has touched the page. So the plan is:
- Try to play on load. Chrome lets sound start automatically for sites a person has visited and listened to before, so returning visitors on Chrome often hear it straight away.
- If the browser blocks it, play on the visitor's very first touch of any kind: a swipe through the cards, a tap, anything. There's no extra button or "tap to start" screen.
Everything that asks for permission today moves behind the switches
| Today | After |
| "Let's go" tap → rear camera, then mic | Gone. The default is "speaks, doesn't listen." |
| First tap on iPhone → motion prompt | Only when Shake is switched on |
| After the greeting, the mic opens by itself (live voice) | Only when Talk is on |
| After the greeting → spoken gesture invite plus a camera prompt | Removed |
| Returning visitors → auto-resume what was granted | Resume only what's switched on, per device |
If a permission was denied, that switch shows "Allow in Settings" instead of failing silently. iPhone never asks a second time.
Not changing
Cards, double-tap to launch, Details, Stack, the Signal, and narration in your voice all stay. The "Let's go" welcome card goes away.
Open questions
- Should the LAUNCH pill stay hidden? Double-tap still launches, and Details has a Launch button.
- Should the Customize label stay as text, or shrink to just ⚙ after the first visit?
Self-critique — Fable adversarial pass
Notes from the v1 review that still apply:
- Playing sound without asking is a surprise. Fable preferred a "▶ hear Byron" button. You chose autoplay. The plan respects that, and only falls back to "first touch" where the browser forces it.
- Hidden features don't get found. This is why v2 gets rid of the invisible "tap empty space" control in favor of a visible Customize pill.
- iPhone permission denials are permanent. Each switch shows a Settings hint when its permission was denied.