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.

KQ Apps

2

Comments

  • @RyoutaKira said:

    @Luxthor said:
    From what I can read, it’s only UIKit specific, and you have a need for multiple scenes support. Otherwise, it is a mundane update where you can just set the value of “UIApplicationSupportsMultipleScenes” to false.

    https://developer.apple.com/documentation/UIKit/specifying-the-scenes-your-app-supports

    There are two lifecycle modes. Scene-based lifecycle and App-based lifecycle.
    The Scene-based lifecycle started at iOS 13 and it is required in the iOS/iPadOS 27.
    Apps with the app-based lifecycle won't boot when built with the latest SDK next year.

    That is not related to which value UIApplicationSupportsMultipleScenes is.

    Yeah, I understand now what you meant by the “Scene feature”. Thank you for the clarification, and good luck fighting with Apple updates. 🤗

  • Thanks for explaining everything @RyoutaKira it really helps, Cheers!

  • What I honestly don’t understand is does that all mean that every current app needs to be re-created as a new separate app before iPad 27 releases? Did Apple really go that hard with incompatibility?

  • wimwim
    edited October 2025

    @vlaoladis said:
    What I honestly don’t understand is does that all mean that every current app needs to be re-created as a new separate app before iPad 27 releases? Did Apple really go that hard with incompatibility?

    It sounds like that only becomes a factor if you compile with the latest Apple SDK. I don't think you (usually?) have to use the latest SDK. And if you don't update an app, you don't have to re-compile it at all. So no, apps won't stop working but updates will potentially be problematic.

    I could be wrong about whether or not you can use an older SDK when recompiling apps.

  • @wim said:

    @vlaoladis said:
    What I honestly don’t understand is does that all mean that every current app needs to be re-created as a new separate app before iPad 27 releases? Did Apple really go that hard with incompatibility?

    It sounds like that only becomes a factor if you compile with the latest Apple SDK. You don't (usually?) have to use the latest SDK. And if you don't update an app, you don't have to re-compile it at all. So no, apps won't stop working but updates will potentially be problematic.

    But that really means that if the industry wants to keep going, everyone must re-buy all the apps they have sooner or later, no?

  • @vlaoladis said:

    @wim said:

    @vlaoladis said:
    What I honestly don’t understand is does that all mean that every current app needs to be re-created as a new separate app before iPad 27 releases? Did Apple really go that hard with incompatibility?

    It sounds like that only becomes a factor if you compile with the latest Apple SDK. You don't (usually?) have to use the latest SDK. And if you don't update an app, you don't have to re-compile it at all. So no, apps won't stop working but updates will potentially be problematic.

    But that really means that if the industry wants to keep going, everyone must re-buy all the apps they have sooner or later, no?

    No. Developers can choose to make a new app to recoup the cost of their development effort to accommodate the changes, or they can fold it for free into the existing app.

  • @wim said:

    @vlaoladis said:

    @wim said:

    @vlaoladis said:
    What I honestly don’t understand is does that all mean that every current app needs to be re-created as a new separate app before iPad 27 releases? Did Apple really go that hard with incompatibility?

    It sounds like that only becomes a factor if you compile with the latest Apple SDK. You don't (usually?) have to use the latest SDK. And if you don't update an app, you don't have to re-compile it at all. So no, apps won't stop working but updates will potentially be problematic.

    But that really means that if the industry wants to keep going, everyone must re-buy all the apps they have sooner or later, no?

    No. Developers can choose to make a new app to recoup the cost of their development effort to accommodate the changes, or they can fold it for free into the existing app.

    Ah, thank you very much for explanation, I thought every app will have to go this way.

  • Yeah I really hope this doesn’t mean I’ll have to re-purchase 897 auv3 apps

  • @Edward_Alexander said:
    Yeah I really hope this doesn’t mean I’ll have to re-purchase 897 auv3 apps

    Yeah, if more than a handful of devs are charging for new apps, I think the community will lose its collective mind lol, and understandably

  • @wim said:

    @vlaoladis said:
    What I honestly don’t understand is does that all mean that every current app needs to be re-created as a new separate app before iPad 27 releases? Did Apple really go that hard with incompatibility?

    It sounds like that only becomes a factor if you compile with the latest Apple SDK. I don't think you (usually?) have to use the latest SDK. And if you don't update an app, you don't have to re-compile it at all. So no, apps won't stop working but updates will potentially be problematic.

    I could be wrong about whether or not you can use an older SDK when recompiling apps.

    Somebody just sent me this link below. So does this mean you'll maintain the old apps after all @RyoutaKira and people should maybe ask for refunds on the new ones they bought unnecessarily?

    https://www.kiraqtech.jp/blog/clarification-about-legacy-apps-and-sdk-changes/

    This is what it says:

    Clarification About Legacy Apps and SDK Changes

    I sincerely apologize for the confusion caused by my earlier announcement, which was based on a misunderstanding.

    Initially, I believed that Apple’s “App-based lifecycle” would no longer be available in future versions of iOS, and therefore announced a plan to discontinue the Legacy apps and asked users to upgrade to new versions. However, after reviewing the information more carefully, I found that this change applies only when using the latest SDK. This means that the Legacy apps are still very likely to continue working.

    I deeply regret having spread incorrect information and for encouraging upgrades that may not have been necessary. Going forward, I will take greater care to confirm details before making announcements, to ensure that I do not cause unnecessary inconvenience or concern.

    Once again, I sincerely apologize for the misunderstanding and any trouble it may have caused.

    2025-10-03,
    KIRA Ryouta"

  • @Gavinski said:

    @wim said:

    @vlaoladis said:
    What I honestly don’t understand is does that all mean that every current app needs to be re-created as a new separate app before iPad 27 releases? Did Apple really go that hard with incompatibility?

    It sounds like that only becomes a factor if you compile with the latest Apple SDK. I don't think you (usually?) have to use the latest SDK. And if you don't update an app, you don't have to re-compile it at all. So no, apps won't stop working but updates will potentially be problematic.

    I could be wrong about whether or not you can use an older SDK when recompiling apps.

    Somebody just sent me this link below. So does this mean you'll maintain the old apps after all @RyoutaKira and people should maybe ask for refunds on the new ones they bought unnecessarily?

    https://www.kiraqtech.jp/blog/clarification-about-legacy-apps-and-sdk-changes/

    This is what it says:

    Clarification About Legacy Apps and SDK Changes

    I sincerely apologize for the confusion caused by my earlier announcement, which was based on a misunderstanding.

    Initially, I believed that Apple’s “App-based lifecycle” would no longer be available in future versions of iOS, and therefore announced a plan to discontinue the Legacy apps and asked users to upgrade to new versions. However, after reviewing the information more carefully, I found that this change applies only when using the latest SDK. This means that the Legacy apps are still very likely to continue working.

    I deeply regret having spread incorrect information and for encouraging upgrades that may not have been necessary. Going forward, I will take greater care to confirm details before making announcements, to ensure that I do not cause unnecessary inconvenience or concern.

    Once again, I sincerely apologize for the misunderstanding and any trouble it may have caused.

    2025-10-03,
    KIRA Ryouta"

    I changed the old ones to deprecated. I won't update the old ones any more.
    I would like to support the new ones for a long time.
    If people want to refund, that is natural.

  • Also, Apple may force me to delete the legacies and users may loss the apps.

  • edited October 2025

    So…basically now it’s a “forced” upcharge that the existing owners have to pay for in order to receive future updates, for what turns out to be basically no reason? I mean, it was $3.99 when I bought it 3 years ago. To upgrade to the new one via a bundle would cost me $6.00, meaning total it cost me $9.99, when it’s $8.99 for new buyers. And we’re being forced to do this because the existing app was deprecated for no reason at all, it turns out . I hope I’m not coming off too harshly , but I’m legitimately trying to understand and quite frankly I hope I’m misreading things. If I am indeed misreading this, then I apologize. Thing is, these things are usually done in two ways 1) a free update for existing owners or 2) a new app that has additional features or something that radically differs from the original . This, well…

  • wimwim
    edited October 2025

    It's not the end of the world.
    Ryouta Kira is one developer I will gladly pay for a new iteration of any of his apps.

    The now-Legacy apps will probably keep working as they always have indefinitely. Nobody really needs to feel they've lost anything until if/when the legacy apps stop working and aren't fixed.

    "Forced upcharge?" Free labor to provide future updates indefinitely isn't something anyone is entitled to.

  • Maybe you’re right …. I guess maybe I’d understand more if I actually understood what some of this stuff like “scenes” and “SDKs” actually were !

  • @Fear2Stop Hey mate. Just wanted to put things into context. I would be more upset if KQ's apps were sunset (like a certain dev did earlier this year to one of the best DAW apps on iOS 😒). If the legacy versions continue to function fine in my projects, no need for me to be upset. And if I want to upgrade to the next OS and still need KQ's apps, I can repurchase the apps for dirt cheap with the upgrade bundle. That's much better than losing the apps forever.

    And yes, paying for a future update here and there isn't the end of the world. KQ's top-quality apps are definitely worth repurchasing. So if his apps mean that much to you and you want to save a few quid when repurchasing, just wait for the bundles to be available (if they aren't available already, maybe I missed something whilst skimming this thread).

    Also for the record, I'm not sure what "scenes" are either, but SDK means "software development kit", which is something developers use to make their apps afaik. I could be wrong. It's almost 5am here, and I should be getting my sorry arse back to bed. 😂

  • @vlaoladis said:
    Lol my bundle price is higher than the price of the new version alone

    Same here and I checked the price I originally paid, it was 9.99€. I’m not sure what’s going on

  • Woah. Brain is fried trying to understand all this.
    What if I just don’t update Dixie and keep using the version I’ve got on my iPad? Is that an option?

  • @Kashi said:
    Woah. Brain is fried trying to understand all this.
    What if I just don’t update Dixie and keep using the version I’ve got on my iPad? Is that an option?

    My brain is fried too, but from what I can gather, so long as you don't update to iPadOS 27, yes you can use the version you got. If I'm off, someone will correct. :)

  • @branis said:

    @vlaoladis said:
    Lol my bundle price is higher than the price of the new version alone

    Same here and I checked the price I originally paid, it was 9.99€. I’m not sure what’s going on

    Yes, even if you bought it at a discount, the bundle currently acts as if someone initially paid YOU to buy the old version, which is definitely not the case. :smile:

    So I don't understand where is this "dirt cheap upgrade" for old buyers

  • @vlaoladis said:

    @branis said:

    @vlaoladis said:
    Lol my bundle price is higher than the price of the new version alone

    Same here and I checked the price I originally paid, it was 9.99€. I’m not sure what’s going on

    Yes, even if you bought it at a discount, the bundle currently acts as if someone initially paid YOU to buy the old version, which is definitely not the case. :smile:

    So I don't understand where is this "dirt cheap upgrade" for old buyers

    It seems to be working for the US AppStore. Maybe some regional setting is missing for Europe

  • edited October 2025

    @branis said:

    @vlaoladis said:
    Lol my bundle price is higher than the price of the new version alone

    Same here and I checked the price I originally paid, it was 9.99€. I’m not sure what’s going on

    Sometimes you need to do something for the bundle price to update correctly. Maybe scroll down and back up, switch to another app and back, etc. Notice that it does not say "Complete My Bundle", so it has not yet correlated it with your original purchase. This is a tradition for AppStore bundles.

  • @uncledave said:

    @branis said:

    @vlaoladis said:
    Lol my bundle price is higher than the price of the new version alone

    Same here and I checked the price I originally paid, it was 9.99€. I’m not sure what’s going on

    Sometimes you need to do something for the bundle price to update correctly. Maybe scroll down and back up, switch to another app and back, etc. Notice that it does not say "Complete my bundle", so it has not yet correlated it with your original purchase. This is a tradition for AppStore bundles.

    Thank you. I tried to scroll, swipe and even restarted appstore several times, but it didn't help

  • @vlaoladis said:
    Lol my bundle price is higher than the price of the new version alone

    Could you please contact Apple Support?
    The price depends on your account so I cannot support.

  • edited October 2025

    @branis said:

    @vlaoladis said:
    Lol my bundle price is higher than the price of the new version alone

    Same here and I checked the price I originally paid, it was 9.99€. I’m not sure what’s going on

    @vlaoladis @branis
    Could you confirm the purchase history (except emails)?
    Do you use the exactly same account, not family one?
    Could you contact Apple?

  • @jwmmakerofmusic said:

    @Kashi said:
    Woah. Brain is fried trying to understand all this.
    What if I just don’t update Dixie and keep using the version I’ve got on my iPad? Is that an option?

    My brain is fried too, but from what I can gather, so long as you don't update to iPadOS 27, yes you can use the version you got. If I'm off, someone will correct. :)

    Cool. Thanks man

  • @Kashi said:

    @jwmmakerofmusic said:

    @Kashi said:
    Woah. Brain is fried trying to understand all this.
    What if I just don’t update Dixie and keep using the version I’ve got on my iPad? Is that an option?

    My brain is fried too, but from what I can gather, so long as you don't update to iPadOS 27, yes you can use the version you got. If I'm off, someone will correct. :)

    Cool. Thanks man

    Cheers! 🍻

  • @jwmmakerofmusic said:
    @Fear2Stop Hey mate. Just wanted to put things into context. I would be more upset if KQ's apps were sunset (like a certain dev did earlier this year to one of the best DAW apps on iOS 😒). If the legacy versions continue to function fine in my projects, no need for me to be upset. And if I want to upgrade to the next OS and still need KQ's apps, I can repurchase the apps for dirt cheap with the upgrade bundle. That's much better than losing the apps forever.

    And yes, paying for a future update here and there isn't the end of the world. KQ's top-quality apps are definitely worth repurchasing. So if his apps mean that much to you and you want to save a few quid when repurchasing, just wait for the bundles to be available (if they aren't available already, maybe I missed something whilst skimming this thread).

    Also for the record, I'm not sure what "scenes" are either, but SDK means "software development kit", which is something developers use to make their apps afaik. I could be wrong. It's almost 5am here, and I should be getting my sorry arse back to bed. 😂

    Okay now for part two of my ignorance …I thought them being deprecated was the same as being sunset ! Didn’t realize it was still going to work! I use Dixie a hell of a lot and I have anger for how many of my projects got broken with the Audiobus Pty calamity , and thought that was gonna happen again

  • The bundle is more expensive to me than the new app. Too expensive for brazil too 😞

  • @Fear2Stop said:

    @jwmmakerofmusic said:
    @Fear2Stop Hey mate. Just wanted to put things into context. I would be more upset if KQ's apps were sunset (like a certain dev did earlier this year to one of the best DAW apps on iOS 😒). If the legacy versions continue to function fine in my projects, no need for me to be upset. And if I want to upgrade to the next OS and still need KQ's apps, I can repurchase the apps for dirt cheap with the upgrade bundle. That's much better than losing the apps forever.

    And yes, paying for a future update here and there isn't the end of the world. KQ's top-quality apps are definitely worth repurchasing. So if his apps mean that much to you and you want to save a few quid when repurchasing, just wait for the bundles to be available (if they aren't available already, maybe I missed something whilst skimming this thread).

    Also for the record, I'm not sure what "scenes" are either, but SDK means "software development kit", which is something developers use to make their apps afaik. I could be wrong. It's almost 5am here, and I should be getting my sorry arse back to bed. 😂

    Okay now for part two of my ignorance …I thought them being deprecated was the same as being sunset ! Didn’t realize it was still going to work! I use Dixie a hell of a lot and I have anger for how many of my projects got broken with the Audiobus Pty calamity , and thought that was gonna happen again

    Deprecated isn't the same as being sunset. And luckily for us, @RyoutaKira is making sure his amazing plugins remain in the Appstore by future-proofing them. I don't mind paying again for those apps.

    I think when it comes to our projects on iOS, the best thing to do is to make sure you have your unmastered tracks backed up to storage (whether an external harddrive, cloud storage, etc). That way you can access them all again in the future in case you want to make an EP/Album out of a selection of said apps. :) Hope this helps.

Sign In or Register to comment.