AUM - Many thanks to j_liljedahl / Kymatica

jwmmakerofmusic

@Gavinski said:

@Iskander said:
At the moment there is a lot of hype about STAGE MANAGER and everyone on the web is excited that something like this will (finally) be available soon.

Many outside of our community are not aware that many of these features and more already exist in AUM for many years like moveable and resizeable windows.

Big compliments to @j_liljedahl who worked his magic here. He showed early on what is feasible.

Having worked in software development for over 40 years myself, I can well appreciate what my colleague has created here. And that with an app size of around 6 MB. Always admirable for me.

He has already realized a long time ago, what other iPad or IPhone users had dreamed of so far (with iPhone it will probably stay that way for the time being). STAGE MANAGER will probably only run on M1 iPads for the time being.
AUM on the other hand will run on ALL DEVICES.

Many thanks again @j_liljedahl for a fabulous and admirable app, which offers so many functions, as hardly any other app. I am always thrilled with every (almost daily) use and discover more and more possibilities.

For us music creators, AUM is indispensable.

Amen! AUM has completely shaped the way I do music on iOS. Brilliant app with constant updates. It just gets better and better, yet we have never even had to pay for an upgrade. Big thanks @j_liljedahl

Exactly! Before I dove into live Ambient, I didn't know how I could ever fit AUM into my workflow. But now it has become an indispensable masterpiece of software that I absolutely cannot live without! Okay, sure, Gadget is still my main go-to for producing EDM (if I ever go back to producing EDM for myself that is), but once audio tracks and automation are added into AUM as @j_liljedahl mentioned above, AUM will probably be the only environment I'll ever produce anything in, period.

cuscolima

@wim said:

@cuscolima said:

@tja said:

@cuscolima said:

@cuscolima said:

@tja said:

@cuscolima said:

@wim said:

@cuscolima said:
IAP is, in my opinion, the best pricing strategy, at least for the end user. You pay once for what you really want. The "a la Loopy" strategy is probably more fair for the dev in term of incomes and planification but it can be very frustrating for the user. An exemple : I am still waiting for Beatsurfing's AU promised compatibility but so far, nothing can prove it will ever happen, even if you pay (in the future) for the upgrade subscription...

I think you've misunderstood Loopy Pro's model. You don't have to pay forward for updates that you may never see, or not see for some time. You can hold off paying after the 12 months. You'll still have the app as-is but you won't get further feature updates, only bug-fixes. When/If you feel like the newer features are worth it, you can pay the 12 month upgrade, and you'll get every update that has happened and that will happen for the next 12 months.

Thanks wim, I understand now. Let see how this model will evolve in the time.

[edit] All this has been discussed in many ways in other threads but I want to mention one big disadvantage of the Loopy model. This is a pure marketing principle : if you want to sell big, then you need a killer-feature. It means that a dev can decide to wait before publishing a new feature because he knows that this is the one that will convince the customers to buy the next 12 months. IAP is better as it can be immediately made available for purchase.

No.

The WorkingCopy / Wotja / Loopy Pro model is the best thing possible, for both customers and developers.

This is totally apparent as soon as you understand the model.

But right, I often see that people misunderstand something in this.

Just saying.

Ok if you say it…no more arguments requested

I still think that there are some unexpected « side effects » related to this model.

You get what you pay for, and you can use this for the rest of your live.
And as bonus, you get even all new features for a year and probably security updates for longer.
So, what is bad here?

ONLY when there is - at any time after that first year - a version that finally offers something that you really want, you can opt to buy it. Just like a major new version from any other software, and again this is yours for your live.

You never loose anything and, but your version will never fully deprecate like other software that has version 2, 3, 4 ... the older version will most likely never updated again for new OS versions or security.
But the WorkingCopy and Loopy Pro licensing will normally always update your bought version for OS and security, even if you never ever buy a new version again.

I really cannot see any "side effect" here!

It is the perfect model for both developers and customers: Customers only buy again, when there are good enough new features, while developers are motivated to deliver them!

Your thoughts?

Thanks for your arguments that are perfectly valid. I don’t say that this model is bad. I say I see a risk that key features will be delayed till the next 12 months period purely for marketing reasons. I prefer a dev releasing immediately the key feature as an IAP. Apps like Loopy Pro and AUM have a huge potential for evolution, so I think both model will be ok here. Some other apps are much more limited and in this case, I fear the few key features will be deliberately delayed…that’s my point of view

I don’t think you quite understand the model yet. There is no fixed 12 month schedule that is the same for everyone. It’s 12 months from the time each customer has bought the app. There’s no way that the developer could game the timing of the system in that way.

Ah, this is interesting and new to me. Ok let's hope this works as good as it's supposed to. I could ask Jonathan why he chooses not to but I don't want to disturb him with such down to earth topic !

[Deleted User]

The user and all related content has been deleted.

[Deleted User]

The user and all related content has been deleted.

anickt

Think we’ve gotten badly sidetracked from the OP….

[Deleted User]

The user and all related content has been deleted.