iPhone bias vs Android

The real issue here is that “Android” doesn’t make phones at all. It’s an operating system written at Google and available to anyone who wants to use it. That gives manufacturers a sort-of standard they can use as a basis for their phones. They can add or subtract features, and they can use whatever hardware they can force it to run on. That means that there’s an almost limitless range of Android devices out there, many with great capabilities. However, there’s no clear standard in terms of hardware to the point where “Android” doesn’t mean much in terms of describing a device. When it comes to apps, there is a vast range of possibilities, but some of those depend on taking advantage of specific hardware or OS quirks that might disappear.

Apple sells, primarily, hardware. They provide some really nice software to run on that hardware, but they control their hardware. That means that while there are various versions of, say, iPhones out there, they have a great deal of standardization and backward compatibility. Apple also exerts lots of control over phone and tablet software - apps have to conform to a standard that minimizes the risk of incompatibilities. This irks many who want a more open system, but it does tend to ensure iPhones work the way they’re supposed to. They also sell a whole lot of copies of the same model.

That means it’s sometimes much easier and cheaper to design something for Apple products.

I’m sure Apple likes it this way, but it’s not a conspiracy. Some other company could come up with a popular device and a SDK and let people write and design stuff for their device. In fact, many companies have done so. However, developers in a free society get to choose for what platforms they develop products and my impression is that designing stuff for Apple seems to pay better.

I guess it was simply luck that the pair of hearing aids I purchased on-line last year connected directly to my non-Apple smart phone. They also connect to my new Microsoft Surface Pro laptop as soon as I turn it on…after pairing once the first time in the Bluetooth setting. I don’t notice any delay in an audio signal. Well, not actually luck. The description said they connected via Bluetooth but I assumed all new hearing aids connected directly via Bluetooth.

I can even use a cheap Bluetooth USB “dongle” plugged into my desktop but I really don’t listen to stuff on the desktop.

I retired after a career in electrical engineering at the National Bureau of Standards Radio division in Boulder, CO…at least that was the name before several later name changes.

I have an Android phone for personal use and an iPhone for work.but for the hardware of the two, I prefer the iPhone, although the price of the iPhone is higher than that of Android, but in terms of hardware and software, the iPhone is significantly more prominent than Android.on the contrary ,Android also has its advantages, and its operations are more comprehensive , such as Android to Android or Android to iPhone…

For all the criticism levelled at them, Apple has always taken accessibility seriously.

2 Likes

As others have said here: it’s pretty much a battle of closed system (Apple) vs the world (Android-based cell phones). Altho the Android phones (Samsung being my own brand) are 5 times more popular on a global scale, that doesn’t mean that software companies are willing to create Android-based apps to help hearing impaired users! We are still a sliver of the total market.

In that respect, I have to hand it to Apple to have jumped on the wagon really early, developing a range of Apple-compatible apps for us hearing impaired users. Even so, I’d prefer an OPEN system, not based on a singular hardware platform. I just get a creepy feeling that Apple wants to control ALL forms of communication: written, spoken, et al, store them on a cloud, make it useful for the NSA, even hackable; slice and dice data for marketing spam …

For now I am sticking with my Android-friendly Phonak Audeo B-Direct aids that work beautifully with my Android-based Samsung 6S Global in addition to my MacBook Pro running OS High Sierra. Um, which reminds me: y’all read about the SUPER bug that enabled root superuser access to Macs? Fix it now!

P’haps, but I DO have a pet peeve with them: the laptop product line has taken a back seat to iPhone development. Plus, Apple removing useful ports (and even the CD drive) from laptops is infuriating. Like we’re supposed to travel with a gaggle of gear now required to do simple things that my older laptop does effortlessly. The Macbook Pro on which I’m typing now is from 2015, and I honestly don’t WANT a newer Mac. I need a port for the TV streamer with an audio jack for that plug, plus the power cord; on the other side is a port for my cell phone for downloading photos, and one for a jumpdrive even. This puppy is FULLY functional!

Well, I don’t mean to hijack a hearing aid thread to rip into Apple, but STILL. Grrrrrrr…

umm…err realistically, what you said describes google. Its well documented that iOS is more secure and  does not sell your information like google or track your online whereabouts so as to sell you clickable ads relating to your interest. Also its not as much the android os is more popular, I would say the less expensive no resale value smartphone hardware is more popular than the operating system android in all its various forms.  has taken security seriously for decades and so has accessibility as Seamaster said above.

You know it’s coming…Blackberry baby!!
Too bad they’re just about defunct. And now even their built-in Android runtime is getting obsoleted due to the version it used. And pretty much no one is writing programs for it either. Sigh.

Well now that the Phonak direct is here I have to say I am underwhelmed and grossly disappointed. Using old technology to simply connect to a broad range of phones is not what I wanted. The race to please every phone user with one solution has led to a very inferior outcome. Give me made for Apple any day.

You will not see made for Android because Android is a name for a series of operating systems on thousands of different hardware configurations and no one can make something work seamlessly for all those combinations unless they dumb it down to a very basic single ear basic Bluetooth like Phonak did. That really is no help for me. I want the advantages of a smart phone and the fully featured low power solution of the made for iPhone aids. You are never going to see those features with Android.

Did you see my post about the beginnings of hearing aid support on Android? Phonak built a solution based on Bluetooth Classic. That was never going to be anything other than stop-gap. The future is the low energy Bluetooth 5. Why do you think Google is incapable of implementing a bluetooth hearing aid protocol? It’s not so much Apple v. Android imo. It’s open standard v. closed. I know which one I want to succeed.

Because Android is only an OS not a whole phone. It is implemented in hundreds of different forms. It is dependent upon all those phone manufacturers and what bits they see as important. Don’t hold your breath waiting for Bluetooth five to be universally adopted and the technology in all those phones to be similar enough for all of them to offer the sort of benefits already available to iPhone users with made for iPhone HAs. Have you actually used them? The find my HA feature alone has the potential to save you from losing your HAs. There are people out there who keep their phones for 6 or more years and they won’t be able to use your idea of an Android system without upgrading their phone. Some HA manufacturers are unwilling to embrace the technology because they believe HA users are not interested in or able to cope with technology and they want a one solution fits all. I think those manufacturers are going to be left behind. The manufacturers who have gone down the made for iPhone route have a base of phone users, to cater for, who all use the same or almost the same OS on every phone with very similar hardware. That is why it works. Anything but a basic connection is going to be very hard for HA manufacturers to work out so it works the same on lots of different phones.

Ok. I’ll buy the model whose manufacturer thinks that hearing aid support is important.

If there’s a standard and they conform to that standard and test against that standard it will work. Bluetooth 5 will be universal because… well, it’s better. The core hearing aid profile code will be supplied by Google. The semiconductor manufacturers who supply bluetooth modules will include supporting code as a matter of course. Why wouldn’t they? I think you’ll find that every phone out there- including Apple- uses Bluetooth hardware from just a few suppliers.

That’s the nature of the market place isn’t it? We all have to buy new hardware to get the latest features. Your Apple phones should continue to support your mfi aids indefinitely. Why would Apple deliberately alienate their customers? I would expect Apple and everyone else to move their cutting edge to the better bandwidth of Bluetooth 5 and a new generation of aids will be designed to take advantage of it.

I have Phonak V90s. That is probably why I find it so frustrating that Phonak chose such a lame solution to their connectivity woes. The Resound Linx aids were uncomfortable in my ears and the LiNX² had microphone noise which drove me crazy. There was no rep to see if anything else could be done when my audiologist had exhausted all her ideas. The Phonak aids work very well as hearing aids but I really miss the made for iPhone advantages. All this insistence on Android solutions just feeds the myth that the HA companies do not need to do made for iPhone versions. Unfortunately my best hearing result was with Phonak and they are hell bent on not bothering to supply the one feature I really want. It will be years before enough phones are Bluetooth 5 and Phonak will still want their aids to be backward compatible so they will probably take even longer to switch. They will then not supply the other features that come with iPhone compatible aids. I hope I do not need new aids for a long time because I am not willing to make such compromises again.

Back in time, I had an IMSAI computer with small floppy disks and upgraded to a Tarbel controller for larger disks. But, it still needed a driver that I then got. I revised it in assembly language and assembled it placing it in the operating system. Not something today’s users want.

Since the IBM PC, standards came about making all this transparent. From that point standards committees came along to maintain the simplicity. The cost is time. The benefit is ease of use.

BT came along in 1994 without standards. Erickson introduced it as a wireless alternative to RS-232. It became popular and the industry went to a standard. A lot of products evolved in such a manner. In the Erickson era, what worked with what was iffy. Today features are evaluated. HA are coming late to the party. It is a minority feature that wasn’t promoted until Apple made it happen. Like Erickson, they saw a niche they could market too. Now, it is being integrated into the standard.

You can complain about how it is taking too long rather than being appreciative that it will soon arrive with a standard. Invariably some of the hardware won’t work as well as it should but that will improve.

The anger about something taking too long or not working to its potential quickly enough isn’t just with aids. It is everywhere but doing it a different way brings more chaos than success.

Rage, rage against the dying of the light sounds.

Well, yeah. I’m complaining. I’ve got aids that are well past their use-by date. I should be trialing the OPN1 or whatever right now. But here’s the problem. I just know in my waters that the day after my evaluation period runs out that the shiny BT5-based aids that I really want will be released and I won’t be able to get them. Or the other possibility is that I’ll still be using my crappy old-tech aids this time next year (if they don’t break down first) with another year of sub-optimal hearing under my belt.

Don’t know where you’re from, but if you have a US Costco available to you, you could do a 6 month trial and see where things stand then. (I would think Resound Forte or Bernafon Zerena would be most tempting) BT5 HA could come out within 6 months, but my suspicion is that we’re talking another 18 months to 2 years. Heck, it took Oticon what, 18 months to come out with their Connect Clip? (I think it’s now available, but haven’t really heard anything definitive.

I agree. That would be the perfect solution… if we had a Costco. I live in pretty much the only place in Australia without one. Yet another thing to whine about. Re timing: Who knows? The Bluetooth Hearing Aid Profile was supposed to be ready by the end of this year. I found the email address of the Chair of the Bluetooth SIG Hearing Aid Working Group somewhere. I’m sure he would tell me to bugger off if I asked him for an eta.

I would think there’s a good chance you’d get a useful reply if you wrote a polite email. Worst case is that you don’t and you’re no worse off than you are now.

I asked my question in the comments section of one of his blog posts. We’ll see.

Got this email from two-pi.com:

The Bluetooth profile for hearing aids is still not adopted by Bluetooth consortium. The schedule is not announced to public, but in case it will be adopted in 2018, then the first products using the profile might be available in 2019.

Regards,
Tarik zukic

Not want people wanted to hear, but seems plausible to me.