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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Nonatone is now open source!

2»

Comments

  • It's a tricky one @wim because let's say Apple continue to host apps when developers move on so to speak...

    What happens come iOS 20 or whatever, and something Apple changed totally breaks the app. We're no strangers to that on iOS, right? Who's responsible for fixing it? :#

    Of course if breaking changes weren't so prevelant on iOS, that might not be such a big deal, but, well... yeah. Like I say, it's a tricky one!

  • @wim said:

    @tspring said:

    @ninobeatz said:

    @tspring said:

    @Rob_Jackson_Music said:
    [edit for clarity: Outside of the Apple ecosystem...]

    You need a code signing certificate and that costs, otherwise your app / you will get flagged as not trusted.

    You also need to host the app download and process payments - again, that costs.

    @tspring - my message was more at folks thinking $99 a year was somehow unreasonable. I happen to think the opposite. :smile: And fair play for open sourcing your app. B)

    The VST3 developer license is needed also and you have to apply for one.

    To be fair I was the one saying $99 a year is unreasonable, but despite that being the main conversation it's not actually something I was that bothered about originally. It was more that it was coming time to renew it, that right now for me isn't an amount of money I can easily spend and it just seemed like it'd be better for everyone if I open sourced it instead.

    @tspring Im a customer of Nonatone and would like to help keep it alive on iOS. If you need help with the developer fee, I’m here to help.

    That's very generous of you, but unfortunately it's easier said than done for a few reasons (one of which being a mistake on my end). From my perspective, I'd been quite happy to see its life on the App Store end here and continue as open source, but if people really want it to remain on the App Store, I'll find the money for another year and we'll deal with it in 2026.

    That just pushes the problem down the road a year while putting you out $99 bucks. It's unfortunate that Apple pushes the hardship down to users when they could just continue to host the app files, but that's their right I suppose. Still, you shouldn't have to compensate for that, IMO.

    That's pretty much my problem with it, if it was a case of paying $100 to let people keep accessing the app, I'd happily pay it, but like you say that's not the case, it just delays the problem for another year. In fact it'd be even worse, at least this year its couched with the good news of it being open sourced, if it goes for another year (or another, but you get the idea), the message would just be "sorry, its over".
    Thats why my preferred solution would just be accepting the inevitable and letting open source be its future, but people did pay for my app and regardless of whatever fee's there are I do owe them that app, so I will pay for another year if that's what people want, and maybe next year I'll do it again, but it'll obviously end at some point.

    As always, thanks to everyone for being so understanding :)

  • @Rob_Jackson_Music said:
    It's a tricky one @wim because let's say Apple continue to host apps when developers move on so to speak...

    What happens come iOS 20 or whatever, and something Apple changed totally breaks the app. We're no strangers to that on iOS, right? Who's responsible for fixing it? :#

    Of course if breaking changes weren't so prevelant on iOS, that might not be such a big deal, but, well... yeah. Like I say, it's a tricky one!

    To be fair there are apps on the App Store itself which are at least partially broken in newer iOS versions. Nonatone was inspired by the great DR-OM which itself sometimes has issues with modern iPads.
    It is a tricky one though, like I say I was under the impression that Apple allows people who previously purchased an app to download it whether its on the App Store or not (unless it got taken down for a violation or something). That might be the case, some people say it is and others say it isn't. If it is, I think we're all good, but if not thats where it becomes tricky.

  • wimwim
    edited May 7

    @Rob_Jackson_Music said:
    It's a tricky one @wim because let's say Apple continue to host apps when developers move on so to speak...

    What happens come iOS 20 or whatever, and something Apple changed totally breaks the app. We're no strangers to that on iOS, right? Who's responsible for fixing it? :#

    Of course if breaking changes weren't so prevelant on iOS, that might not be such a big deal, but, well... yeah. Like I say, it's a tricky one!

    The whole thing could be solved by allowing apps to be installed from backups made from one's devices rather than the App Store being the only source for backups, and a 3rd party utility being the only way to accomplish a backup and restore of an app.

    (I'm talking about fully-signed and locked to the same Apple ID here, not just backup and restore of any app to any device. Hopefully nobody will read the above and think I'm opening that can of worms.)

    At least then it would be the fault of the user, not the developer or Apple, if they got into a situation where there was no backup. Sure, there'd be the problem of breaking changes, but that's always been true with computer operating systems.

  • edited May 7

    @tspring said: some people say it is and others say it isn't.

    Well... maybe we should take Apple's word for it? :smile:

    If your Apple Developer Program membership expires, your apps will no longer be available for download and you won’t be able to submit new apps or updates or access Certificates, Identifiers & Profiles. However, your apps will still function for users who have already installed or downloaded them, and you will still have access to certain App Store Connect features and free development resources.

    https://developer.apple.com/help/account/membership/renewal/

  • edited May 7

    @wim said: Sure, there'd be the problem of breaking changes, but that's always been true with computer operating systems.

    that's always been true with Apple computer operating systems :smile:

    Stuff that's mission-critical, like defence, air traffic control, healthcare, etc., the number one rule is...

    absoloutely zero breaking changes! :smile:

    Windows Embedded for example, often used in healtchcare devices never had breaking changes.

  • edited May 7

    @Rob_Jackson_Music said:

    @tspring said: some people say it is and others say it isn't.

    Well... maybe we should take Apple's word for it? :smile:

    If your Apple Developer Program membership expires, your apps will no longer be available for download and you won’t be able to submit new apps or updates or access Certificates, Identifiers & Profiles. However, your apps will still function for users who have already installed or downloaded them, and you will still have access to certain App Store Connect features and free development resources.

    https://developer.apple.com/help/account/membership/renewal/

    Well that just confirms the tricky situation, obviously Apple isn't gonna change their policy because of me so where does that end up, I'm stuck paying Apple for the rest of my life because I sold an app once, or users just have to accept they don't get what they paid for anymore? Neither one of those sounds particularly fair, but thats the situation it seems we're in.

    From my perspective, this obviously has to end at some point, and now where at least I can open source it to give something back seems as good a time as any. My hope was that open sourcing it could, at least in some way if not completely, turn a bit of a negative into something more positive

  • @tspring I don’t think there’s a better outcome in the circumstances than the one you came up with initially.

    I love this app, and it’ll be a pity I can’t install it on new devices or reinstall it if there’s a problem, but thank you for at least trying to find a workable solution by open sourcing it, and for coming here and explaining what’s happened.

  • wimwim
    edited May 8

    @bygjohn said:

    I love this app, and it’ll be a pity I can’t install it on new devices or reinstall it if there’s a problem, …

    You can if you can back it up with iMazing before it goes away.

  • @bygjohn said:
    @tspring I don’t think there’s a better outcome in the circumstances than the one you came up with initially.

    I love this app, and it’ll be a pity I can’t install it on new devices or reinstall it if there’s a problem, but thank you for at least trying to find a workable solution by open sourcing it, and for coming here and explaining what’s happened.

    Thank you, and sorry it did have to come to this, but who knows, maybe someone else will take on the idea and build something better with it (I know there were a lot of other features people wanted to see, like compatibility with midi-only DAWs). Or maybe when I'm in a better place financially I'll be able to relist it and it'll go back to how it was before.

    As with before, I do genuinely appreciate how understanding everyone is

    @wim said:

    @bygjohn said:

    I love this app, and it’ll be a pity I can’t install it on new devices or reinstall it if there’s a problem, …

    You can if you can back it up with iMazing before it goes away.

    Thankfully, the licence doesn't expire until the 20th, and even then I think there's a 90 day grace period (don't quote me on that, but I've seen that around), so you should have plenty of time

  • @tspring said:

    @wim said:

    @tspring said:

    @ninobeatz said:

    @tspring said:

    @Rob_Jackson_Music said:
    [edit for clarity: Outside of the Apple ecosystem...]

    You need a code signing certificate and that costs, otherwise your app / you will get flagged as not trusted.

    You also need to host the app download and process payments - again, that costs.

    @tspring - my message was more at folks thinking $99 a year was somehow unreasonable. I happen to think the opposite. :smile: And fair play for open sourcing your app. B)

    The VST3 developer license is needed also and you have to apply for one.

    To be fair I was the one saying $99 a year is unreasonable, but despite that being the main conversation it's not actually something I was that bothered about originally. It was more that it was coming time to renew it, that right now for me isn't an amount of money I can easily spend and it just seemed like it'd be better for everyone if I open sourced it instead.

    @tspring Im a customer of Nonatone and would like to help keep it alive on iOS. If you need help with the developer fee, I’m here to help.

    That's very generous of you, but unfortunately it's easier said than done for a few reasons (one of which being a mistake on my end). From my perspective, I'd been quite happy to see its life on the App Store end here and continue as open source, but if people really want it to remain on the App Store, I'll find the money for another year and we'll deal with it in 2026.

    That just pushes the problem down the road a year while putting you out $99 bucks. It's unfortunate that Apple pushes the hardship down to users when they could just continue to host the app files, but that's their right I suppose. Still, you shouldn't have to compensate for that, IMO.

    That's pretty much my problem with it, if it was a case of paying $100 to let people keep accessing the app, I'd happily pay it, but like you say that's not the case, it just delays the problem for another year. In fact it'd be even worse, at least this year its couched with the good news of it being open sourced, if it goes for another year (or another, but you get the idea), the message would just be "sorry, its over".
    Thats why my preferred solution would just be accepting the inevitable and letting open source be its future, but people did pay for my app and regardless of whatever fee's there are I do owe them that app, so I will pay for another year if that's what people want, and maybe next year I'll do it again, but it'll obviously end at some point.

    As always, thanks to everyone for being so understanding :)

    Why don't you add an in-app purchase for tips? That could help you defray the cost for you to continue paying your annual fee. Have a small tip ($1.99), medium tip ($4.99), large tip ($9.99... or more), for example.

  • edited May 8

    Sorry to hear this @tspring I wish you nothing but the best in the future.

  • edited May 8

    @wim said:

    @espiegel123 said:

    @wim said:

    @espiegel123 said:

    Isn’t the iMazing app archiving broken at the moment? I haven’t verified but a few people have reported recently that it wasn’t working.

    I read that too, but I'm backing up apps without issues as I write this. I did decline to update 3.0.something to 3.2.something just now. I'll give it a try with the update after I get through backing up what I need to.

    Tx for the info.

    I installed the latest 3.2.0 version and iMazing is working again for backing up apps from the App Store.

    I need iMazing

    @wim do you use the free version or do you pay for iMazing 3?

  • @Rob_Jackson_Music said:
    It's a tricky one @wim because let's say Apple continue to host apps when developers move on so to speak...

    What happens come iOS 20 or whatever, and something Apple changed totally breaks the app. We're no strangers to that on iOS, right? Who's responsible for fixing it? :#

    Of course if breaking changes weren't so prevelant on iOS, that might not be such a big deal, but, well... yeah. Like I say, it's a tricky one!

    Yea I see both sides of it.

  • @Poppadocrock said:

    @wim said:

    @espiegel123 said:

    @wim said:

    @espiegel123 said:

    Isn’t the iMazing app archiving broken at the moment? I haven’t verified but a few people have reported recently that it wasn’t working.

    I read that too, but I'm backing up apps without issues as I write this. I did decline to update 3.0.something to 3.2.something just now. I'll give it a try with the update after I get through backing up what I need to.

    Tx for the info.

    I installed the latest 3.2.0 version and iMazing is working again for backing up apps from the App Store.

    I need iMazing

    @wim do you use the free version or do you pay for iMazing 3?

    Free.
    Detailed iMazing app backup info here:
    https://forum.loopypro.com/discussion/comment/1363294/#Comment_1363294

  • @wim said:

    @Poppadocrock said:

    @wim said:

    @espiegel123 said:

    @wim said:

    @espiegel123 said:

    Isn’t the iMazing app archiving broken at the moment? I haven’t verified but a few people have reported recently that it wasn’t working.

    I read that too, but I'm backing up apps without issues as I write this. I did decline to update 3.0.something to 3.2.something just now. I'll give it a try with the update after I get through backing up what I need to.

    Tx for the info.

    I installed the latest 3.2.0 version and iMazing is working again for backing up apps from the App Store.

    I need iMazing

    @wim do you use the free version or do you pay for iMazing 3?

    Free.
    Detailed iMazing app backup info here:
    https://forum.loopypro.com/discussion/comment/1363294/#Comment_1363294

    Right on. I was browsing and saw they had several free software options then paid options as well. Thanks for clarifying I’m definitely doing the free version then… cheers mate.

  • edited May 9

    @NeuM said:

    @tspring said:

    @wim said:

    @tspring said:

    @ninobeatz said:

    @tspring said:

    @Rob_Jackson_Music said:
    [edit for clarity: Outside of the Apple ecosystem...]

    You need a code signing certificate and that costs, otherwise your app / you will get flagged as not trusted.

    You also need to host the app download and process payments - again, that costs.

    @tspring - my message was more at folks thinking $99 a year was somehow unreasonable. I happen to think the opposite. :smile: And fair play for open sourcing your app. B)

    The VST3 developer license is needed also and you have to apply for one.

    To be fair I was the one saying $99 a year is unreasonable, but despite that being the main conversation it's not actually something I was that bothered about originally. It was more that it was coming time to renew it, that right now for me isn't an amount of money I can easily spend and it just seemed like it'd be better for everyone if I open sourced it instead.

    @tspring Im a customer of Nonatone and would like to help keep it alive on iOS. If you need help with the developer fee, I’m here to help.

    That's very generous of you, but unfortunately it's easier said than done for a few reasons (one of which being a mistake on my end). From my perspective, I'd been quite happy to see its life on the App Store end here and continue as open source, but if people really want it to remain on the App Store, I'll find the money for another year and we'll deal with it in 2026.

    That just pushes the problem down the road a year while putting you out $99 bucks. It's unfortunate that Apple pushes the hardship down to users when they could just continue to host the app files, but that's their right I suppose. Still, you shouldn't have to compensate for that, IMO.

    That's pretty much my problem with it, if it was a case of paying $100 to let people keep accessing the app, I'd happily pay it, but like you say that's not the case, it just delays the problem for another year. In fact it'd be even worse, at least this year its couched with the good news of it being open sourced, if it goes for another year (or another, but you get the idea), the message would just be "sorry, its over".
    Thats why my preferred solution would just be accepting the inevitable and letting open source be its future, but people did pay for my app and regardless of whatever fee's there are I do owe them that app, so I will pay for another year if that's what people want, and maybe next year I'll do it again, but it'll obviously end at some point.

    As always, thanks to everyone for being so understanding :)

    Why don't you add an in-app purchase for tips? That could help you defray the cost for you to continue paying your annual fee. Have a small tip ($1.99), medium tip ($4.99), large tip ($9.99... or more), for example.

    I guess the best way to put it is that it's more of a cash flow problem. Over the year it might way pay for itself even without tips, or at least close to, its just the fact that I can't really afford to spend the full $100 right now all at once, that and the fact I just don't have a lot of free time to work on it at the moment unfortunately (made worse by the fact that I made a mistake when moving it over to open source, I won't go over the details but I'd need to do some work just to get it working in dev again). Adding a tip system would obviously be pretty straightforward, but it'd still take me a few days to get right at least. Also now that it's open source I'd need to do some work to make sure I'm not committing my signing details to the repo, so a bit of work on top of that, but you get my point.

    It is a really nice suggestion though, so thank you

Sign In or Register to comment.