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.
Comments
@PaulB It being bad manners implies there is something inherently concerning about it. Which is why I still ask: what is a logical concern regarding usage data tracking?
I can't think of a single app / service / platform that asks first. iOS doesn't ask first IIRC. Asking first would mean a pop-up on first use of the app, and would send a signal to the user that this is something they need to be worried about. Most would say no, and be left with a taste of anxiety in their mouth before even using the app. The few who say yes would massively skew the results away from the rest. I'd rather not track at all than ask first.
Is there a logical concern to chewing gum when greeting the queen?
Seriously, if we met on the street, got chatting and you invited me back to your home for a coffee, wouldn't you think it bad manners if I picked up your phone and made a short phone call without asking you first? What would be your logical concern in that case?
The point about a EULA is that it is usually displayed and agreed to on installation or first use, so they do ask. Apps generally don't. Pointing at someone else's EULA after the fact or saying that everyone else is doing it doesn't cut it as a justification, it's still taking liberties.
It's not someone else's EULA - it's guitarism's EULA. That's the way Apple's set it up - if an app doesn't provide it's own EULA it inherits the default one. It brings up the question of when does the user agree to this blanket EULA for all non-custom-EULA apps. I'm not 100% sure but I believe that the EULA that iOS presents whenever you install a new version of iOS (or setup a new iOS device) states something to the effect that it (i.e. the iOS EULA) applies to all apps you install on the device unless the app has its own EULA. So the permission for usage data tracking is buried in a EULA that everyone must agree to when they first setup their device. Thus it's pretty obfuscated, but it is there.
Wrt real-world analogies, it's akin to a scenario where say you have employed a live-in housekeeper whose name is iOS Alfred (let's assume you're Batman) and your agreement with him states that not only does he have permission to make short phone calls on your landline, any friends or family of his that come over (after being screened by you) also have automatic permission to make occasional short phone calls. Or perhaps he runs a housekeeping services organization and can offer you maids, gardeners, chauffeurs etc and each of them automatically gets permission to make short phone calls while at your place.
.
Hey, if someone make a point of telling me they're tracking usage data BEFORE I buy an app and what's more provides an opt out toggle, then I'm likely to see it as benign and let it happen. When someone obfuscates and buries the info somewhere obscure so that I'm unlikely to see it without searching around or reading the entire Apple EULA next time I upgrade the iOS (not going to happen, I'm sticking with 6.1.3), then that immediately gets me suspicious and less likely to trust them. Bad manners AND underhand.
So its like beta testing for paid apps? I'd hope developers would spend their time researching, designing and debugging the app before release rather than pouring over usage statistics and re-designing the interface based on lowest common denominator usage patterns. I think thats how we ended up with dumbed down versions of Final Cut and Pages. I'm sure many users just flail around and figure things out on the fly and thats ok, but it doesn't tell you much about how well the app is being used by those who take the time to learn and get into it. I doubt some of the great original synths, hardware and software were made by people who spent all their time in a feedback loop with customers.
Also think that the users who bother to complain would be exactly the people to pay attention to. A lot of buyers will simply move on because they have no idea you are correcting issues by secretly observing them. They will delete the app, and there goes your spying tool. Someone who emails you is giving vital information the old fashoned way and is more likely to stick with you through the correction of an issue.
Luckily you don't have to trust me or any other dev regarding misuse of personal info - iOS doesn't allow it. Apps can only track data on how they're being used, they can't get access to the user's personal info. A few things (e.g. contacts, location etc) are opt-in meaning the user gets asked per-app before the app gets the info, and other things (email address etc) are just not allowed at all. Apple's designed usage data tracking to not be about user privacy. In fact, the iOS opt-out switch for its own tracking is not located in Settings -> Privacy but in Settings -> General -> About -> Diagnostics & Usage.
@smeeth It's not really about beta testing or finding bugs - it's not actually possible to find bugs via usage data tracking anyway. Most developers don't spend hours redesigning their app based on usage data. But e.g. I recently had a situation where I was considering droping iOS 5 support (because it was a lot of work to support it for a specific feature I was adding). I looked at my usage data and found that 5% of my users are still on iOS 5, so I ended up doing the extra work to support them rather than leaving them behind.
I wonder if there is a bit of 'shoot the messenger' happening here. I could of course have stayed silent on this whole topic but I chose to disclose precisely because I do care about transparency. But my expectation is that the vast majority of apps are doing usage tracking under the iOS 'blanket EULA'. Some of the one-man apps (or 'abandoned apps') might not do it, but I expect that usage data is tracked by 99% of apps that are made by more than one person and actively kept up-to-date.
Wasn't having a go at you, Rhism, just the covert practice. You're just the one who is engaging in the conversation. Tell me, how does the data get to you if I'm offline whenever I use Guitarism?
It's a tough one for sure. Yay for being up front but being asked first via a blocking dialog would just suck terribly. If your hairs are up over tracking/privacy I can see why this would be an ostensibly attractive option but my god, in practice, no thank you. Most of us will just learn to tap 'ok' anyway as evidenced by clause #2 of the iOS EULA! More noise = fail.
Google attempts to deal with this problem with chrome and android apps by telling you what the app you're about to install can track/observe. It's a cluster**** though. Way more confusing than it needs to be. I'm reasonably comfortable with this stuff and why randomAppX might need access to personalDataY to do what it does but it still freaks me out a bit when I install a chrome app. Enough so that I sometimes say forget it and move on without the app. I sometimes wonder how much of a factor this sort of reaction is when comparing global download stats for android vs apple app stores.
@simon cheers and no problem. I'm in a weird spot. I basically hate tracking (the EFF is one of my annual charities) and any sort of heavy handed invasion of what I deem to be private but I also make apps/sites that employ anonymous usage tracking. I find the data incredibly valuable and know first hand that there is absolutely nothing personally identifiable about the sort of things I track. Indeed, I wouldn't find any value in being able to do that. For people trying to sell you shoes though, it is a different story.
@rhism I hope that you don't get squeeky wheeled into removing legit usage tracking that makes your app better and better for all of us.
@smeeth It's not beta testing. Think of it as "release the best product you can and continue doing research to make the best possible updates for your users". And you can for sure gather better info than you're implying. You might ask the data "how many people clicked on the midi button?" but you can also cross that question with "of those users, how many used my app 10 or more times?". You might also ask "Who only used it once?" and find out that uncommitted users are being scared off and try to figure out why.
@paulb it either doesn't go out or it's cached until you go back online, depending on how it's setup.
Where is it cached? And what uploads it if the app is no longer running?
I would assume that apps own cache and it's uploaded next time you use the app
@PaulB If you're offline the data doesn't get to me. I believe Flurry caches a little bit (in the application's temporary file store) in case you're online next time the app is launched, but it doesn't accumulate beyond a certain size.
@syrupcore Yep I'm pretty sure if the OS were to tell me each time I download an app "this app tracks X Y and Z" it'd just make me constantly nervous and anxious as it'd imply that I need to care about these things and if I choose the wrong thing it's all my fault.
Instead, iOS establishes a benign baseline for data tracking that doesn't include any personally-identifiable info, and requires all iOS users to agree that any app can follow that baseline without asking again. So it's taking away some control in exchange for a smoother experience - a very Apple thing to do. Note that Apple now even rejects apps that use the UDID which is a unique device ID, because it's theoretically possible (though practically really hard) to associate a UDID with a person and then figure out what that specific person is doing in an app. Privacy is important to Apple but so is iterative improvement of the platform, so they're doing their best to make sure that diagnostic data and privacy are completely separate and unconnected things.