Auto-advance a banner carousel that waits while a finger rests on it
A row of offers or levels that moves on by itself is lively, but it must not snatch the page away while someone is reading or dragging it. When it resumes after a touch, should it start counting again or continue? And a manual swipe should earn a full wait. Here are the rules that make it feel considerate.
Why this works
A moving row should serve the reader, not compete with them. Keeping the time that is left and stopping the clock while the page is held means a reader is never hurried, and a swipe, which is a choice, earns a full wait.
When not to use it
Do not auto-advance when the content matters for decisions, such as terms, prices or the only way to reach a feature. Moving it away on a timer hides it. Show a plain list, or let people move on themselves.
In the full entry
- What to build, step by step
- Starting values and the reason for each
- 3 common mistakes and the fix
- A diagram of every state
- 27 lines of example code with 4 checks that pass
- How your AI shows you that it works
Say this to your AI
Use the Spielerando entry "Auto-advance a banner carousel that waits while a finger rests on it" (read_entry casual-banner-carousel-that-pauses-while-touched) in my game. Build it step by step, and show me how you checked that it works.Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP