is progressive web Applications are as easy as in ...
# cfml-general
g
is progressive web Applications are as easy as in coldfusion as they show in youtube videos for .net
a
Progressive Web Applications are not really anything to do with the server side technology. Sure you can create an API in server side language 'x'.
s
We have a PWA that is launched from a CFM page. But the only CFML is on the launch page. Everything else is JS/HTML/CSS.
g
the question i asked because we have a very big site connected to mysql and its not using much apis, so in that case, is it a possibility
a
PWAs use web workers to fetch data in the background (when connected to the web) so it's not easy to convert and existing traditional web application (in any lang) to a PWA. Are you actually looking to build something with offline support?
e
The real question I would ask is : what is to be gained by developing your app into a pwa? If you really need it to be a PWA then you may want to talk to the commandboxfolks such as @bdw429s as commandbox is very close as you can get to being a PWA as any coldfusion product that I have seen.
a
How does commandbox make it a PWA?
g
@aliaspooryorik yes offline support, its a task and we have timeline for it, so we want to explore first and see how complicated can it get to make it a PWA,
@yes how commandbox can generate PWA
a
Can you share the video where they are doing it with .net easily? I'd imagine the app is built with a decoupled front end and then powered by APIs but interesting to see if that's the case.
g

https://www.youtube.com/watch?v=47L5LjYlZWA&pp=ygUcUFdBIHdpdGggLm5ldCB3aXRoIGt1ZHZlbmthdA%3D%3Dโ–พ

a
OK - that video is using Blazor, so it's basically a JS / HTML front end which talks to the server via an API and then stores data locally to work offline.
s
@Evil Ware What do you think PWA stands for and why do you think that CommandBox has anything to do with it?
g
So all in all it seems itโ€™s not an easy task which video shows using .net especially for coldfusion
s
Define "easy". A lot of apps these days are built with an interactive (JS) frontend and just make API calls to the backend to fetch data and update stuff.
@gsr This will give you an idea of what you're in for, in terms of work: https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps
g
@seancorfield its a legacy app, not a modern UI based vue or react product which uses API, so i am sure it will take time, that is where the work "easy" is used
s
Yeah, that's going to be a lot of work, unfortunately.
e
1. "here is what I stated" PWA then you may want to talk to the commandboxfolks such as @bdw429s as commandbox is very close as you can get to being a PWA as any coldfusion product that I have seen."" -- CLOSE, under the hood, command box just downloaded, and run, what does it do, it can run as a self-contained binary, it creates a icon to further control its running (at least Windows platform).With zero modification, it runs as an interactive shell, has the ability to query remote server, update itself, grab github and forge box content. Its close, would it need modification, absolutely, but Its freaking close, So everyone is on "What Does EVILWARE THINK IS A PWA" here1 . Web Technologies 2. Responsiveness 3. Offline Capabilities 4. App-Like Experience 5. Progressive Enhancement 6. Secure 7. Discoverability 8. Push Notifications 9. App Manifest 10. Installation 11. Updates Since, there is a diconnect on what I believe makes commandbox LIke a PWA, at least on a windows OS, 1 > web technology, at its core its running a java web server, 2, Command line interface does somehing when text is input, 3, It runs offline, 4, It is like dos /unix . 5. GitHub, ForgeBox, Switching of server engines ,6, Yes its secure, 7, Yes,, 8, Arguablity Yes, 9, Arguablity Yes, 10, It has an installer, or self contained binary, 11, Updates are regular. Would it need work to turn some old website into a modern desktop PWA, yes.
g
I have to say they seems to include everything and created an msi file Not sure on pwa
a
That's not a PWA (or not in any definition I'm aware of ๐Ÿ™‚ ). A PWA to me is a website that runs in a web browser (like any website does), the key bit here though is that from the browser you can choose to install it on your device and you get a nice little icon etc, which when you click it opens up as an app (but is really a web browser). If you have connectivity then it goes off and gets the latest data. If you don't have connectivity then it uses the data it had when it was last connected. It uses the browsers local storage to do this. The idea is that you can deliver an "app like" experience to end users without having to distribute an app.
Just double checked I wasn't spouting nonsense and the wikipedia article matches my understanding of what a PWA is https://en.wikipedia.org/wiki/Progressive_web_app
As an example, if you hit the "x" website (which for some reason is on a domain called twitter.com - dunno why,,,, ๐Ÿ˜› ) you see the option to install it as a PWA. https://ibb.co/N9JJq2y
I assumed that is what you wanted when you asked about a Progressive Web App @gsr ?
g
yyes
s
(all of that still has absolutely nothing to do with CommandBox @Evil Ware)
For a PWA to operate offline and be "app-like" on a device, it needs to be primarily JS -- with API calls to fetch data from remote servers when it is online and the ability to use local storage (on the device). In other words, a "traditional" server-side rendered HTML app cannot be a PWA, no matter what server it is running on.
e
Okay Sean, from your perspective Commandbox is just a binary that has Nothing to do with PWAs, forget its binary like features, that it runs on Java,. Instead, let's just go back to Coldfusion, from adobe: https://helpx.adobe.com/coldfusion/mobile-application-development/building-mobile-applications.html
s
CommandBox is a way to run Lucee and ACF on a server. Nothing to do with PWAs.
a
That MDN article appears to back up what the wikipedia article states. If you read how to install a PWA guide on MDN https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Making_PWAs_installable or the section on the "Web App Manifest" in the smashing mag article it's saying the same thing as the Wikipedia article. The adobe and simplelearn articles don't really say much about the technical definition of a PWA.
That 2nd Adobe article is about the ill-fated cfclient tag which used PhoneGap to build and is not related to PWAs at all.