
Background information
Why your phone deserves a new look
by Dayan Pfammatter
Even in 2023, having a stable connection between your smartphone and camera isn’t a given. Come to think of it, why not?
In theory, smartphone apps that allow you to control your camera are a great thing. They allow for a direct wireless connection between your devices, making it easy to quickly share your vacation photos or to use your smartphone as a remote shutter release. Reality often looks different. It can take countless attempts to establish the connection, only to have it break off randomly. In my experience, such connection problems aren’t an exception, but the rule.
I’m not alone in this. In an article on dpreview.com, Richard Butler explores why camera manufacturers are still incapable of managing something as banal as a stable Wi-Fi connection. His analysis seems plausible to me. Below, I’ll summarise the reasons he goes over in my own words.
In the case of Android phones, camera manufacturers have to deal with a wide variety of devices, manufacturers and Android versions. As a result, camera manufacturers can’t test all device and system combinations by a long shot. The situation is clearer in the Apple ecosystem, but there are other problems. Apparently, it still isn’t possible for cameras to use the iPhone’s NFC connectivity. In addition, apps didn’t have the power to change Wi-Fi settings for the longest time. It’s since possible, but only if you set it up that way. This increases security, but prevents the camera app from establishing a connection fully automatically.
A camera is a piece of hardware. Of course, it does also contain software – the importance of which has grown steadily over the years. But at their core, camera manufacturers are still hardware manufacturers and invest relatively little in software development.
This doesn’t just apply to smartphone apps. Each camera has a proprietary operating system, which runs on a specialised processor; unlike in a smartphone, no standard components are used. The camera manufacturers are on their own here.
In the noughties, I tested various smart TV platforms and phones with proprietary operating systems. That gave me first-hand experience in what happens when hardware-centric corporations develop software and entire operating systems by themselves. They felt choppy, slow, prone to errors and rarely intuitive. Android has done a great service to these manufacturers. But there’s nothing comparable in the camera sector yet.
The third reason Butler cites is that cameras are typically used for five, ten or even more years – in contrast to smartphones. Therefore, cameras often don’t support new, faster wireless standards. However, the basic problem is the same as explained under Reason #1. Namely, that the camera would have to be compatible with the most diverse generations of smartphones and their operating systems.
There is progress. If you have a new camera coupled with a current smartphone, the connection now works quite well and remains stable. At least most of the time. But the pace of progress is leisurely, and I doubt that’ll change anytime soon.
To develop everything in-house is becoming increasingly difficult for manufacturers, as demands on software are growing. Manufacturers should consider incorporating standard components into their cameras. For example, ARM-based chips and a system with a Linux kernel – in other words, something akin to a slimmed-down version of Android. Now, I can’t say if this is technically feasible. But it would make economic sense. This would presumably allow manufacturers to meet future requirements better and at a lower cost.
My interest in IT and writing landed me in tech journalism early on (2000). I want to know how we can use technology without being used. Outside of the office, I’m a keen musician who makes up for lacking talent with excessive enthusiasm.