181–190 of 216 posts
Earlier quoted context omitted.
I can't even run chrome on my android (2.3). I've resorted to Firefox which is actually pretty nice.
Firefox for Android supports Froyo (2.2) up the latest Jelly Bean (4.2). Chrome for Android only supports ICS (4.0).
Earlier quoted context omitted.
You couldn't be more wrong and, unfortunately, I don't have the karma yet to enable downvoting :-). Easy example as long as we're on the topic, the Chrome browser or ChromeOS. I can think of a dozen things that could be done to Android to both mitigate against current threats and exploited weaknesses and either not interfere with or improve user experience. Unfortunately, we are long past the point where fundamental…
The usability of the browser is severely hampered by the security requirements. For one, it necessitates running code downloaded from the web in a sandbox, which prevents it from interacting with the rest of the computer in a meaningful way except through narrow channels designed painstakingly by committee. The web would be a much more interesting place if we could hook up arbitrary peripherals. It's holding back the…
Im enginering something, that was a spinoff of this thougths.. i 've go an answer balancing the good parts of the web with the good parts of the app platforms.. plus some concepts of biological cells..
it may be a party for google, apple samsung and the like.. but we technological people are back to the nighmare that were the 90's.. with multiple platforms.. and thats the only reason browsers became popular.. even when we were loosing so much..
here we are into the nightmare again.. have to create things for multiple platforms :(
Earlier quoted context omitted.
Are you talking updates without prompting the user? My Nexus (original) updates itself every so often with a prompt.
Android ought to update like Chrome: silently downloaded via Wifi (optionally via 3G/4G), installed in the background to whatever extent possible, and then show a reboot prompt only if needed. Android is a Linux distribution, so most updates ought to be possible without having to reboot the device.
It's pretty much the equivalent of forcing a reboot of an OS like Android.
Earlier quoted context omitted.
> So iPhones aren't so secure. What's your benchmark? If you have access to the hardware virtually everything can be jailbroken. With the iPhone, however, you can't do it non-destructively (i.e. you can't get personal information). At least that's my understanding, if I'm wrong please correct me.
The original user-friendly jailbreaks worked by pressing a button on a website. That means that any website could use the same technique to run native code with root privileges on your iPhone. I'm not sure how much physical access is required for current jailbreaks.
However, I am no mobile developer, so take this with a grain of salt.
Earlier quoted context omitted.
Not to mention that Chrome has figured out how to push updates, while a majority of Androids are still running a version released over two years ago. If Google can start pushing auto-updates to all of its devices, that would be one of the greatest improvements ever made to Android. Also, one of Chrome's most touted features is performance, which has always been Android's weakest point. Hopefully he'll be willing to a…
> Not to mention that Chrome has figured out how to push updates, while a majority of Androids are still running a version released over two years ago. The reason for the hold out is the carriers, not Google. Google is very good at pushing updates to phones when it's not limited by the carriers (and Android implemented over the air updates years before anyone else did. iPhones still require cables to be updated).
This simply isn't true.
Observation by Benedict Evans: almost all key divisional leads at Google were born in India. Android, Engineering, Advertising, Youtube… Polar opposite to Apple, which is a white boys club.
There are lots of Indians in top Google management, definitely, but they're hardly the majority. Maybe 25% of "key divisional leads", maybe 25% of SVPs (a group that greatly overlaps with "key divisional leads"). First of all, there's no "key divisional lead" of "engineering". That's not a division at the top level. That'd be a pretty stupid top-level division, in a company which is mostly engineering (I'm deliberate…
http://www.google.com/about/company/facts/management/
"Nikesh oversees all revenue and customer operations" - revenue, and more.
Two SVPs are listed for specifically for engineering, both Indian.
Android and Chrome, obviously. And there is no bio given for Salar Kamangar, Youtube, which sounded as thought it could have been an Indian name but obviously wasn't.
That's quite a high proportion of Indian people in senior positions, don't you think?
Beyond that, you're getting very upset by minor lack of precision in a tweet, of all things.
-Benedict Evans
Earlier quoted context omitted.
Not to mention that Chrome has figured out how to push updates, while a majority of Androids are still running a version released over two years ago. If Google can start pushing auto-updates to all of its devices, that would be one of the greatest improvements ever made to Android. Also, one of Chrome's most touted features is performance, which has always been Android's weakest point. Hopefully he'll be willing to a…
Much harder for an OS than an app. Phone makers have their own custom set of drivers for driving their unique hardware and these often have to be changed in subsequent releases to deal with changes to the hardware abstraction layer. And even for releases that don't change the exposed hardware abstraction layer it can be really difficult to know if each phone maker's drivers will deal properly with subtle changes to t…
Earlier quoted context omitted.
> Before Android, you could write a Windows Mobile app and have it run pretty much on every Windows Mobile device and the same with Blackberry and iPhones. Considering that Android pre-dates the iPhone (and thus iOS), the statement isn't accurate. This article cites 2004 and the iPhone didn't debut until the middle of 2007. It was indeed a nightmare, not only in the development process but in distribution. Good luck…
Note that 2007 is the iPhone's public debut. The project was started in 2004 [1]. Android the product was also announced in 2007, after the iPhone, although the project indeed started before the iPhone, in 2003 [2]. [1] http://readwrite.com/2012/08/07/4-real-secrets-weve-learned-... [2] http://www.businessweek.com/stories/2005-08-16/google-buys-a...