But in this case it's a software change and people who buy the hardware don't own the software. It's licensed to us as consumers. Licensed software can legally be changed by the developer.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
watchOS 7 Removes Force Touch Support From Your Apple Watch, Here's Everything That's Changed
- Thread starter MacRumors
- Start date
- Sort by reaction score
Your point would have validity if the customer was backed into a corner and OS upgrade was required. When you choose to upgrade you take the risk.
Generally the courts have taken a dim view of screwing over customers and then saying - its software dummy. We told you in a 100 Page document you had to sign before you could use your device.
Well then by your "facts" companies shouldn't even bother posting legal documents such as their T&C since they won't hold up in court.
Keep in mind you never owned the software, it was just licensed to you.
#7 (switching between forecast, temperature, and precip) has always been possible by tapping on the screen. Been doing it that way for a long time.
A few thousand? watchOS is probably a huge codebase. So no, it wouldn't be a few thousand. Testing takes a time and resources. If it takes 5 minutes to make a code change that doesn't mean work is done after 5 minutes. It usually takes more time to review, test, and deploy than to actually make the code change. Also, that time and resources takes away from maintaining more relevant code or working on future, more meaningful projects. These things is where the costs start adding up.
And as I said before, it's not like Apple to put a lot of resources into something they're phasing out anyway. If there were more people using it or it were a larger impact, I could see them slowly phasing it out. But here's some anecdotal evidence that it was barely used: here on MacRumors this post currently has just 155 comments after almost 24 hours. On an Apple-centric site this story is barely more than average; there's no tweet storm of users complaining it's gone; news media has't sad anything; there's no angry FaceBook mob with pitchforks over it. So it just makes sense for Apple to nix it now.
I agree that Apple is making so much money they can certainly afford it. But one of the reasons they're making so much money is they make good business decisions (or at least try to). And putting effort into maintaining Force Touch for a tiny user base is not a good business decision. You don't start making bad business decisions simply because "we can afford it."
Reminder that I like Force Touch and would love to keep it around. I just see what I think is the reality of the situation.
Yes - I was wondering about that. It does work for changing the watch face on AW5. The article mentions that this is simply a long press, but it feels just like force touch.
You're using your phone wrong if you're pushing that hard. I have my force settings set to firm despite the cracked glass and exposed display panel and there hasn't been a single issue with the functionality with very regular use
True, but it’s not magically disappeared on older models. It’s all bizarre as they haven’t even replaced Force Touch with Haptic Touch like they did on the phone.
Hopefully Apple doesn’t get the galaxy brain idea to remove Force Touch from the trackpads next.
It is so difficult to clear all notifications now. Why did Apple think it was a good idea to remove a feature that was so easy and intuitive to do?
Same here. Loved the feature and will miss it on both the watch and phone.
Honestly the one I miss the most is the one not mentioned in the article:
Where is the "Disable this notification on Watch / Send as secondary" menu?
I used it all the time for annoying notifications like those from games, real estate apps etc...
I'm almost ok with all the others, although I hate the waste of space for new buttons and the added scrolling required.
I still think though that a consistent long-press replacement (as on the XR, which I love), just like they did for Change Watch Face, would have been both smooth for old users and intuitive enough for new ones.
Where is the "Disable this notification on Watch / Send as secondary" menu?
I used it all the time for annoying notifications like those from games, real estate apps etc...
I'm almost ok with all the others, although I hate the waste of space for new buttons and the added scrolling required.
I still think though that a consistent long-press replacement (as on the XR, which I love), just like they did for Change Watch Face, would have been both smooth for old users and intuitive enough for new ones.
Does anyone know how to change Siri languages when replying to a message with this new interface? Before you just started the Siri dictation mode and then force pressed the screen to switch from English to Danish for example, but i wonder how it is done now?
I've just replied to a Whatsapp notification and it was already there, between the three buttons (Dictate, Write, Emoji) and the canned replies.
Does that mean you can just pick dication in Danish or dictation in English? (depending on enabled languages)
Exactly, see these photos I've just taken.
Attachments
Awesome! Thanks for the photos. That makes me a bit more relaxed as I am waiting for a new Apple Watch. If I could not do this, 80% of my workflow would be brown on the watch. It seems to be one extra step compared to before, but as long as it works I am good.
Well, there went a feature I used a lot. I was wondering why my 
Watch Series 4 "glitched out" and opened the calendar when I went to change my watch face. It didn't, I just didn't have Force Touch.
I used it all the time on iPhone - gone.
I used it a lot onWatch - gone.
Only a matter of time before it is no longer supported in macOS (or did Big Sur already axe it?)
Watch Series 4 "glitched out" and opened the calendar when I went to change my watch face. It didn't, I just didn't have Force Touch.I used it all the time on iPhone - gone.
I used it a lot on
Watch - gone.Only a matter of time before it is no longer supported in macOS (or did Big Sur already axe it?)
we all know they remove it coz of money saving. that's it. no need to over thinking