Live data from Hacker News

Bose has released API docs and opened the API for its EoL SoundTouch speakers

arstechnica.com

71–80 of 416 posts

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#71

Earlier quoted context omitted.

If only their sound signature was a bit better... they went all in on engineering tricks to make things small and cheap to produce, but it shows in their sound quality. Their QC headphones are the best in noise cancellation, and the sound quality is good enough that they're my pair of wireless headphones.

A long while ago i heard something (that might have been a urban myth) about Bose putting useless weight into their headphones to make them appear more "substantially professional". Is that a myth or they have pivoted towards actual quality since early days?

I believe that's always been a thing. A long time ago I read this teardown article [1] of real vs counterfeit Beats headphones. And even the counterfeit versions had metal weight added to make it feel like the real Beats headphones!

[1] https://blog.bolt.io/our-beats-were-counterfeit/

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#73

This is not open sourcing any actual software or hardware it is “open-sourcing the API documentation for its SoundTouch smart speakers”. You might be able to point them at an alternative back-end¹ if you want the cloud features, but that will need to be written from scratch rather than being forked from code provided by Sonos. > When cloud support ends, an update to the SoundTouch app will add local controls to retai…

The question on my mind is will the SoundTouch app continue to be supported on new mobile OS versions ?

Is it the same app that caters for other speakers too ? If it is, and Bose continue to include their old speakers on the functionality of the app, then I can hardly see how this is a true EoL. They’re really continuing to support the speakers in their app, at least.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#74

Earlier quoted context omitted.

This def needs to be celebrated and rewarded. I am more likely to purchase Bose now.

Bose hardware quality is rather low and, and their sound quality is sub-par, while forcing you to pay the Bose brand tax, riding the corpse of Amar around for profit. I'd avoid, even if they happened to do this.

Some of their high priced noise cancelling headphones have excellent quality. I purchased the QC-25 ages ago, and when it stopped working I reached out to support, this was beyond their 3y warranty, provided serial number and they sent me a new QC-35 no questions asked replacement unit.

I am very happy with my QC-35 headphones. They are probably 5y+ now and they go with me everywhere. I think it is unfair to state their hw quality is low. It is much better than low.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#75

Earlier quoted context omitted.

This def needs to be celebrated and rewarded. I am more likely to purchase Bose now.

Bose hardware quality is rather low and, and their sound quality is sub-par, while forcing you to pay the Bose brand tax, riding the corpse of Amar around for profit. I'd avoid, even if they happened to do this.

My experience is the opposite: Bose hardware and sound quality seems excellent to me.

This may be subjective. Bose might sound good to some people's ears and less good to other people's ears.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#76

Earlier quoted context omitted.

If only their sound signature was a bit better... they went all in on engineering tricks to make things small and cheap to produce, but it shows in their sound quality. Their QC headphones are the best in noise cancellation, and the sound quality is good enough that they're my pair of wireless headphones.

A long while ago i heard something (that might have been a urban myth) about Bose putting useless weight into their headphones to make them appear more "substantially professional". Is that a myth or they have pivoted towards actual quality since early days?

My understanding of modern Bose kit based on RTINGS reviews is that it's fairly competitive in its price range. Still a touch pricey for what you get, but not bad by any means—like 2nd/3rd best, and occasionally punching above its weight for their midrange offerings. They seem to be #1 for comfort (headphones) though.

I don't own any, I've just read reviews from when I was in the market for new headphones and earbuds.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#77
post #8

This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.

[flagged]

Yes. Like with Tuya devices (tasmota) or the WRT-54G two decades ago.

Only takes one person to create the new firmware. Everyone else can follow whatever steps are needed to use it.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#78
post #74

Earlier quoted context omitted.

Bose hardware quality is rather low and, and their sound quality is sub-par, while forcing you to pay the Bose brand tax, riding the corpse of Amar around for profit. I'd avoid, even if they happened to do this.

Some of their high priced noise cancelling headphones have excellent quality. I purchased the QC-25 ages ago, and when it stopped working I reached out to support, this was beyond their 3y warranty, provided serial number and they sent me a new QC-35 no questions asked replacement unit. I am very happy with my QC-35 headphones. They are probably 5y+ now and they go with me everywhere. I think it is unfair to state th…

In current dynamic world product quality of a company 'today' vs '5y+ ago' may drastically change. Sadly, usually to the bad side

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#79
post #20

Providing API specs is not open-sourcing them. Where's the source code?

Yeah, it's kinda sad how much applause this is garnering when publishing API specs should be bare minimum for any smart device, never mind EoL concerns.

Don't let perfect be the the enemy of good. I fully agree with you on what the bare minimum should be, but the reality is that our definition of bare minimum is currently a fantasy. Any steps taken toward our vision is good and should be applauded IMHO. Especially when it's a major player like Bose that hopefully sets a positive precedent and gets other manufacturers to realize this is not only possible but leads to applause and hopefully more sales.

Evolution v. Revolution. I'd prefer the latter, but realistically the former is the more likely to succeed short of people like us getting control of regulatory bodies and forcing it.

Re: Bose has released API docs and opened the API for its EoL SoundTouch speakers

#80
post #8

This is how "end of support" should be handled. Instead of turning devices into e-waste, open-source them and let the community extend their life. Kudos to Bose for setting a good example. More companies should follow this approach - especially as right-to-repair becomes a bigger issue.

[flagged]

I'm not even sure what you're complaining about here.
Post reply on HN