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.
A place for devs to Immortalise Apps
Another thread got me thinking - sorry if this is a stupid idea in some way - about whether there could be a system or place for devs who for whatever reason may not have the time to maintain or update certain apps, and who don’t mind doing so rather than those apps becoming obsolete, to leave the code for other devs or people who want to take on looking after the app. Of course profits and things would be something to be discussed but just as a way of keeping some apps alive that would otherwise fall away. We have some really unusual or niche ones on iOS from cool eccentric imaginative devs and there’s also a community thing so what do you think?
Comments
App Store mechanics are the biggest hitch. Every app is published by just one developer from one developer account. There's no mechanism for a community - published app. The source code could go somewhere and people could contribute as they do for other open source projects, but to get that available it has to be published by someone. Even if you set up some kind of foundation that maintains a developer account, I'm not sure there's a way to transfer apps between developer accounts and still maintain it as the same app.
There's the big hoopla over changes coming from the EU "side loading" thingamabob, but I don't know if or when that'll result in people just being able to download something from anywhere on the net and installing it on iOS.
I'm just used to thinking of apps as perishables. I don't let it bother me that every one of them can just slip away. But it's good that people like you are thinking in those directions. I'll watch the thread with interest.
There are a lot of other potential problems here as well, as I discussed here.
Eventually software, especially GUIs, becomes incompatible with current platforms (OS, devices). It may need to be completely rewritten, just to keep it alive. This is a completely thankless job, a labor of love. The original creator may accept it, but would someone else be prepared to do that work for free? The same applies to converting an IAA to run as AUv3.
The person (or business) who takes the job of publishing the app(s) needs to pay the annual fee for a dev license, needs to own a current Mac computer to run Xcode, needs to be able to test app compatibility with current devices, and needs to deal with the AppStore reviewers who may require major changes.
@wingwizard, are you volunteering to take the lead on this project?
No, mainly due to the fact that I’m not a dev which I feel may represent a minor issue in app development.
I was wondering if instead of letting apps fade they might become public domain and be taken up by another dev, who did have the time and liked the app, or was part of the iOS music community, or apps might be circulated and taken care of in this way. A dev already pays the fees anyway and all the things mentioned.
Whoever took it on would be taking money from the AppStore for it.
I didn’t know about that system, but didn’t mean the app being a community owned thing. Just that if there was a mechanism that meant when an app was going to fall by the wayside the dev at least had the option of tossing it that way in case another dev did want to take it on.
It’s interesting though, wonder if there could be like a collective dev account. You could just rerelease the app rather than transferring I would have thought?
Yeah I had heard about the other stores thing. Going to be really interesting. It’s funny when corporate policies and law clash. I mean, I enjoy it due to the fact that the former tends to forget it’s not the latter
Well, in that case, it could be as simple as the developer releasing the code as open source and posting it on GitHub. The licensing the developer chose would determine how it could be used. The developer could specify that only they can publish to the App Store, that anyone can publish their own or the identical version, whether or not it could be charged for, what permissions would be needed ... whatever.
The thing is though, there's no such thing as a single app being able to be published under more than one Apple Developer account. Even if the apps were identical, someone else publishing it would mean it's a separate app.
But if what you were asking about was just a developer saying, "I'll continue to publish the app, but am hoping for someone else to maintain it", there wouldn't be much standing in the way of that.
Well, to Apple, it would be a single developer account, and any fees and revenue would be transacted through the owner of that account. How many people arrange to deal with the account and distribution of costs/revenue on the other end probably (I haven't checked the Developer Agreement) makes no difference to Apple. I doubt there's anything stopping anyone from creating a sort of a foundation that owns an account.
Anyway, if you're interested in lots of confusing detail and speculation in such a discussion, there's the other thread @uncledave referred to.
Sadly, nothin' in life is really all that simple eh?
Thanks
Edit: I read the other thread. The only actual problem is code containing proprietary bits the dev wouldn’t want to give away, maybe in use elsewhere. I hadn’t thought of that and can see that could be a problem, unless perhaps someone is retiring. That would be a good example of it being useful
Just transfer the code on GitHub, one dev withdraw the app the other submit. Love GitHub and Google collab and that hugging face whatever it is site for ai
The rest is motivation, which is basically are there enough defunct apps that something might be worthwhile. Perhaps o should make a thread for that.
I was just thinking of more of a specific repository and culture place to discuss for this to happen. GitHub ideal as the means.. even a section on this forum or something as a culture