How to upgrade app shell of a PWA (Progressive Web App) - progressive-web-apps

I was wondering if there's a way to upgrade the app shell of a PWA (Progressive Web App) after the PWA has been installed on the user's phone.

A progressive web app rely on Service Workers to optimise resources loading. The app shell is no exception.

Try take a look at sw-precache too to facilitate caching & versioning of resources.
Alternatively you could manage it yourself through simple versioning. Ultimately the important part is to notify the application that the resources need to be updated by invalidating the cache. The same applies for any static files.

Related

How to deploy SAP Spartacus PWA to app stores

We are currently working on a new PWA mobile app using the SAP Spartacus framework, and we would like to package and upload this new mobile app to the Google and Apple app stores. I've found online documentation for using Bubblewrap for deploying PWAs to the Google play store and PWABuilder for deploying PWAs to the Apple app store, but I have not found anything online specifically for Spartacus PWAs.
I have not yet attempted to deploy to either of these stores using either of the packages mentioned (Bubblewrap or PWABuilder), but I'm assuming from experience that the process for packaging and deploying a Spartacus PWA will be more complicated than a simple PWA.
Has anyone done this already and can share tips/tricks on how to make this happen? Is anyone aware of online resources to help make this happen?

Flutter Desktop (macOS, Linux, Windows) - How to deliver code updates?

Delivering client updates is important for future compatibility of our product. Obviously, the desktop storefront can issue application updates and assist with managing that process. However, many of the popular developer tools in use today can be downloaded directly from the developer's website.
Is there a solution that allows me to package a Flutter desktop application and deliver updates without needing something like an App Store? Something that can download the updated binaries across launch and install them before the next launch?

Call phonegap plugin function within web app

i am building my first phonegap app and when i open the app i instantly redirecting (window.location) the user to my server where my web app is hosted. Is it possible to load the phonegap plugins from there? Because the "deviceready" event is not firing and i cannot call any plugin functions.
I can confirm that loading remotely does appear to allow access to native components (when scripts are properly loaded) and that cordova.jsdoes not appear to need to be loaded by the local index.html bootstrap.
Short answer: Yes
Some 'gotcha's'
You will have to supply correct cordova.js version for the platform browsing to your site.
you can look here for more info https://github.com/apache/cordova-js. This project hosts the core js elements, and builds the platform specific cordova.js lib
Any plugin api's your app wants to interact with must be pre-installed into the Native App
any plugin with native code will have to be added to the project and deployed to device bundled inside the app. There is no way to lazyload native code. The js portions of the plugin could be hosted on your server, however.
More information, some apps that do this
The PhoneGap Developer App uses a similar technique to what is describe above and what you want. The only difference is that it is meant as a dev tool, and the server is a local dev machine.
The Cordova App Harness also uses this technique of pre-bundling an app package with plugins, to be consumed by remotely hosted resources
You cannot, deviceready only functioning if the app run on mobile phone environment only. If web based or dekstop application, it won't trigger.
No , dont do that . loading remote website will not able to intract with your plugins . and the app will get rejected on istore too

Phonegap's Facebook Connect plugin - making it work with web app as well as native apps?

I've got the FB Connect plugin working with my Phonegap project native apps, but now I'm wondering what the workflow is for making it work with the web-app version.
When I run the web-app version, I get the standard Phonegap FB Connect errors, the last one being 'FB variable does not exist. Check that you have included the Facebook JS SDK file.' - this makes sense, as my web app doesn't have those js files, as they get injected during the PG Build process.
So what is the typical way of moving forward at that point? Can I use that last error as a way of determining 'ok, this is the web-app version, not native', and then what do I do next? Should have the Facebook SDK installed on my web-app?
Cheers
The git repo has steps for including the plugin in web app
Web App
www/js/facebookConnectPlugin.js contains the JavaScript SDK and API file. The API matches as close as possible to the native APIs.
Setup Web App Example
Host the www folder on a server and configure your Facebook dashboard correctly to test the Web APIs. Most people use Parse for easy testing.
NOTE : Developers should call facebookConnectPlugin.browserInit() before login - Web App ONLY
https://github.com/phonegap/phonegap-facebook-plugin

Can I create Background Services on Android using Phonegap Build?

I have been developing a phonegap application (HTML/jQuery) for Android devices and packing it in Phonegap Build.
I have a demand of having a background service that keep sending data to our web services every 1 minute. As far as I heard, it's only possible developing the background service in Java and communicating with the UI somehow.
My background is in .NET, so my question is: Is there another way of doing that apart from Java? Any good tutorial?
If not, Can I still keep using PhoneGap Build to pack the UI and the Background Service? Or do I have to have the whole Phonegap SDK installed in my machine?
You can't do it by Phonegap Build!
You have to install the whole set of tools (eclipse, android sdk and cordova), and then develop the service in Java, adding your HTML assets into the project. So that you'll get able to generate the APK containg Background Service and Webapp.