Now that CouchDB and PouchDB are heading to Wappler, what are the reasons to build native Android/iOS apps or a PWA? I was thinking I needed to build a native app in order to have all the device functionality but will always have the hassle of app store approval, updates, etc. not to mention the extra cost (minimal in the great scheme of things but there nonetheless).
But it looks like PWAs are offering access to hardware (camera, local data storage, GPS location, etc.) so that is looking increasingly appealing.
On the basis I need it to behave like an app, use the camera for things like QR code scanning, be able to work when there is no internet connection, sync offline data when back onlineā¦ would a PWA be a good solution?
PWAs are becoming increasingly powerful, especially now Apple have allowed Push Notifications for apps added to Home Screens. I would say, though, that there is a certain trust that comes with an app from an app store vs a website. Also, most peopleās initial instinct when looking for an app is to go to their deviceās app store rather than visiting a website. A lot depends on your intended audienceā¦
Yes, Progressive Web App. You can add it to your mobile homescreen to sit with the other apps and it will look much like a native app, too. Itās stored locally, too, so should work without an internet connection (can someone correct me if Iām wrong about that?) But the key difference is itās not under the authority of the app stores so there isnāt a risk of it being rejected or any long delays publishing updates. We remain in 100% control of it.
Very good points. In my case, the app is for company staff to use rather than the general public so none of these issues apply to this particular project. And it will be so easy to just email or message a link to the PWA with instructions on how to add it to their home screen.
Iām assuming that came from someone invested in PWAs
It isnāt wrong, but misses off lots of the device feature access that native apps provide. Although many are increasingly available to PWAs a lot still arenāt
Is anyone able to confirm what can and cannot be done in PWAs? Iām trying to establish the way to proceed trying to avoid finding out something key when Iām already down the road of developing it.
For me, the key requirements are local data storage, syncing back to the web server db when reconnecting after being offline, use of camera for both photo storage and QR code scanning, GPS location tracking.
That would be pretty game changing. Does anyone know if we can use PouchDB as offline DB only i.e no synching to CouchDB at all. It would be lovely to then not need to worry about any GDPR for a couple of app ideas I have
Yes of course you can use PouchDB only, as a local database. Just create a connection in the database manager, using PouchDB only (not CouchDB and PouchDB).
you can always let the builder check it for youā¦ and then create the files to upload to a App Store.
I did try this ā¦ BUT with all the āquestionsā and red tape in the app storeā¦ i just opted for a PWAā¦ as you saidā¦ dont have all the other points aboveā¦ BUT as I update the siteā¦ so does the PWAā¦
I have a fully working PWA site for my clients ā¦ I do not require offline syc or storage of the database because of the nature of the use of the app.
Having dipped my toe in the app store waters a couple of times now Iām leaning more and more towards PWA. I found it a hassle to maintain Apple, Android and Microsoft accounts to package up to the respective stores. In addition, we had to purchase Apple specific hardware to allow us to upload to their AppStore.
PWAs are less hassle with updating and more flexible for our own needs. Operating offline is no problem, a service worker looks after that and is straightforward to implement:
You can also choose local device storage and with the new Wappler updates couch/pouch integration should give even more flexibility.
Whilst the takeup of PWAs among the big players has been slower than many have liked, recent advances have made the usage case for PWAs a lot stronger in my opinion - especially the push notifications that @bpj mentioned above - that was a game changer for us.
As far as I can see, the only downside for us is the way the PWA is stored to the users home screen, its a little bit more of a hassle for them to add to their device - this is manageable in a couple of ways so there are solutions there to choose from.
We deal a lot with B2B with only a small portion B2C so the ability to have a āpackagedā standalone installable desktop app was a great boost in addition to the above points.
Some excellent responses which are really helpful. It feels like Iām 99% decided on going the PWA route. The negatives wonāt apply for the project I need to build. I donāt need bluetooth connectivity or touch/face ID, and the slightly more quirky installing onto the home screen shouldnāt be an issue as the app will be used entirely by staff so I can provide concise instructions. If customers will be using anything then it will just be as a normal website.
Just so I know for sureā¦ Couch/PouchDB will work with a PWA, wonāt it? The ability to work offline is probably the most crucial aspect of this. Staff will be in location where there is no mobile signal so they need to be able to open job records and update them and then have it all sync back to the server when a connection is available again.
