I would argue that it’s the nature of having a mature and complex product. Adding new stuff is hard because you have a lot of legacy code /UX that you have to accommodate for. You need to move slower because it’s easier to break stuff in a more mature product.
I’d also argue that Apple and Google’s research teams are generally hearing the similar stuff out of their end users, so it’s to be expected that both companies are going to prioritize similar functionality.
That was my experience when I’ve worked on massive products. The complexity of the product impacts development speed, and shared understandings of user desires results in similar feature sets between competitors.
Exactly. You get it. At the end of the day they are all going to get many of the same features.
They both copy from webOS anyway, at the end of the day. That webOS from Palm was way ahead at the time but lacked the hardware and Carrier support needed to succeed.
Me watching WWDC: “Android already does that.”
Me watching Google I/O “iOS already does that.”
In ten years all phones will be crabs
I knew there was a link between cell phones and cancer!!
nah thats social media
if only i could be as successful as mr. krabs…
I’m experiencing déjà vu…
EDIT: Found this thread in the wild, then stumbled upon it. That’s why.
Windows phone 10 had most of these things in 2015
It had everything except apps.
Ouch
… and the users
Oof. I felt the heat from that burn from all the way over here
I miss Windows phone, still the most intuitive phone UI I’ve ever seen.
Microsoft: “I think we really nailed this phone UI. We should make this the desktop computer experience too.”
Ok my god. I had an Samsung Omnia 7 and I loved the Metro UI.
Remote Desktop to a Windows 2008 Server and try to open the Start Menu by clicking a single pixel in the left lower corner… Shoot me.
Qnx had a lot of features before windows phone in 2013.
deleted by creator
I would argue that it’s the nature of having a mature and complex product. Adding new stuff is hard because you have a lot of legacy code / UX that you have to accommodate for. You need to move slower because it’s easier to break stuff in a more mature product.
I’d also argue that Apple and Google’s research teams are generally hearing the similar stuff out of their end users, so it’s to be expected that both companies are going to prioritize similar functionality.
That was my experience when I’ve worked on massive products. The complexity of the product impacts development speed, and shared understandings of user desires results in similar feature sets between competitors.
Exactly. You get it. At the end of the day they are all going to get many of the same features.
They both copy from webOS anyway, at the end of the day. That webOS from Palm was way ahead at the time but lacked the hardware and Carrier support needed to succeed.