2023-06-18 13:30:00
If you own a pair of AirPods, have a Mac, and have followed the Apple world for a while, you’ve probably heard of the AirBuddy — utility that makes the integration between Apple headphones and macOS much smoother and similar to that of iOS (and which is already in its second version).
What some people might not know is that this app, originally released in 2019, is made by a Brazilian developer: William Rambo. In addition to working as a developer, he is also part of the gigahertz — an independent technology-focused podcast network known for, among other shows, the Transfer area.
After talking to us in one of the first episodes of the segment “MM Interview”, in our YouTube channel — when he explained a little about his origins in the Apple world and, mainly, how spelunker —, Rambo agreed to talk this time about his routine as a developer and the challenges of keeping one of the most popular apps for Mac up and running.
Good reading! ????
What was your impetus to start working on AirBuddy? When exactly did this happen?
The word “impulse” defines it very well indeed, as I actually started AirBuddy completely on impulse. I started development in mid-January 2019. It had been bothering me for a long time that macOS didn’t integrate with AirPods as neatly as iOS does.
At the time, I was working at an e-commerce company and would occasionally stay after hours tinkering with app prototypes or testing random things. It was on one of those after-hours journeys that I decided to create a very simple prototype of what the AirPods status window on the Mac would look like. The goal that day was to be able to open the AirPods case next to the Mac and see a window showing battery levels, much like it was on iOS (and still is today).
I had previously explored how AirPods work and how they communicate with other devices, so that research and reverse engineering part was already done, leaving today the job of integrating it into something that looked like an app. Before long, I already had a working prototype. I showed it to some friends, posted a video demonstration to my Twitter and went home.
The next day, my Twitter was flooded with positive responses from people very interested in having something like that on the Mac; it was then that I decided to turn that prototype into a product. I initially thought about doing it as an open source project, but I realized that it would probably be a long-term commercial project, so I ended up choosing to keep it closed.
What’s the hardest part of maintaining an app like AirBuddy?
Every app requires maintenance — some more, some less. Most apps require greater attention when there are major updates to operating systems, such as macOS in the case of AirBuddy, to ensure that everything still works as expected, as internal system changes can cause application bugs.
In the case of AirBuddy, as it is an app that has a very deep integration with the system, this extends not only to the most significant updates (such as macOS 12 to macOS 13) but even minor updates, such as macOS 13.0 to 13.1.
In addition to this part of the updates, there is also the issue of hardware. The app’s operation can be affected not only by the Mac’s hardware, but also by the specific model of AirPods or other devices being used, or even by the user’s environment. I remember some very specific bugs that happened when using the app in an environment where a lot of people have AirPods, like in a technology company office, for example.
So the most complicated part is dealing with this constant change, which in the case of AirBuddy ranges from the operating system to the user’s hardware combination, or the launch of new models of headphones by Apple/Beats.
Considering your experience, would you accept an invitation from Apple to join the AirPods team (if you haven’t already received one, of course)?
I’ve been invited to work at Apple by a few different teams, including the team responsible for integrating AirPods and other devices into systems. I never accepted any invitation to work at the company because I have no interest in moving to the United States, in addition to the fact that being an Apple employee would require giving up several things, such as the freedom to participate in podcasts, write a blog, minister lectures, among others.
As interesting as it could be to work there, for me it’s not worth giving up so much to work for a company; I’m happy being my own boss (despite being the worst boss I’ve ever had). ????
Your app supports both Apple and Beats headphones. With that in mind, software-wise, are there any differences between the two brands’ products that make the process of adding Beats headphones to your app easier or harder?
In the beginning it was more difficult, for two reasons: I wasn’t so knowledgeable about how these devices work and I also didn’t own Beats headphones, so I ended up depending on third-party tests to see if they were working correctly.
Nowadays, as all Apple and Beats headphones follow a very similar operating model, I already have an established process for adding support for new devices, which often doesn’t even require an app update.
The most recent challenge related to Beats headphones was when they released the Beats Studio Buds, as they do not work in the same way as the AirPods – being more aimed at the Android market – so they required a little more work to implement.
Fortunately, even today, I can buy all headphones, both from Beats and Apple, making hands-on testing of the app much easier.
From time to time, we see apps like AirBuddy — that is, that fill a void left by Apple in one of its systems — lose space or simply be discontinued after the company implements its own, native solution. How do you deal with the possibility of this happening to your app?
The important thing is to always go beyond what Apple would do in a native implementation of a feature. Generally, when Apple integrates something into systems, it makes the simplest and most accessible version for all users, without many advanced configuration options.
There have already been a number of changes to macOS that have made basic AirBuddy functionality less necessary, but there is a significant market of power users who want to control more aspects of the experience beyond what Apple offers.
A recent example of this is the feature Continuity Camera, which arrived with macOS Ventura. Initially, it seemed like a death sentence for the Camo app, which lets you use your iPhone camera as a webcam on your Mac. However, this was not what happened in practice, since the Continuity Camera is very basic, while Camo offers numerous options for controlling the iPhone’s lens, image adjustments, and more. I myself continue to use Camo, despite the Continuity Camera always be available.
I try to follow a similar line with AirBuddy, always adding features that go beyond what Apple would do natively. This does not mean that there are no changes that the company could make that would reduce AirBuddy’s market size, but I always try to expand the app’s features so that the impact of this type of change is as small as possible.
Which platform do you consider more friendly for new developers who want to enter the Apple world, iOS/iPadOS or macOS?
This will depend a lot on the developer. I consider all of Apple’s platforms to be excellent opportunities for app development. Perhaps I would give macOS an extra point in this regard by allowing the distribution of apps outside the App Store, which can be easier for those who are starting out, since they do not have to go through the strict rules of the store.
Which platform do you most enjoy developing apps for, iOS/iPadOS or macOS?
I like macOS for the freedom the platform provides. I like to create apps that expand the system’s functionality, but unfortunately on Apple’s mobile systems this is practically impossible.
Thinking like a developer, what feature or service is your dream consumer on Apple systems?
To no one’s surprise, given the previous two answers, I would very much like Apple to open up their mobile systems (iOS and/or iPadOS) more to allow distribution of apps outside of the App Store. This does not mean giving up the security of the systems, as their security goes far beyond the App Store review, which is a much more commercial/political process than a technical one.
What features would you most like to see in a future generation of AirPods (be it the standard, Pro, or Max model)?
I would like a more responsive, or configurable, Adaptive Environment mode feature. I really like the feature, which came with the second generation AirPods Pro, but it only kicks in for very loud and abrupt noises, like a horn, a barking dog, or a crash. I would like a way that allows me to walk down the street with the ambient mode turned on, but without having to use the headphones volume very loudly due to the noise of cars/trucks passing in the next street.
I understand that perhaps Apple has done it that way for security reasons, but nothing prevents the user from walking around with Active Noise Cancellation, which ends up being much worse.
Could you share with us some of your projects for the future, whether related to AirBuddy or not?
I’m currently working on version 3.0 of AirBuddy, which will be a pretty big update and full of new features. Outside of AirBuddy, I’ve also been working on the developer-focused virtualization tool, the VirtualBuddy, plus other new apps I plan to release in the future.
Whether you’re an aspiring developer, a tech enthusiast or just a fan of the Apple world, we hope this interview helped you understand a little more about how the apps we use every day work, and shed light on the challenges of creating an app. for Apple systems.
we do MacMagazine, of course, thanks to Rambo for stopping to chat with us once again! ????
1687116016
#Interview #Guilherme #Rambo #creator #AirBuddy