The value of standalone?

[Deleted User]

Wondering, how others value the option for standalone mode.
Sometimes I just want to jam with a single synth, full screen, no routing, especially when first buying it. Helps me concentrate and explore the app in its entirety.
Thoughts?

Tarekith

I pretty much ONLY use apps in standalone mode, I hate having to load up a separate app just to be able to use the one I want. Standalone, self-contained apps is why I like iOS music making. If I want to do hosting, complicated routing, or other things like that the laptop is vastly easier to do it with for me.

[Deleted User]

I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

gusgranite

@Tarekith said:
I pretty much ONLY use apps in standalone mode, I hate having to load up a separate app just to be able to use the one I want. Standalone, self-contained apps is why I like iOS music making. If I want to do hosting, complicated routing, or other things like that the laptop is vastly easier to do it with for me.

Interesting. I very rarely use an app standalone. How do you record the output? Do you still sync with other apps? Or just use all in one apps?

[Deleted User]

Standalone to the point of buying hardware for it and let iOS just for one or two monolithyc apps like Blocs or garageband (with defaults no AU hosting)

[Deleted User]

Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

gusgranite

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

[Deleted User]

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

u0421793

? It did it twice. See next post.

u0421793

">

Tarekith

@gusgranite said:

How do you record the output? Do you still sync with other apps? Or just use all in one apps?

Most of the apps I use are groovebox or pattern based, and most let me export my work in Live format or as stems to work on back in the studio. If I'm using a synth app on the iPad and need to record it for a song, I just do it digitally over the lightening cable via MacOS Audio MIDI preferences.

I don't sync with other apps, mostly because I try and avoid having to jump back and forth between apps when working on iOS devices. I still find it a very clunky workflow myself, so I prefer all in one apps like Groovebox, Gadget, KEW, etc.

reasOne

Stand alone is cool to jam live or if recording out to an external source, but deff prefer au over it, because au can do all the same functions and more

[Deleted User]

Also AU apps can be multiple apps as shown by Rozeta and ApeMatrix, so many apps could have midi controller parts and sound parts seperate but still sold together.

realdawei

@Tarekith said:

@gusgranite said:

How do you record the output? Do you still sync with other apps? Or just use all in one apps?

Most of the apps I use are groovebox or pattern based, and most let me export my work in Live format or as stems to work on back in the studio. If I'm using a synth app on the iPad and need to record it for a song, I just do it digitally over the lightening cable via MacOS Audio MIDI preferences.

I don't sync with other apps, mostly because I try and avoid having to jump back and forth between apps when working on iOS devices. I still find it a very clunky workflow myself, so I prefer all in one apps like Groovebox, Gadget, KEW, etc.

Well that would explain the difference in perspective. Some of us enjoy doing the whole creative shebang on the iOS device. In this regard I find AUv3 much less clunky

gusgranite

Cheers @Tarekith. I always like the sounds you share.

Carnbot

Standalone can be very useful for iOS in multiple device setups too. Sequencers to hardware/desktop. iOS to iOS. FX routing. The great thing about iOS is it's potential flexibility over desktop setups, it's ideal in having more than one device. So if you're treating the device as a piece of hardware with a single purpose (it's original design) it makes sense..

But when connecting multiple apps together it's AUv3 all the way
Standalone also works best for iPhone too imo.

gusgranite

As SugarBytes have shown, we can now have our cake and eat it! A stand-alone app that is also AU.

Hurrah!

AndyPlankton

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

[Deleted User]

@AndyPlankton said:

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

I doubt memory restrictions are the reason the apps I mentioned are unable to go AU. Having a host is not really a problem with the low footprint hosts we have on iOS.

gusgranite

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

I doubt memory restrictions are the reason the apps I mentioned are unable to go AU. Having a host is not really a problem with the low footprint hosts we have on iOS.

Isn’t this all a moot point now though? Run an app standalone if you prefer that workflow, or run it as an AU in a host. Developers can now please everybody! (Well, almost. Lol).

[Deleted User]

@gusgranite said:

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

I doubt memory restrictions are the reason the apps I mentioned are unable to go AU. Having a host is not really a problem with the low footprint hosts we have on iOS.

Isn’t this all a moot point now though? Run an app standalone if you prefer that workflow, or run it as an AU in a host. Developers can now please everybody! (Well, almost. Lol).

Yeah sure we will see how well AU itself and the development community, ehem ‘develops’ lol

DMan

As AUv3, so many apps do not scale well, may not go full screen at all, don’t have preset systems that follow to every host, and sometimes full screen is just nice. I like to make patches in the standalone for the majority of apps. Once I get a sound I want then I go AU with it. Some developers get it right in AUv3 in the first place and the experience is similar to standalone.

kobamoto

@Tarekith said:
I pretty much ONLY use apps in standalone mode, I hate having to load up a separate app just to be able to use the one I want. Standalone, self-contained apps is why I like iOS music making. If I want to do hosting, complicated routing, or other things like that the laptop is vastly easier to do it with for me.

+100000000000000000000000

AndyPlankton

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

I doubt memory restrictions are the reason the apps I mentioned are unable to go AU. Having a host is not really a problem with the low footprint hosts we have on iOS.

Having a host is not a problem for those of us lucky enough to already own one, but for a first timer, having to buy an app AND a host in order to use it may be a deal breaker, you would have to buy the host first, and a host with no Au's is useless !
I still prefer firing up apps stand alone and only using a host when I need to for FX routing or recording etc...

[Deleted User]

@AndyPlankton said:

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

I doubt memory restrictions are the reason the apps I mentioned are unable to go AU. Having a host is not really a problem with the low footprint hosts we have on iOS.

Having a host is not a problem for those of us lucky enough to already own one, but for a first timer, having to buy an app AND a host in order to use it may be a deal breaker, you would have to buy the host first, and a host with no Au's is useless !
I still prefer firing up apps stand alone and only using a host when I need to for FX routing or recording etc...

Don’t Apple already give a half decent host away for free? You could say the same for PC / Mac. Yeah devs can always make an app standalone and include AU extensions, I don’t see it as a reason not to include AU extensions. Personally I would still prefer tighter AU integration and better hosts. Stand alone can still be a simplified IAA host included in the app if the dev thinks it’s needed.

AndyPlankton

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

I doubt memory restrictions are the reason the apps I mentioned are unable to go AU. Having a host is not really a problem with the low footprint hosts we have on iOS.

Having a host is not a problem for those of us lucky enough to already own one, but for a first timer, having to buy an app AND a host in order to use it may be a deal breaker, you would have to buy the host first, and a host with no Au's is useless !
I still prefer firing up apps stand alone and only using a host when I need to for FX routing or recording etc...

Don’t Apple already give a half decent host away for free? You could say the same for PC / Mac. Yeah devs can always make an app standalone and include AU extensions, I don’t see it as a reason not to include AU extensions. Personally I would still prefer tighter AU integration and better hosts. Stand alone can still be a simplified IAA host included in the app if the dev thinks it’s needed.

I'm not saying don't do AU, I am saying don't drop stand alone, the title of the thread implies no need for stand alone any more.

[Deleted User]

@AndyPlankton said:

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@AndyPlankton said:

@Fruitbat1919 said:

@gusgranite said:

@breilly said:
Yeah that full screen is much appreciated; thats the only pro that i see to loading an app via iaa rather than au. Not a fan of swiping and sliding to see the various parameters an app offers, it kinda affects my thought process.

@Fruitbat1919 said:
I would gladly give up any standalone mode if it meant better integration with hosts. I often open up apps and just use them, but once I get something going I want to expand on that.

At this time, iOS apps don’t integrate seamlessly or with little hassle. Often things just go wrong and that great work becomes a nightmare to become part of something greater.

So while I understand why people like using apps in standalone sometimes, I would much prefer that full screen app feeling within a host, so it is ready willing and able to play nice the minute I hit gold with my tinkering.

It’s pretty close though, isn’t it?

Eg. Here’s Egoist standalone:

And here’s the AU:

Yeah that’s the rub now. AU full screen is pretty much the same as IAA, so why are people still releasing any apps as non AU? There has to be a reason, even if it’s just plain not wanting to learn the new skills to do AU. Would love a dev here to tell me that Patterning or iBassist etc etc would not be possible in AU form.

Don’t get me wrong I love some apps enough to buy them still as IAA, but really I don’t want to keep having to try to make apps work together. Surely AU is more than just synths and cut down drum apps?

The app shown above makes me think AU is already quite capable and it may just be if the devs really want to move in that direction

AU memory restrictions
Having to use a host in order to run the app

Just two biggies that spring to mind

I doubt memory restrictions are the reason the apps I mentioned are unable to go AU. Having a host is not really a problem with the low footprint hosts we have on iOS.

Having a host is not a problem for those of us lucky enough to already own one, but for a first timer, having to buy an app AND a host in order to use it may be a deal breaker, you would have to buy the host first, and a host with no Au's is useless !
I still prefer firing up apps stand alone and only using a host when I need to for FX routing or recording etc...

Don’t Apple already give a half decent host away for free? You could say the same for PC / Mac. Yeah devs can always make an app standalone and include AU extensions, I don’t see it as a reason not to include AU extensions. Personally I would still prefer tighter AU integration and better hosts. Stand alone can still be a simplified IAA host included in the app if the dev thinks it’s needed.

I'm not saying don't do AU, I am saying don't drop stand alone, the title of the thread implies no need for stand alone any more.

Yes I understand that. I just said that personally I would drop it in a second if it would help devs integrate their apps with hosts and DAWs better.

brambos

While we're discussing the value of standalone, can we also discuss the cost of standalone?

[Deleted User]

+1....it def seems certain apps scale so much better in au than others making it a more pleasurabe or unpleasurabe experience. Obviously pending the type of app; most effects and smaller instrument apps seem to scale beautifully, those larger synth apps not so much. Brambos nails the au design 👍🏼
Others involve to much scrolling and resizing which can kill your groove.
Its these apps that standalone remains much appreciated.....or a rescaling design for au which is well out of my expertise 😆

@DMan said:
As AUv3, so many apps do not scale well, may not go full screen at all, don’t have preset systems that follow to every host, and sometimes full screen is just nice. I like to make patches in the standalone for the majority of apps. Once I get a sound I want then I go AU with it. Some developers get it right in AUv3 in the first place and the experience is similar to standalone.

kinkujin

@brambos said:
While we're discussing the value of standalone, can we also discuss the cost of standalone?

Yes, let us. Not being a developer, I have no clue of the associated costs of doing both. Although is it a safe assumption that there are at least some costs with putting out a standalone as well as an au? If so, a dev could offer a synth in au format and then do an IAP for those of us interested in the standalone or iaa format. I’d pay the extra in at least some cases. Thoughts?

AndyPlankton

@kinkujin said:

@brambos said:
While we're discussing the value of standalone, can we also discuss the cost of standalone?

Yes, let us. Not being a developer, I have no clue of the associated costs of doing both. Although is it a safe assumption that there are at least some costs with putting out a standalone as well as an au? If so, a dev could offer a synth in au format and then do an IAP for those of us interested in the standalone or iaa format. I’d pay the extra in at least some cases. Thoughts?

No @brambos you can't, you HAVE to get back to work on bringing us NOIR....
hehehe

Are you referring to the cost of doing standalone, or cost of doing both AU and standalone ? Time is needed for both, you need one or the other to have an app in the first place, do you mean additional cost for doing both ? Or is it significantly harder to do stand alone that it is to do AU ?