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
The only encouraging thing is this issue was widely reported on tech and gaming websites last week with universal criticism.
So although Apple will do whatever they want, there's a lot of exposure. It's probably what lead apple to clarify and slightly relax the rules.
https://www.theverge.com/2022/4/29/23049576/apple-outdated-apps-removal-extension-90-days
Is this all you need to do a safe backup?...
Getting started with iMazing:
https://imazing.com/guides/getting-started-with-imazing
https://developer.apple.com/news/?id=gi6npkmf
I agree. I would like a bit more specificity on what a "minimal download threshold" is. But, this is a much more sane way to state the policy.
Yeah, they are probably all safe for a couple of years. The thing that would concern me if I were trying to make a living on this would be keeping older products in peoples' awareness. For smaller apps, the attention cycle pushes towards making more apps and not spending too much time on older apps. The new apps get the airtime on YT.
The thing that had me the most nervous with the original announcement was the thought that when they do the app review of an AU, they're going to reject a good chunk of them almost randomly because the container app part doesn't provide enough function. That's where the appeals process comes in and it's a pain because they don't ever seem to train the reviewers on music apps.
Yes, but that chart didn't look so good for the Mac a couple of years ago. They've always made Apple good bunch of cash though.
My response when anyone tells me they are going to kill the Mac is that you'll know it's true when they port Xcode to Windows.
😂
Do you ever get "But ... Xcode is coming along with Logic to iOS at WWDC this year!" in response?
That makes a lot more sense!
Now quick, go download my Sector and Bitwiz Audio Synth!
Makes me think that running about 18 month periodic sales and promotion cycles would be a good tactic. Maybe I should write an app for developers that tracks your app update history and sends you a notification when it's time to run a promotion. I wonder if Apple would approve that one.
What's stopping developers from just adding arbitrary legacy updates every 2 years, with nothing changed except for a changelog that says 'f apple [current year]'
Good point. I think I'll have to write my new app for the Mac instead
.
At the very least, you have to update the version number. The submission requires that. And, that means you have to do a new archive build to submit. There's also the point that there is a cryptographic hash for the components of the build that is generated during the signing process. That would make anything that didn't have any changes obvious. To get a new submission through doesn't take a big change. The last update I did of LRC5 was just changing the name of one parameter that I had accidentally made a duplicate of another parameter. That small change was enough and went through fine. It was a real bug though.
There are several posts upthread addressing this if you care to hunt them down. Short answer: it isn't always as simple as that. Even recompiling an unchanged app after a couple of years can have complications due to a number of factors.
This is a really good idea man. do it! if you are prolific in coding this could possibly be done in swift alone on an ipad lol.... OR, devs could write a shortcut on their ipad that adds a calendar reminder in 16 months give or take that its time to do a little upkeep and promotion lol shrug still an app specifically for that might be cool i wonder if you could get apple to endorse it as their official 'Quality Software Calendar App for Developers' since apples mission isnt $$$, no no no ye of little faith and much cynacism, in their own words "Apple always wants to help developers get and keep quality software on the App Store" so quote back their own words to them when you pitch the app to them.
idk how any dev copyrighting or patenting works but try to get ownership of the idea and the app name before you pitch it to apple so they dont just steal it...
SO, EVERYBODY, ARE THERE ANY APPS WE NEED TO HURRY AND GET BEFORE THEY ARE REMOVED?
If you get them, they won’t be removed.
There's no way anyone here could know that unless they're a developer that has heard from Apple. Even if we made a list of apps that haven't been updated for three years, we wouldn't know if they were below the download threshold, and we would have no way of knowing if the developer would update the apps to prevent that happening if they were notified.
Besides ... why would anyone buy an app that they didn't already want just because it could disappear from sale?? And, if an app did disappear from sale, there's also a much higher probability that it will be removed entirely at some point by the developer removing it or letting their yearly developer fee lapse. If removed in that fashion, then it's not even available any longer in your purchased items.
ARE WE REALLY GONNA PANIC OVER A HANDFUL OF OLD AND NO LONGER UPDATED APPS?
Disclaimer: I've had my FOMO vaccine and all booster shots. ymmv
Yep.
I'd buy that for a $
The ruling update makes more sense but that was a big PR cockup from Apple, but it's good that they do respond to criticism
All those people building cases against App store monopoly will be much more optimistic now though.
Have a 1 character length label with the font color set to your app’s background color, and the text set to “.”. Place it in the very bottom left position of your screen.
When you then need to refresh the app, change that label’s text to “,” or whatever.
Then when you recompile to obtain the new version number then the hash will be different.
That would got you over the hash problem, no? Or is that too simplistic? I’m a dev but not an Apple app dev so have no experience of their submission and review processes.
If “.” would be too obvious a bs value for a label to the reviewer, maybe “Frequency Cutoff” as that sounds a legit value, just change it to “lfo rate” or whatever when an app refresh is required. No user is ever going to actually see it and as a label if they accidentally clicked it then nothing’s going to happen.
I worked for a company (thank gawd I don't anymore...) that constantly wanted to update the App Store description for their apps which also requires a new build to be uploaded. Literally all I was changing were the version numbers and they got through review every single time.
Were they fishing for descriptions that would get more hits? Or, was it part of a marketing strategy to keep the apps more visible in the store?
That confirms at least that a submission with no changes to the executable can get through. So, my tactic is going to be that once a year I'm doing a release that has the release notes of "No changes, building against latest SDK."
To be honest, I had no clue what they were trying to accomplish, and I suspect neither did they. It's pretty much why I left
But yeah, something like Updating to latest SDKs sounds good to me too. And I guess the longer you leave re-building with new Xcode versions, the more painful it is. Once a year doesn't sound too bad...
worked for me (dev with app targeted by Apple death ray)
Nice! It's good to hear you were able to get your app through the process.
Building against latest iOS SDK is a reasonable reason to update an app. Apple might fix bugs in the newer SDKs, and other improvements. For example there was one (14.5 perhaps?) where they added support for the display aspect ratio of the new iPad Mini. Apps built with older SDKs got a black border on the sides. Unfortunately they also dropped support for macOS Catalina, which meant I had to upgrade my macOS. Unfortunately my mac was too old to support the next macOS version, so I also had to order a new mac first! (This can serve as an example of how it can indeed be complicated to just recompile an app with latest xcode)
As a developer myself, I can empathize with the frustrating changes to the policies, but as a customer, I do not feel as strongly against the policy.
I already scan the last updated date before buying an app, and it was frustrating to see so many apps being sold for 20-50$ after no updates for over 4 years. The last updated date is a major part of my decision to buy or not, already, although it is quite possible the dev just updated the version number.
At this point, the App Store feels like it is filled with abandonware that is still monetized - not a great look from a customer’s perspective.
It’s not very customer friendly to gamble money on apps on the off-chance that the dev released a golden stable version of the app 4 years ago that still works today.