3 ms·
Couldn’t fit enough ads in the android UX so they’re starting from scratch. /s There isn’t a technical reason to do this other than pulling support from Google
by happytiger 3y ago
Couldn’t fit enough ads in the android UX so they’re starting from scratch. /s
There isn’t a technical reason to do this other than pulling support from Google as they continually show how much Amazon truly sees them as a competitor.
It also shows a roadmap possibility, like Amazon eventually wanting control of their own hardware or chips (which is exactly what they are doing: https://www.aboutamazon.com/news/aws/take-a-look-inside-the-lab-where-aws-makes-custom-chips https://www.aboutamazon.com/news/aws/take-a-look-inside-the-...) to compete with Apple in custom silicon.
- blacksmith_tb 3y agoSeems like a Pyrrhic victory though? It sounds like Vega will be similar to ChromeOS, boot into a browser, more or less. That could work for consuming Amazon's own content like Video or Kindle, sure. And Netflix etc. should work, but no native apps may turn off some potential customers I would think.
- arrakeenrevived 3y ago>other than pulling support from Google as they continually show how much Amazon truly sees them as a competitor. It seems the opposite to me. The article talks about this. Google has contractual limitations on manufacturers that ship devices with Android that says they are not allowed to also manufacture devices with forked versions of Android. This was making it hard for Amazon to find any manufacturers that contractually even could make Fire devices (since FireOS is a fork). It seems like Google was the one pulling support from Amazon.