# Bram Bos online paper on AUv3 MIDI Plugins

**URL:** <https://forum.juce.com/t/bram-bos-online-paper-on-auv3-midi-plugins/26590>\
**Category:** MacOSX and iOS\
**Created:** [February 28, 2018, 1:03pm UTC](https://forum.juce.com/t/bram-bos-online-paper-on-auv3-midi-plugins/26590 "2018-02-28T13:03:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![fr810](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/fr810/32/841_2.png) [@fr810](https://forum.juce.com/u/fr810)\
**Post date:** [March 2, 2018, 11:42am UTC](https://forum.juce.com/t/bram-bos-online-paper-on-auv3-midi-plugins/26590/2 "2018-03-02T11:42:24Z")

</div>

Maybe it’s better to continue the discussion on this thread as it contains more information:

> [@iOS AUv3 version of examples /PluginSamples/Arpeggiator](https://forum.juce.com/t/ios-auv3-version-of-examples-pluginsamples-arpeggiator/24593/14):
>
> 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…

---

_[View the full topic](https://forum.juce.com/t/bram-bos-online-paper-on-auv3-midi-plugins/26590)._
