Live data from Hacker News

A new breed of Chrome Apps

chrome.blogspot.com

151–160 of 169 posts

Re: A new breed of Chrome Apps

#152

Earlier quoted context omitted.

Why would you have Go on a mobile OS as a mobile application development framework?

I probably wouldn't switch from Java but lots of people want to use Go to make Android apps.

I'd trade Java for Go in a heartbeat

Re: A new breed of Chrome Apps

#153

Earlier quoted context omitted.

That language will be web, I suspect. Perhaps Google will offer prerolled components specifically for Android? I strongly suspect that Chrome is the platform Google wants to push for client development now, with Android essentially as a shell for it. While web may arguably be "worse" on Android now, Google has a very large, talented engineering team who could change that relatively fast. Java is a dead end at this po…

Word on the street has it that Android and Chrome are two highly separate fiefdoms within Google which are somewhat antagonistic (fighting over company priority). There is unlikely to be a high level of cooperation between the two teams without significant internal restructuring. As far as I remember, chrome isn't even Android's default browser.

> There is unlikely to be a high level of cooperation... without significant internal restructuring

Internal restructuring like, say, Andy Rubin beyond deposed as head of Android and replaced by the guy in charge of Chrome (Sundar Pichai), who now oversees both Chrome and Android? Because that happened in March.

(Chrome is the default browser in nexus devices. Whether it's the default in non-nexus devices is up to the manufacturer & carrier, who usually choose to use the AOSP browser - an unbranded front end of the system webkit - because they can control and customise it, which they obviously can't with chrome as a branded google app that's updated through the play store).

Re: A new breed of Chrome Apps

#154

Earlier quoted context omitted.

Firefox as of 23+ uses significantly less memory than Chrome (in my experience - your mileage may vary though)

Being able to identify which tabs are hogging CPU/memory is a deal breaker to me.

about:memory shows detailed report on which website uses how much memory.

Re: A new breed of Chrome Apps

#155

Prediction: The much-anticipated convergence of Android and Chrome is near. These new Chrome apps are the programming model for the upcoming native Android webapps The next milestone I expect to see is V8 added alongside Dalvik as a first-class runtime for Android. Maybe in Android KitKat?

Prediction: Chrome (the browser) is slowly taking over your OS. P.S. while trying to add this new type of app, I was tricked into signing into my chrome account, which I had managed to avoid all this time.

So another hook for always positively identifying Google's always listening data-collection network.

I've started jumping the Google ecosystem. I'm now more often than not, not signed into a Google-account, to the point where I can go a week without signing in at all.

No way I'm joining a program which requires me to reverse on that.

Re: A new breed of Chrome Apps

#156

The new breed of chrome apps has a lot of flaws after I tried to convert my app over: -Previous installed chrome app matches the HTML5 api, the new chrome apps has a lot of restriction where you have to totally rewrite you code in terms of storage. i.e. Chrome.storage instead of localStorage; All chrome storage is async. -The new window format for apps are a huge UI flaw. You can not open an Chrome app in a tab anymo…

The result is, you can no longer build an HTML5 app and prepare it for the chrome store, you have to specifically change the code to package it. This makes it less ubiquitous and creates extra work for developers.

So a proprietary HTML-based format then? Yay Google for promoting the open web!

With Google going down south, we need Firefox OS to get traction, and we need it now.

Re: A new breed of Chrome Apps

#157
post #9

Earlier quoted context omitted.

Cool, Java Applets reborn

More like ActiveX components reborn, because these things will only run in Chrome. Much like ActiveX only ran in IE.

Well, Activex was windows only. At least you can run in three big platforms now. And probably Android later. This is not activex, perhaps Adobe AIR is kind of similar, but it was not web centric.

Re: A new breed of Chrome Apps

#158
post #95
post #33

Chrome is now a serious security risk for me. it's just waiting to happen. for now on, it will be used as the remote debugger for android browsers (until we have something native). just like i have a spare mac for running xcode for the same reason. firefox serves me well. and will not make me worry much.

All this functionality sounds like an increased attack surface, and it is. But when the comparison is Firefox, it's far outweighed by the fact that Chrome has a very good process sandbox, while Firefox has none. It will be years before Firefox can match Chrome's level of security.

Moreover Google has paid millions to security researchers for finding flaws in Chrome.

Re: A new breed of Chrome Apps

#159

Earlier quoted context omitted.

This isn't 100% true. The majority of that is the native shared library and binary resources. These could be hosted centrally and loaded from an APK. It isn't totally necessary to package them in an APK.

But in that case you're both drawing attention to the fact that your app is HTML5 (which thanks to Facebook is associated with a low quality experience) and also that the user has to download a separate library in order to run it. You'll likely get a significant portion of bad reviews solely motivated by this, just as with apps that require the user to download Adobe AIR separately. For example: https://www.google.co…

In my case, I happen to be doing something completely different with AOSP. I'm not looking to build a webapp for the Play store. We are embedding AOSP on our own hardware.

Also, I don't care what Facebook says.

Re: A new breed of Chrome Apps

#160

Earlier quoted context omitted.

This isn't 100% true. The majority of that is the native shared library and binary resources. These could be hosted centrally and loaded from an APK. It isn't totally necessary to package them in an APK.

You still have to download the library at some point, and the library has to end up in your app's private libs folder. Android doesn't do dependencies or inter-app shared libraries outside of those that are part of the platform.

If you embed Android yourself, you can make it do anything you want.
Post reply on HN