janjonas, in the company I work we had a similar problem with Windows Mobile 6.x, and we use pretty much the same solution pointed by EboMike: The main app check if it’s updated, against a WebService. It receives the current version & the URL from where download the new version, if necessary. The main app … Read more
Step 1: Add dependency (build.gradle (app)): dependencies { implementation ‘com.google.android.play:core:1.7.3′ … } Step 2: Check for update availability and start if it’s available private AppUpdateManager mAppUpdateManager; private static final int RC_APP_UPDATE = 11; In onStart() method: mAppUpdateManager = AppUpdateManagerFactory.create(this); mAppUpdateManager.registerListener(installStateUpdatedListener); mAppUpdateManager.getAppUpdateInfo().addOnSuccessListener(appUpdateInfo -> { if (appUpdateInfo.updateAvailability() == UpdateAvailability.UPDATE_AVAILABLE && appUpdateInfo.isUpdateTypeAllowed(AppUpdateType.FLEXIBLE /*AppUpdateType.IMMEDIATE*/)){ try { mAppUpdateManager.startUpdateFlowForResult( appUpdateInfo, AppUpdateType.FLEXIBLE … Read more
We use Omaha for our products. Initially there was quite a bit of work to change hardcoded URLs and strings. We also had to implement the server ourselves, because there was not yet an open source implementation. Today, I would use omaha-server. There are no regrets with ditching our old client update solution and going … Read more
To replicate this update behavior you need two things: An updater application which checks for updates regularly. If an update is found it should install it automatically. Most commercial setup authoring tools include good updater applications. You can try writing an updater yourself, but it’s not as easy as it sounds. Per-user installations for each … Read more
Note: As of Firefox 57, and Chrome 68, as well as the versions of Safari and Edge that support service workers, the default behavior has changed to account for the updated service worker specification. In those browsers, HTTP cache directives will, by default, be ignored when checking the service worker script for updates. The description … Read more
I think that “language agnostic” is going to be a limiting factor here. Applications come in so many shapes and sizes that there is no one-size-fits-all answer. I have implemented several auto-updaters in several languages, and no two were similar. The most general philosophy is that the application checks with some home location (web address, … Read more
That sounds like a simple webview caching mechanism to me. The following should do what you are looking for: WebView webView = new WebView( context ); webView.getSettings().setAppCacheMaxSize( 5 * 1024 * 1024 ); // 5MB webView.getSettings().setAppCachePath( getApplicationContext().getCacheDir().getAbsolutePath() ); webView.getSettings().setAllowFileAccess( true ); webView.getSettings().setAppCacheEnabled( true ); webView.getSettings().setJavaScriptEnabled( true ); webView.getSettings().setCacheMode( WebSettings.LOAD_DEFAULT ); // load online by default … Read more
Currently this defaults to 5 hours (based on the code here). You can override this by launching chrome with the extensions-update-frequency command-line parameter, which is the frequency in seconds. And you can go to chrome://extensions, tick the Developer mode checkbox at the top right, then press the Update Extensions Now button Chrome docs doesn’t specify … Read more
The basic structure of a solution is as follows: There is a main loop responsible for repeatedly loading the latest version of the app (if required) and launching it. The application does its thing, but periodically checks the download URL. If it detects a new version it exits back to the launcher. There are a … Read more
No cache scenario (No Service worker): Your PWA app will be cached only when you use Service worker. Manifest.json will help adding your web app to home screen with a icon and open without address bar. If you don’t have a service worker or if your browser don’t support it, web page will be loaded … Read more