Apple, iOS, and the need for third-party innovation

A main use of my iPad is creating music. In my experience, iOS has provided a convenient and relatively low-cost way to explore and experiment with music synthesis, sampling, looping, audio processing, programming, sound design, production and dissemination of my semi-amateur home-studio recordings. The numerous developers involved in creating music-related apps have produced some of the most innovative products available.

At times, these developers have pushed the envelope when it comes to app design, functionality and interoperability. Even though many of these developers are involved with the design and production of hardware instruments and technology, and writing software for laptop and desktop computers, they also recognise that the iPad offered another way to interface with digital music tools. In some cases, iPad apps can connect to or interact with their hardware and software counterparts (e.g., touchAble).

Elsewhere, developer vision has pre-empted and even overtaken Apple’s own product design. A good example is IAA (Inter-App Audio), introduced by Apple in 2013. While some app developers were quick to adopt this feature into their own products, in the same year the team at Audiobus took this functionality to another level, with a fully integrated platform within iOS that allows multiple apps to be connected virtually. Eventually, in 2019, Apple countered by upgrading their own Audio Unit (AU) infrastructure that introduced another way to connect separate apps.

There remain some anomalies in Apple’s approach to competing music apps and their commercial models. Although Apple has enabled developers to offer in-app purchases and upgrades, it is noticeable that to this day, Bandcamp does not sell digital music via its mobile app (thought to be due to Apple’s hefty sales commission on digital content?); but Bandcamp customers can purchase physical goods via the app. While over on the SoundCloud app, users can purchase in-app subscriptions offering ad-free streaming and off-line content, but Spotify customers cannot purchase similar premium streaming services within the corresponding app.

The latest move from Apple has got some developers quite excited. As well as bringing its professional video editing suite, Final Cut Pro, to iPad, Apple has launched an iPad version of Logic Pro, its professional music DAW (Digital Audio Workstation). Now, I don’t have a problem with this, and I can see the attraction for both app developers and Logic Pro users.

I myself use Ableton Live (and not Logic Pro or Apple’s consumer-level product, GarageBand), so I am not planning to add another desktop DAW. Besides, Ableton enables third party developers to integrate their AU and VST plug-ins on Mac. In addition, Ableton has launched a mobile app, Ableton Note, that can interact with the desktop program, which just confirms the co-existence of these platforms, and user preference for interoperability.

My concern is that with the introduction of Logic Pro on iOS, Apple may close off some inter-app functionality to third party apps if they do not support integration with Logic Pro. We’ve seen the way Apple can shut down external innovation: without getting too technical, until 2021, and with a little effort, users could run iOS music apps on their Macs, and within DAWs such as Ableton. Apple then closed off that option, but more recently has enabled iOS-derived AUv3 plugins to run on M1 chip-enabled Macs.

Hopefully, Apple recognises that an open ecosystem encourages innovation and keeps people interested in their own products, as well as those from third-party developers.

Next week: Crown Court TV

No-code product development

Anyone familiar with product development should recognise the image below. It’s a schematic for a start-up idea I was working on several years ago – for an employee engagement, reward and recognition app. It was the result of a number of workshops with a digital agency covering problem statements, user scenarios, workflow solutions, personas, UX/UI design and back-end architecture frameworks.

At the time, the cost quoted to build the MVP was easily 5-6 figures – and even to get to that point still required a load of work on story boards, wire frames and clickable prototypes….

Now, I would expect the developers to use something like a combination of open-source and low-cost software applications to manage the middle-ware functions, dial-up a basic cloud server to host the database and connect to external APIs, and commission a web designer to build a dedicated front-end. (I’m not a developer, programmer or coder, so apologies for any glaring errors in my assumptions…)

The growth in self-serve SaaS platforms, public APIs and low-cost hosting solutions (plus the plethora of design marketplaces) should mean that a developer can build an MVP for a tenth of the cost we were quoted.

Hence the interest in “low-code/no-code” product development, and the use of modular components or stack to build a range of repetitive, automated and small scale applications. (For a dev’s perspective check out Martin Slaney’s article, and for a list of useful resources see Ellen Merryweather’s post from earlier this year.)

There are obvious limitations to this approach: anything too complex, too custom, or which needs to scale quickly may break the model. Equally, stringing together a set of black boxes/off-the-shelf solutions might not work, if there are unforeseen incompatibilities or programming conflicts – especially if one component is upgraded, and there are unknown inter-dependencies that impact the other links in the chain. Which means the product development process will need to ensure a layer of code audits and test environments before deploying into production.

I was reflecting on the benefits and challenges of hermetically sealed operating systems and software programs over the weekend. In trying to downgrade my operating system (so that I could run some legacy third-party applications that no longer work thanks to some recent systems and software “upgrades”), I encountered various challenges, and it took several attempts and a couple of workarounds. The biggest problem was the lack of anything to guide me in advance – that by making certain changes to the system settings, or configuring the software a certain way, either this app or that function wouldn’t work. Also, because each component (the operating system, the software program and the third party applications) wants to defend its own turf within my device, they don’t always play nicely together in a way that the end user wants to deploy them in a single environment.

App interoperability is something that continues to frustrate when it comes to so-called systems or software upgrades. It feels like there needs to be a specialist area of product development that can better identify, mitigate and resolve potential tech debt, as well as navigate the product development maintenance schedule in anticipation of future upgrades and their likely impact, or understand the opportunities for retrofitting and keeping legacy apps current. I see too many app developers abandoning their projects because it’s just too hard to reconfigure for the latest system changes.

Next week: Telstar!

 

 

 

The Maker Culture

London’s newly re-opened Design Museum welcomes visitors with a bold defining statement of intent. According to the curators, there are only designers, makers and users. To me, this speaks volumes about how the “makers” are now at the forefront of economic activity, and how they are challenging key post-industrial notions of mass-production, mass-consumption and even mass-employment. Above all, as users, we are becoming far more engaged with why, how and where something is designed, made and distributed. And as consumers we are being encouraged to think about and take some responsibility for our choices in terms of environmental impact and sustainability.

Design Museum, London (Photo: Rory Manchee)

Design Museum, London (Photo: Rory Manchee)

There are several social, economic, technological and environmental movements that have helped to define “maker culture”, so there isn’t really a single, neat theory sitting behind it all. Here is a (highly selective) list of the key elements that have directly or indirectly contributed to this trend:

Hacking – this is not about cracking network security systems, but about learning how to make fixes when things that don’t work the way that we want them to, or for creating new solutions to existing problems – see also “life hacks”, hackathons or something like BBC’s Big Life Fix. Sort of “necessity is the mother of invention”.

Open source – providing easier access to coding tools, software programs, computing components and data sources has helped to reduce setup costs for new businesses and tech startups, and deconstructed/demystified traditional development processes. Encompasses everything from Linux to Arduino; from Github to public APIs; from AI bots to widget libraries; from Touch Board to F.A.T. Lab; from SaaS to small-scale 3-D printers.

Getting Sh*t Done – from the Fitzroy Academy, to Andrea de Chirico’s SUPERLOCAL projects, maker culture can be characterised by those who want: to make things happen; to make a difference; to create (social) impact; to get their hands dirty; to connect with the materials, people, communities and cultures they work with; to disrupt the status quo; to embrace DIY solutions; to learn by doing.

The Etsy Effect – just part of the response to a widespread consumer demand for personalised, customised, hand-made, individual, artisan, crafted, unique and bespoke products. In turn, platforms like the Etsy and Craftsy market places have sparked a whole raft of self-help video guides and online tutorials, where people can not only learn new skills to make things, they can also learn how to patch, repair, re-use, recycle and re-purpose. Also loosely linked to the recent publishing phenomena for new magazines that combine lifestyle, new age culture, philosophy, sustainability, mindfulness, and entrepreneurism with a social conscience.

Startups, Meetups and Co-working Spaces – if the data is to be believed, more and more people want to start their own ventures rather than find employment with an existing organisation. (Under the gig economy, around 40% of the workforce will be self-employed, freelance or contractors within 5 years, so naturally people are having to consider their employment options more carefully.) While starting your own business is not for everyone, the expanding ecosystem of meetups and co-working spaces is enabling would-be entrepreneurs to experiment and explore what’s possible, and to network with like-minded people.

Maker Spaces – also known as fabrication labs (“FabLabs”), they offer direct access to tools and equipment, mostly for things like 3-D printing, laser-cutting and circuit-board assembly, but some commercial facilities have the capacity to support new product prototyping, test manufacturing processes or short-run production lines. (I see this  interface between “cottage industry” digital studios and full-blown production plants as being critical to the development of high-end, niche and specialist engineering and manufacturing services to replace the declining, traditional manufacturing sectors.) Some of the activity is formed around local communities of independent makers, some offer shared workshop spaces and resources. Elsewhere, they are also run as innovation hubs and learning labs.

Analogue Warmth – I’ve written before about my appreciation for all things analogue, and the increased sales of vinyl records and even music cassettes demonstrate that among audiophiles, digital is not always better, that there is something to be said for the tangible format. This preference for analogue, combined with a love of tactile objects and a spirit of DIY has probably reached its apotheosis (in photography at least) through Kelli Anderson’s “This Book Is A Camera”.

Finally, a positive knock-on effect of maker culture is the growing number of educational resources for learning coding, computing, maths and robotics: Raspberry PI, Kano and Tech Will Save Us; KidsLogic, Creative Coding HK and Machinam; Robogals, Techcamp and robokids. We can all understand the importance of learning these skills as part of a well-rounded education, because as Mark Pascall, founder of 3months.com, recently commented:

“I’m not going to advise my kids to embark on careers that have long expensive training programs (e.g. doctors/lawyer etc). AI is already starting to give better results.”

Better to learn how things work, how to design and make them, how to repair them etc., so that we have core skills that can adapt as technology changes.

Next week: Life Lessons from the Techstars founders

 

“Language is a virus” – a look at coding skills

We are fast-approaching the point when a lack of some basic coding skills will be likened to being illiterate. If you are unable to modify a web page or use an HTML text editor, it will be like not knowing how to create a Word document or edit a PDF file. Coding does appear on some school curricula, but it is primarily taught in the context of maths, computer programming or IT skills. Whereas, if we look at coding as a language capability (part of a new literacy), it should be seen as an essential communication tool in itself.

quote-William-S.-Burroughs-language-is-a-virus-from-outer-space-92713First, I am aware that a number of programs for children are trying to teach coding and maths in more relevant ways, and having talked to some of their creators, I admire their ambition to place these skills in a broader context. Coding might be described as the “4th R”: alongside reading, writing, arithmetic we have reasoning”. So a program like Creative Coding HK (as it name implies) focuses on students making things; in the USA, KidsLogic is placing as much emphasis on contextual learning as on robotics; while Australia’s Machinam is re-writing the maths curriculum to teach practical, everyday problem-solving skills.

Second, as we know, learning the foundations of coding is like learning the syntax of a foreign language. However, while Latin and Greek can provide the basis for learning the structure (and many words) of many European languages, it’s not much use when learning character-based languages (Chinese, Japanese) – although there are common grammatical elements. But if we understand that a line of any code has to be structured a certain way, contain essential elements, define key attributes and run in a particular sequence or order, we may come to “read” and interpret what the code is saying or doing.

As an aside, I’m struck by the comments made by the founder of AssignmentHero during a recent pitch night. Although he had studied computer sciences at Uni, he did not use any of the formal computing languages he had learned when building his product. This highlights the downside of learning specific languages, which can become obsolete, unless we have a better grasp of “which languages for which purposes”, or find ways to easily “interpolate” components of one language into another (just as languages themselves borrow from each other). Or do we need an Esperanto for coding?

Third, even if I don’t want or need to learn how to program a computer or configure an operating system, knowing how to define and sequence a set of instructions for running some software or a dedicated program will be essential as more devices become connected in the Internet of Things. For myself, I have dabbled with a simple bluetooth enabled robot (with the original Sphero), acquired a WiFi-enabled light bulb (the programmable LIFX) and experimented with an iOS music app that incorporates wearables (the MIDI-powered Auug motion synth).

Finally, just like a virus, coding is contagious – but in a good way. At a recent event on Code in the Cinema (hosted by General Assembly as part of the Melbourne International Film Festival), there were three demos which captured my attention, and which I will be investigating over the coming months:

I think they show why, where and how many of us “non-computing” types will want to learn the benefits of coding as a new language skill. If nothing else, getting comfortable with coding will help mitigate some of the risks of the “digital divide”.

Next week: The arts for art’s sake….