Loopy Pro: Create music, your way.
What is Loopy Pro? — Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.
Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.
Download on the App StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
UI buttons responsiveness vs UI scrolling.
I just wanted to point out a touch screen UI design behaviour that tend to make them very unpleasing to use if not making one mad. Perhaps It will make some sense to some ios users and might give developpers a hint for future apps UI, or not.
How often have I tapped on a botton with a slight unwanted unavoidable side sliding movement and ended up moving the UI/menu instead of activating the damn button. Such a pita.
Buttons on touchscreen UI imho should work like real life buttons, as soon as you touch them, they respond. Not when you unpress it or only if you’re doing so in a perfect vertical movement.
As if one was playing a synth sitting on a teflon table slippering around while trying to play it.
It seems to be a design paradigm, and I can’t wait to see it shifting.
The best scenario for a windowed UI, is to have a scroll bar, (hold paradigm that seemed unmatched)
I like those virtual synth key beds that will play every note under your steady finger while the keys are moved by another finger scrolling the keys, it give such a realistic feeling. Mini Synth by EHX key bed behave that way.
Comments
>
Personally, I love the 'can't see what the control is doing because my finger is in the way' UI feature.
Give me rotary knobs or give me death.
Oh wait! I know! Rotary scrolling! Yeh.
This problem is not that much about which event handles action (onTouch vs. onRelease) but about SIZE of touch area.. many devs do mistake and they use touch area just in same size as UI of element .. lot better strategy is increase touch area to be bigger than UI of touched element - in that cases it works WAAAY much better ..
Plus - if you need to listen also to other events (like gestures - multiple touch, slide, etc) - then "onTouch" is no go because other events (which may, in context of app, trigger different action) are triggered AFTER onTouch ..
Hm.. if you're talking about knobs and sliders, i think most apps works the way that after you start tweak, until you don't release touch you can move finger to left or right and continue tweaking by moving fingers up/down, while you see the control UI .. it's good standard in many apps ...
In a custom button code you can override the gesture recogniser and return 0 so it does not effect that touch area and scroll the view. But, yes agree the touch area should be bigger than the button and it should be triggered on touch down rather than waiting until touch up.
.
Thank you!
An example of that is Step Bud, a super step sequencer filling a hole in ios music ecosystem, but with one big killer feature, meaning killing the joy: the down scrolling button bar, going left and right instead of just responding.
Most wanted features + bad UI = frustration or resignation, quite opposite of sparking some joy...
Hey @Philippe, which "down scrolling button bar" do you mean?
You mean the mode and settings strips?
Hi @cem_olcay , yes, I mean I guess.
I mentionned your app cause it was just a classic case of scrollable buttons,
I didn't mean to diminish your work.
These kind of things are everywhere in ios and happen everywhere the screen is too small to cram everything into it.
I am more a fan of nanoloop kind of UI where everything is on screen and symbols are used instead of words to take less space. Muscle memory happens, and so workflow, and buttons don't "slip".