Amazon Preparing to Release Smartphone
online.wsj.com
online.wsj.com
But I'm not one of those marketing geniuses who loves to create walled gardens and captured verticals and synergized markets and all that...
And yet virtually nobody talks about this. I'm quite certain that any developer without an accountant is either getting it wrong or ignoring it completely. This is the reason that if I release a game for Android, it will only be through Amazon.
https://support.google.com/googleplay/android-developer/answ...
No doubt if they are planning a smart phone though it'll be more similar to their Kindle Fire tablets which is fair enough, but hey I can dream..
Posted: http://online.wsj.com/news/articles/SB1000142405270230387360...
Google: http://online.wsj.com/article/BT-CO-20140411-711057.html
Why not post the google one and save us the collective time lost?
Would they sell it at or close cost like most Amazon hardware? I don't see a lot of the customer using "amazon content (movies and music, which amazon is trying to bet heavy on)" on their tiered data plans.
Or sell above cost and join the market of, oh so many, other handsets?
Google Music is a perfect example, actually. I allow it to stream music over 3G, but it still aggressively manages a local cache of music anywhere from 1-2GB, leveraging WiFi to save data. (It would use more if I didn't have a dinky 8GB device)
The fact that in today's "build software people want" world you need to do it three times, or at the very least in 3 different languages on the front-end is fucking crazy.
Now, the HTML5 problem will solve the platform. Especially with local storage and high performance browser graphics! Boom shaka-laka. Coming soon hopefully.
The problem after that is much more trivial - responsive layout. Can you really write an all purpose app that responds to desktop, and all shapes of mobile and tablet without having to think about each form factor individually?
I doubt it. More likely we would have a bunch of browsers that followed an even more divergent set of standards.
Web standards are slow to improve because they involve getting a bunch of competing companies to agree to things, often things that are against their commercial interests. It's ridiculous for people to claim to support web standards but then complain about the slow pace. That is an inevitable part of the process of trying to get everybody in the world to agree on a single platform API that monopolises all user facing software. Native platforms move forwards more quickly because Google doesn't need to get permission from Apple and Mozilla and Microsoft before they add a new feature to Android. The web has to be a slow moving lowest-common-denominator type platform or it loses the only advantage it has, which is that it runs just about everywhere.
If you want a platform that is fast moving, exciting, and cutting edge then you don't want web standards at all, because web standards are exactly the opposite of those things, by design.
The Kindle Fire OS is a fork of the Android Open Source Project, not Ubuntu or Ubuntu Touch.
Since its the default OS for Linux on AWS, it probably has a pretty large install base. More than most would probably assume.
Reminds me of the zSpace. (https://zspace.com) Pretty neat stuff.