# iOS AUv3 version of examples /PluginSamples/Arpeggiator

**URL:** <https://forum.juce.com/t/ios-auv3-version-of-examples-pluginsamples-arpeggiator/24593>\
**Category:** General JUCE discussion\
**Created:** [October 11, 2017, 12:06am UTC](https://forum.juce.com/t/ios-auv3-version-of-examples-pluginsamples-arpeggiator/24593 "2017-10-11T00:06:28Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![dstenning](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/dstenning/32/2686_2.png) [@dstenning](https://forum.juce.com/u/dstenning)\
**Post date:** [October 25, 2017, 5:48pm UTC](https://forum.juce.com/t/ios-auv3-version-of-examples-pluginsamples-arpeggiator/24593/14 "2017-10-25T17:48:55Z")

</div>

Doesnt all this issue - and the basic fact that Apple has dragged its heels for over a decade about properly supporting AudioUnits on iOS - suggest that it really might be worth ROLI reconsidering its position of only supporting Apple official API’s in the JUCE Framework?

AudioBus - clearly even now - is way in front of what AUv3 can deliver. And there’s the non-apple API Ableton-Link as well - firmly established in the iOS music-making world - and elsewhere too.

So surely - bearing in mind JUCE is intended for AUDIO software developers - surely - it makes sense - and helps us developers - if ROLI’s JUCE team put work into supporting both AudioBus3 and Ableton-Link now ?

Better to support the leading-edge of what is now possible on the leading platforms instead of Apple’s trailing-edge - reminiscent of the “Please sir” scene in Oliver Twist!

---

_[View the full topic](https://forum.juce.com/t/ios-auv3-version-of-examples-pluginsamples-arpeggiator/24593)._
