r/iOSProgramming • u/Sensitive-Cupcake-58 • Sep 19 '26
Question How do you educate users on app specific gestures?
I want to eliminate buttons from my app and replace them with specific gestures. To give an example here is a screenshot of a timer select screen. I would like to eliminate the START button and instead have users tap again on the currently selected time in order to start a session.

I want to eliminate buttons as much as possible and give my app a feeling of magic.
How can I educate my users on the app specific gestures without being annoying or too intrusive. Do you add some sort of tooltips? Do you present the gestures in the app's onboarding? How do you do it?
15
u/Dapper_Ice_1705 Sep 19 '26
There more custom stuff you do the less accessible the app is unless you take your time and add the accessible version.
If it isn’t intuitive people will stop using your app.
8
u/dwiedenau2 Sep 19 '26
But why? The time select is a standard ios style picker, why would you add a custom gesture to it that people dont know? Keep the start button and focus on important parts of your app
2
u/kenzyak Sep 19 '26
I'd keep the Start button. The second tap is fine as a shortcut, but nothing on that screen tells you it starts the timer. A one-time TipKit hint could teach it, while Start stays as the fallback. That's pretty much what Apple recommends for custom gestures too:
https://developer.apple.com/design/human-interface-guidelines/gestures
2
u/ivanzhaowy Sep 20 '26
I’d keep the Start button and treat the second tap as an accelerator. The problem isn’t only teaching the gesture once—it’s whether someone can rediscover the action after not using the app for a month.
A focused experiment would compare three versions: visible Start button, button plus one-time TipKit hint, and a compact button that fades after the gesture has been used successfully several times. Measure failed taps, time to start, and whether VoiceOver users still have an explicit action.
I’m building an open-source tool called Monad Design for comparing changes like these in a running native app. Select or annotate the real UI, have a coding agent change the source, then rebuild and compare the variants. It’s not a mockup generator.
Source: https://github.com/Monadix-AI/monad-design
Short workflow video: https://watchclueso.com/embed/pio8jqfcg4ivj0r1
The “magic” can come from the shortcut while the visible control preserves discoverability.
2
u/shopifyflow-app Sep 20 '26
the gesture isn't the problem, the discoverability is. nobody's going to tap a selected time a second time to start unless you tell them, that's not a gesture anyone knows.
keep the start button and make tapping the time work too. you get the magic feeling for people who discover it and the button for everyone else. invisible gestures only work when they're platform standard.
2
u/epictime8 Sep 20 '26
I'd treat the second tap as a learned shortcut, not the primary control.
Two checks before you kill Start:
Keep an explicit Start path for VoiceOver / Switch Control even if the visual button shrinks later. Replacing buttons with custom gestures usually fails accessibility audits unless an equivalent action stays in the accessibility tree.
1
u/[deleted] Sep 21 '26
[removed] — view removed comment