Earlier quoted context omitted.
Four months notice to be told there's no point releasing a Chrome packaged app you might have been working on (which may not work as an extension) isn't very much notice.
Four months is plenty of time to repackage a chrome app into electron or something.
From Chrome Apps to the Web
81–90 of 111 posts
Re: From Chrome Apps to the Web
#82Re: From Chrome Apps to the Web
#83Re: From Chrome Apps to the Web
#84I chose Electron for obvious reasons, but still wish there was a some simpler way to package and distribute Electron apps. And a way to restrict app-permissions on Electron desktop apps - similar to what we do on mobile .
Re: From Chrome Apps to the Web
#85I think next year's Android tablets will be more like the Play Store with Chrome OS under the hood, the apps they are obsoleting today will be a universally inferior experience on tablets because they were only ever supported on desktops. I think Google are betting on the Play Store for Windows and macOS breaking the Windows/Mac desktop paradigm too ... between Chrome the browser and Android apps Google occupies a lo…
After thinking some more... Maybe Play Store for Windows and Play Store for OS X will launch real soon... as Play Store for Chrome. In Chrome OS they're currently adding the Play Store to select hardware including x86 laptops using ... "container" technology. In Chrome OS these apps will start to stop being available in about a year. In Chrome on Windows and Mac they are losing access to these apps, the vast vast vas…
Re: From Chrome Apps to the Web
#86This is going to be really annoying since hardware access from HTML5 is still very rough and not even standardized. Stuff like talking to a serial port isn't even on the radar (so good luck programming a board like BBC micro:bit, Arduino, etc. without a native app), and efforts like WebUSB are still extremely early and not even a full standard. I feel like the product managers making this decision are completely obli…
Re: From Chrome Apps to the Web
#87This is going to be really annoying since hardware access from HTML5 is still very rough and not even standardized. Stuff like talking to a serial port isn't even on the radar (so good luck programming a board like BBC micro:bit, Arduino, etc. without a native app), and efforts like WebUSB are still extremely early and not even a full standard. I feel like the product managers making this decision are completely obli…
The article mentions using Electron or NW.js if you want to continue building apps on web technologies that need deeper platform access. Is there a reason that those are worse options than Chrome apps?
Re: From Chrome Apps to the Web
#88Earlier quoted context omitted.
Asking a end user if foo.com should be allowed to open a TCP connexion to host:port makes no sense. 99.999% of users can't make an informed decision, and they just want the damn to work so they choose "allow". Never ask users questions that they can't reasonably answer, ie don't do what android did for a long time (looks like this has been improving since N). Maybe the case of TCP/UDP could be improved by showing a h…
You can't reasonably limit access to a specific host anyway, because DNS allows you to point a hostname to any IP; once you have permission to access a hostname that you control DNS for, you can connect to any arbitrary IP address, including LAN addresses. (You could slightly mitigate that by blocking RFC1918 private addresses and localhost, but then you couldn't build clients to talk to such servers.) As another alt…
It is awful that we can't rely on devices to do proper authentication but that is the state of security today.
Re: From Chrome Apps to the Web
#89So does this mean Chrome Remote Desktop is going to be a Chrome OS exclusive by early 2017?
There's also the official SSH client that is a NaCl version of OpenSSH, I've been toying with it since it seems kind of superior to PuTTY on Windows.