Google Wants Progressive Web Apps To Replace Chrome Apps (androidpolice.com)
An anonymous reader quotes a report from Android Police: The Chrome Web Store originally launched in 2010, and serves a hub for installing apps, extensions, and themes packaged for Chrome. Over a year ago, Google announced that it would phase out Chrome apps on Windows, Mac, and Linux in 2018. Today, the company sent out an email to developers with additional information, as well as news about future Progressive Web App support. The existing schedule is mostly still in place -- Chrome apps on the Web Store will no longer be discoverable for Mac, Windows, and Linux users. In fact, if you visit the store right now on anything but a Chromebook, the Apps page is gone. Google originally planned to remove app support on all platforms (except Chrome OS) entirely by Q1 2018, but Google has decided to transition to Progressive Web Apps:
"The Chrome team is now working to enable Progressive Web Apps (PWAs) to be installed on the desktop. Once this functionality ships (roughly targeting mid-2018), users will be able to install web apps to the desktop and launch them via icons and shortcuts; similar to the way that Chrome Apps can be installed today. In order to enable a more seamless transition from Chrome Apps to the web, Chrome will not fully remove support for Chrome Apps on Windows, Mac or Linux until after Desktop PWA installability becomes available in 2018. Timelines are still rough, but this will be a number of months later than the originally planned deprecation timeline of 'early 2018.' We also recognize that Desktop PWAs will not replace all Chrome App capabilities. We have been investigating ways to simplify the transition for developers that depend on exclusive Chrome App APIs, and will continue to focus on this -- in particular the Sockets, HID and Serial APIs."
"The Chrome team is now working to enable Progressive Web Apps (PWAs) to be installed on the desktop. Once this functionality ships (roughly targeting mid-2018), users will be able to install web apps to the desktop and launch them via icons and shortcuts; similar to the way that Chrome Apps can be installed today. In order to enable a more seamless transition from Chrome Apps to the web, Chrome will not fully remove support for Chrome Apps on Windows, Mac or Linux until after Desktop PWA installability becomes available in 2018. Timelines are still rough, but this will be a number of months later than the originally planned deprecation timeline of 'early 2018.' We also recognize that Desktop PWAs will not replace all Chrome App capabilities. We have been investigating ways to simplify the transition for developers that depend on exclusive Chrome App APIs, and will continue to focus on this -- in particular the Sockets, HID and Serial APIs."
Jesus Christ just compile the damn code for each plaform so I can run it locally!
And how are they different from normal web apps?
Just wait a week, and it will be replaced with a new one.
So if you made a Chrome app, Google now made your work useless. And what next year? Will they phase out web apps for the new flavor of the year? Google tech doesn't stick and can be abandoned by Google at any moment. I can't build on that.
I can't wait to transition to PWAs so that one day they can tell me it will stop functioning at the end of the month and all my related data will be deleted. This is much better than the garbage applications that keep working even when you are offline. Honestly, how do they expect to spy on my entire life without internet connectivity?! ;)
Anons need not reply. Questions end with a question mark.
In related news.....
You still can't get an Android tablet larger than 12 inches...
(Measures Galaxy Tab A)
Hey, what's 50cm divided by 2.54?
Twelve inches is enough for most people.
There is a 99.9% chance that your "web app" was either nothing more than a glorified bookmark that registered an icon in your start menu and did nothing more than redirecting to a regular website. If you actually used javascript running locally, local storage, or other webapp features, that was basically only thenew fancy HTML5 stuff to begin with and that won't go away either, You mostly have to do a boilerplate update.
bickerdyke
You know I just ported a big application to Android 7.1.
It's so flakey now, I cannot guarantee that the background service will continue to run. It gets killed every so often when the OS decides to run Bixby or similar. I have to block the reload of the gui on rotation of the device because a leak in Samsungs stylus in the text edit field makes it run out of bitmap memory (I thought Google would fix this heap by now, but no, it seems not). So I literally have to move existing controls around the screen myself, changing their layout so they are not unloaded and reloaded.
I have to keep the data in a holding service, because Android kills activities and reloads them seemingly at random. Hundreds of megabytes of preprocessed data I am supposed to save in a bundle of "key = graphView, value = 102.23,123.45..,,..." key pairs, then reload when you flip back to the application, then magically stitch the gui and data together in an instant.
I have a module that Art won't compile because its too big.... at 12000 lines, it runs as interpreted code. Seriously it won't compile a class of 12000 lines.
It's so much work keeping up with Google's fucking incompetent shit.
They changed from Eclipse to Intellij development platform..... completely different file layout, unsupported version plugins, and a whole different set of bugs! This one crashes when debugging if it gets confused about breakpoints. This bug has been there for 2 years.
Each change they make is done in a way designed to break the maximum number of applications for the minimum gain. Can you imagine developing a corporate app, where you can't even ensure it will continue to run? Or that it won't be unloaded to reduce the ram footprint.... even if there's plenty of free ram?
Chrome OS was always a noddy OS designed to run webapps, so I have little sympathy for people who developed for that platform. I had hopes that Android would mature into a full OS, instead it's becoming more like Chrome with each change. It's good enough to run a control panel and a todo list and an SMS/messenger app, not much else.
Ah well, at least I didn't waste my time developing for a short-lifetime 'product'
I'll make sure that I'll avoid it's replacement too. Developing anything for a platform that's going to be dead in a few years is a complete waste of effort for the most part.
It still has no official way to close an app
My guess is that you didn't even bother to check that.
Chrome "APPS" are just that: Not real apps. More like normal Websites.
Chrome Apps: useless.
AMP: useless.
"progressive" apps: useless.
Googles own fault for coming up with such crap.
Psst, did you know about the targetSdkVersion setting in build.gradle? So you can keep using the OS quirks you like?
It's almost like it was built for ease of use because that's what the majority of people care about, rather than the spregy edge case users wanting to computer janitor every interaction of their pocket computer.
OK, then, now that Chrome is doing the desktop web application more seriously, where is Firefox's replacement of the defunct XULRunner that did essentially the same thing?
Kriston
I Think progressive web apps are really good. It is really good for chrome apps. Our team in https://www.identitypi.com/ uses chrome apps a lot. especially as extensions. It is good to hear progress.
Playing a local game? Those don't 'need' central servers and certainly worked before the internets.
Except nowadays, commercial video games need the Internet for matchmaking even if you're playing on the LAN.
<cough>StarCraft II</cough>
And isn't this something they should be able to do pretty readily?
I don't use Chrome apps, and I won't use "progressive web apps", either.
"Really big apps have lots of data powering that GUI, they are not crappy checklists"
I think the platform, as they usually do, has outgrown the inventor. These mobile platforms were devised as consumer devices by companies that like to use one button or make all of their revenue off a single form field on a blank web page.
I object to power without constructive purpose. --Spock
No way these web apps are going to last. Just thinking about developing one makes my skin crawl.
I object to power without constructive purpose. --Spock
Take a look at Xamarin Forms. It abstracts away a lot of those problems to someone else and lets you focus on developing an app. ...and your app works on other platfroms without much fuss.
I object to power without constructive purpose. --Spock
I think that you care because you went to the effort to reply to my comment.
What is the difference between this and a local HTML file. I am very confused on the difference.
The millennial that doesn't like most of the stuff designed for millennials.
font, icons, and layout are usually common to all the app pages and can be cached. Now the data retrieved to populate the layout elements can be analyzed and also cached locally if/when needed. Now the web app works fine when offline (just like loading an html file in the browser directly) - except where data needs to be pulled or pushed to an online resource. Pushing the data can be queued, so that side of things can also be handled offline. Getting new data is the one thing the app can't really work around - but it CAN show an appropriate in-app error/warning message that this can't be done right now. Whereas a typical web page/app would just give the default "service not available" error from the browser/os. The heavy lifting is handled by a JS service worker. So a news reader type application could update it's news articles when a connection is available, and then the app could display those articles if the online connection exists or not. Or a time tracking app could collect entries in a queue and then push them to the server when the online connection is restored.
Why does the Delphi store show "Add to Cart" without a price?
If you repeatedly ran into screens like the following, would you find it still "worth the trade-offs"?
Using a different browser at a different location, I see prices. But neither Starter nor Professional appears to support X11/Linux. Only Enterprise (roughly $3000 per seat) does.
...that I never watched.
google does not spy on your life AND internet is free and uncensored, everywhere.
this would free us from the need of another google "invention" that goes down the drain in one or two years.
Try accessing Flipkart.com or Zomato.com. It feels like you have opened the app, though it’s not the app that you have installed on your phone, it’s just a PWA. Few attractive features of PWA are 1) Responsive- Compatible with any device (desktop, mobile, tablet, including the ones yet to come). 2) Progressive- Work for all users irrespective of their browser choice. 3) Connectivity-Work Offline or on poor networks. 4) Up-to-date- the service worker update process ensures current, with offline Quoted from this article: https://codeburst.io/pwa-vs-am... A Native App is developed specifically for a particular mobile device, customized for the operating system and other device configuration, and installed directly to the device, usually through app stores. A crucial consideration, to be taken upfront, is whether to opt for native apps or web apps https://www.fingent.com/blog/n...