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.
Email from Imaginando Regarding Cloud Sync (Feb. 2024)
Got this email from Imaginando this morning:
Hi everyone,
As we start the 10th year of Imaginando’s journey and look to grow while still delivering the same level of high-quality products and updates, we need to reevaluate the services we offer.
As a result, we have decided to retire/remove the Cloud Sync functionality from all of our apps by the end of 2024.
We will issue full details about the process and schedule of the transition away from Cloud Sync/storage in due course; we just wanted to make Cloud Sync users aware of the changes and explain the reasoning behind the decision.
Why are we doing this?
The primary reason is the cost and maintenance of the required server infrastructure. As our product and user base grows, the additional financial impact makes Cloud Sync an unsustainable service for the future.
Removing Cloud Sync from our apps will also help streamline the maintenance of the apps themselves, allowing us to concentrate our efforts on other improvements and updates going forward.
With the rise of third-party cloud storage services such as Google Drive and iCloud now integrated into both desktop and mobile OS, we believe the smart move is to invest our resources into improving project/patch management across all apps.
What about sharing patches/projects in the future?
By improving file-based import/export functionality, we believe that we can provide greater flexibility for users to choose how to store, backup and transfer the content they create inside our apps.
What happens now?
There will be no immediate changes to the Cloud Sync service yet, the removal process will be gradual, and we will share further details when available.
For account queries, help or support, you can get in touch via our website contact page.
Best regards,
Team Imaginando
Comments
I got the same email and I can fully understand their point. Why reinvent the wheel and maintain another cloud service, when there are already plenty to choose from? And much better than introducing a subscription model just to cover the costs for the infrastructure.
We have so many other options. I am fine with the change.
Honestly, I have no idea why they didn’t leverage iCloud from the start. There would be no more re-logging in to their apps every time I use them if the license info was kept on-device or in icloud.
Since they target OSes other than apple ones. If you only have apple apps it makes sense to do it on cloud of course.
From the email I get the sense they would have some platform agnostic cloud code (speculation on my part, but possibly on top of AWS or similar, and man… do those costs add up after a while), which is now becoming to expensive to maintain.
I cannot fault them from going that route before, nor taking this new decision now.
That’s a fine theory, except they had already sunk dev costs into iPadOS development (after all, they sell through the App Store).
At least they didn’t mention ‘subscription’.
Yep.
Right, so they had two options back then (generally speaking): develop some code based on an external cloud provider which runs more or less the same on iPad , macOS, windows and android. Or do one for mac/ios based on iCloud, one for android based probably on firebase and one for windows probably on top of onedrive, which would multiply the development time and costs. Since UI and network code can be separated there is no sunk cost here.
My guess is they went for option one.
Good reasons and, more importantly, great way of communicating with their users.
It's a good choice of fat to cut. This user won't have an issue with it and if it helps them financially it's a win win, or not lose win.
My only complaint is the vagueness of this title thread ,
@NeuM is usually more precise in all their contributions .
“re: Cloud Sync ending “ would be useful addition to title .
I mean I’m usually spammed once or twice a week by Imaginando, if I started a thread every time for that…
Good suggestion. Updated.