Personally I find that the in browser storage is really adequate for just about anything. Local and Session is what I use most and being key->value stores, you can do much with it.
I did build a solution based on storing "tasks" locally when offline, and when the browser goes online, would run through those task sending them to the main server.
These days I've become spoilt with using Firebase's Firestore NoSQL backend as it handles all the offline support right out of the box, nothing extra to be done by you. It just works. (Free for small projects)
You could also look at some abstraction packages for the browser localstores, something like LocalForage comes to mind. It handles json and also blobs amongst other types.
I've already used LocalForage and I got the job done.
But now I'm searching for a wider solution to overcome the various limits imposed by the browser (they are there for security reasons, of course).
So I'm looking for a solution where the app in the browser could talk with a local process acting as a web server running in the Android device. In this way all operations could be possible, including reading/writing files, access any relational db (SQL), etc...
I'd like such process was a NodeJS instance :)
However, I'm very grateful for your response.
God bless
I forgot to mention PouchDB, that's nice.
It is an auto synchronising db, but if you really need SQL, then...
It sounds like you are looking for something like WebSQL, but that has been deprecated due to difficulties in standardising, but it still seems to work across many devices.
For reading and writing files, Filesystem-API will work. You can request permission to store files on the client.
Maybe you should look at what you can do with a ServiceWorker to proxy the outgoing connection.
So, ServiceWorker that writes to WebSQL and FileSystem sounds like what you are after.
I would thank you for your kind help, Jaaki; it's much valuable.
I've used some of the solution you propose, except ServiceWorker; it is not so plain for me, I don't "feel" it :( furthermore PWAs in general mandate the use of https, so certificates and so on..
But I ultimately would escape the browser world, 'cause it currently has severe limitations (also in Filesystem API, which I've tried) and more of them may come in the future due to security reasons.
So I'm looking for a solution like the one that I've outlined in my original post as "new scenario".
Do you have any hints on it? (but maybe you are a front-end man and not a full-stack one ...)
Thanks again, Jaaki. Have nice days.
Nando
Service workers basically replaced AppCache.
I think you should take a look at them in detail as they are a major component in the offline system.
"New Scenario" looks like you want a PWA plus a native app (local server) in the background to bypass security constraints of the browser system. Bad idea!
Maybe, if you want the PWA to act like a native app, it should in actual fact BE a native app, but it is hard for me to suggest what you should do because I don't understand exactly what you want to do and whether the Filesystem-api etc. is in fact to limiting for what you are trying to accomplish.
Hi Jaaki.
I think that a native app can do anything it is needed without suffering of limitations. It's not so for a web app, due to (legitimate) browser constraints.
If I could develop a native app I could do things that I'm not able to do in the browser, right? So, I thought it was possible to combine the two: where is the bad?
However, I will try in some other way; I've found an interesting app named AndroidJS; maybe it's a possible solution.
Thanks again for your help
God bless
Yes, PWA runs in a sandbox, probably always will.
Native app is much more powerful.
You should then look at the new Ionic 4 framework. It is a favourite for many developers who are testing new products. It now allows you to use much of your existing Vue app inside a Hybrid environment. You can add plugins like SQlite, but then you have to deploy it through the AppStore/Google Play, so you need to pay developer fees etc.
A quick overview:
PWA (browsers only), runs in limited sandbox, but is easy to deploy. (Push to webserver takes 2 minutes for update)
Native App, most powerful with best performance. Deploy through AppStores/PlayStore, takes long to update.
Hybrid Apps, sits somewhere in between. Performance not so good, but getting better. If you want native plugins like bluetooth and sensors or SQLite, you have to deploy to AppStore/PlayStore.
If you build a basic system, (sand boxed browser), deploy to webserver is possible.
I had some experience with Cordova, but the apps were just painfully slow.
Hi Jaaki,
I've read carefully your explanation.
The current version of my app is of the Hybrid type, then it suffers of running in the browser sandbox, but may use AppCache and LocalStorage.
The major problem I have is caused by the mandatory use of https in the last versions of browsers; https doesn't accept the use of the AppCache :(
I don't absolutely like the use of ServiceWorkers as workaround for the AppCache.
This fact, togheter with other possible future limitations imposed by the browsers, pushed me to search an alternative solution as described in "new scenario".
I would like to find a way to proxy to a local app the operations that cannot be executed natively in the browser or are better executed in background.
I would hearthly thank you for your kind help, Jaaki.
Have nice days
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Personally I find that the in browser storage is really adequate for just about anything. Local and Session is what I use most and being key->value stores, you can do much with it.
I did build a solution based on storing "tasks" locally when offline, and when the browser goes online, would run through those task sending them to the main server.
These days I've become spoilt with using Firebase's Firestore NoSQL backend as it handles all the offline support right out of the box, nothing extra to be done by you. It just works. (Free for small projects)
You could also look at some abstraction packages for the browser localstores, something like LocalForage comes to mind. It handles json and also blobs amongst other types.
Thank you for your reply, Jaaki.
I've already used LocalForage and I got the job done.
But now I'm searching for a wider solution to overcome the various limits imposed by the browser (they are there for security reasons, of course).
So I'm looking for a solution where the app in the browser could talk with a local process acting as a web server running in the Android device. In this way all operations could be possible, including reading/writing files, access any relational db (SQL), etc...
I'd like such process was a NodeJS instance :)
However, I'm very grateful for your response.
God bless
I forgot to mention PouchDB, that's nice.
It is an auto synchronising db, but if you really need SQL, then...
It sounds like you are looking for something like WebSQL, but that has been deprecated due to difficulties in standardising, but it still seems to work across many devices.
For reading and writing files, Filesystem-API will work. You can request permission to store files on the client.
Maybe you should look at what you can do with a ServiceWorker to proxy the outgoing connection.
So, ServiceWorker that writes to WebSQL and FileSystem sounds like what you are after.
I would thank you for your kind help, Jaaki; it's much valuable.
I've used some of the solution you propose, except ServiceWorker; it is not so plain for me, I don't "feel" it :( furthermore PWAs in general mandate the use of https, so certificates and so on..
But I ultimately would escape the browser world, 'cause it currently has severe limitations (also in Filesystem API, which I've tried) and more of them may come in the future due to security reasons.
So I'm looking for a solution like the one that I've outlined in my original post as "new scenario".
Do you have any hints on it? (but maybe you are a front-end man and not a full-stack one ...)
Thanks again, Jaaki. Have nice days.
Nando
Service workers basically replaced AppCache.
I think you should take a look at them in detail as they are a major component in the offline system.
"New Scenario" looks like you want a PWA plus a native app (local server) in the background to bypass security constraints of the browser system. Bad idea!
Maybe, if you want the PWA to act like a native app, it should in actual fact BE a native app, but it is hard for me to suggest what you should do because I don't understand exactly what you want to do and whether the Filesystem-api etc. is in fact to limiting for what you are trying to accomplish.
Hi Jaaki.
I think that a native app can do anything it is needed without suffering of limitations. It's not so for a web app, due to (legitimate) browser constraints.
If I could develop a native app I could do things that I'm not able to do in the browser, right? So, I thought it was possible to combine the two: where is the bad?
However, I will try in some other way; I've found an interesting app named AndroidJS; maybe it's a possible solution.
Thanks again for your help
God bless
Yes, PWA runs in a sandbox, probably always will.
Native app is much more powerful.
You should then look at the new Ionic 4 framework. It is a favourite for many developers who are testing new products. It now allows you to use much of your existing Vue app inside a Hybrid environment. You can add plugins like SQlite, but then you have to deploy it through the AppStore/Google Play, so you need to pay developer fees etc.
A quick overview:
PWA (browsers only), runs in limited sandbox, but is easy to deploy. (Push to webserver takes 2 minutes for update)
Native App, most powerful with best performance. Deploy through AppStores/PlayStore, takes long to update.
Hybrid Apps, sits somewhere in between. Performance not so good, but getting better. If you want native plugins like bluetooth and sensors or SQLite, you have to deploy to AppStore/PlayStore.
If you build a basic system, (sand boxed browser), deploy to webserver is possible.
I had some experience with Cordova, but the apps were just painfully slow.
Hi Jaaki,
I've read carefully your explanation.
The current version of my app is of the Hybrid type, then it suffers of running in the browser sandbox, but may use AppCache and LocalStorage.
The major problem I have is caused by the mandatory use of https in the last versions of browsers; https doesn't accept the use of the AppCache :(
I don't absolutely like the use of ServiceWorkers as workaround for the AppCache.
This fact, togheter with other possible future limitations imposed by the browsers, pushed me to search an alternative solution as described in "new scenario".
I would like to find a way to proxy to a local app the operations that cannot be executed natively in the browser or are better executed in background.
I would hearthly thank you for your kind help, Jaaki.
Have nice days