Block a user
Android touch model, phases 2-4: swipe to queue, and the other three lists
Android: touch gestures for track lists — swipe to queue, tap to play, long-press to multi-select, double-tap for the menu
Android: touch gestures for track lists — swipe to queue, tap to play, long-press to multi-select, double-tap for the menu
Phases 2, 3 and 4 are in PR #201, which finishes this. Phase 1 was
#199. The plan has moved to
.planning/plans/completed/019-android-touch-model.md.
Three things worth having on the issue…
Android touch model, phases 2-4: swipe to queue, and the other three lists
A dismissible surface should answer the back gesture, and the shell should own that
Android: touch gestures for track lists — swipe to queue, tap to play, long-press to multi-select, double-tap for the menu
Phase 1 landed (PR #199, merged as ff3875b): tap plays, hold
selects. The design is
.planning/plans/active/019-android-touch-model.md; #63 stays open and
claimed for phases 2–4.
**The…
Android touch model, phase 1: tap to play, hold to select
Android touch model, phase 1: tap to play, hold to select
Android: touch gestures for track lists — swipe to queue, tap to play, long-press to multi-select, double-tap for the menu
Taking this. Branch: 63-android-touch-model. The Direction asks for
the interaction model to be designed as one piece first, so that is
.planning/plans/active/019-android-touch-model.md and…
Android: raise every remaining control to the 44px touch floor
Android: every control that is not the transport is below the 44px touch floor
Android: every control that is not the transport is below the 44px touch floor
Second pass landed in PR #198, and it closes this out: Settings, then the rest of the second table.
Settings was 120 controls, not 93. Swept on the device with all
eleven config-sections…