You know what really irks me? Lately people are using the terms “website” and “app” synonymously and there’s just no reason for it.
I was on the phone with customer service for my grandmother a few weeks ago, and the agent on the phone kept saying that my grandmother needed to go “on the app” to set her router name. I went three rounds with the agent explaining that my 94-year-old grandmother didn’t really have a phone capable getting to the app before I realized that the agent meant website, but was still saying “app”.
The improper usage of the words is far more an issue than the discussion about whether JavaScript is creating an application experience that is no longer a “website”.
I get that my generation is aging out of the “target audience” for tons of things, but I’m willing to stand my ground on this one til the day I die. An app and a website are two different things. 😡
Another one that gets me is “portal”. I’m often asked to create a this portal or that portal, but once I finally get them to describe the requirements it’s just a standard web form or static web page.
Webapp is pretty well understood though. As long as there has been WWW there have been webapps.
Well that’s just goes back to the crux of the article. At what point is the web_site_ a web_app_?
But, more to the point “app” entered the casual lexicon about 15 years when smartphones became ubiquitous. If you’re speaking to someone and they say “is there a web_site_ I can use, like on a laptop?” and they respond with “yes, there’s an app”, it’s not a matter of webapp versus website, but of lack of understanding that not everything that showcases the internet is an “app”.
Web developer here.
If your site has a lot of interactivity, it is a web app.
A read-only site like Wikipedia is not a web app.
A store page is not a web app.
Your bank’s customer portal is a web app.
Facebook, Lemmy, Reddit, Twitter, etc. are web apps because they provide a lot of interactivity.
I agree that the line between web apps and websites is blurry, but my thinking is if a website is built mostly using front-end technologies, it is a web app, if it’s built mostly with JSP or PHP, it’s a website. Things like the WordPress admin panel blur the line between the two as they offer lots of interactivity, but is mostly PHP-based.
But, more to the point “app” entered the casual lexicon about 15 years when smartphones became ubiquitous.
The term “application” has had a well understood meaning for far longer than that. That’s simply when people started conflating “app” with “mobile app” due to some clever marketing by "App"le.
If you’re speaking to someone and they say “is there a web_site_ I can use, like on a laptop?” and they respond with “yes, there’s an app”
I think that answer would be pretty unambiguous. If you hear that answer after asking that question and your first thought is that they mean “smartphone app”, you could just ask “is it a smartphone app or web app?” But if you had already told them you wanted to access something from a laptop and they tell you there is an “app” then you can normally safely assume that it’s not a mobile app.
As an engineer who builds web sites / apps, I can assure you that no, they are not two different things.
For instance, the non profit news organization that I’m working for right now has a website, an android app and an iOS app, with all three being created from the exact same code base that is mostly JavaScript files.
Hell if you have to use the Google Chat app for work (their equivalent of slack / teams), you install it by literally just adding the website to your desktop.
Hell, with new additions to browsers like Web Assembly, and WebGL, you can literally run custom low level assembly or c++ style code in a web browser, code that is just as efficient as native code running directly on the OS.
The primary difference between a website and an app is just the method of distribution (how it’s code gets to your phone).
As a software developer a website is not an app and a web app is not an app. A web app is a hybrid solution and calling it just an app is pure confusion for the end users. Always refer to your web app as a website for end users unless you want them to literally install an application.
Just saying ‘nuh uh they’re different’ is not an argument or a rebuttal to my point that the code running them is literally identical.
When you’re using Figma online that’s just a website? That’s not literally the entire Figma app running in web assembly?
Yeah, the method of how a user gets a web app installed is different, but there is no real difference between the actual code of a web app and a natively installed app.
Paper and cutting boards come from the exact same trees. However when I tell you to use a cutting board instead of cutting on the table, somehow everybody knows that they shouldn’t use paper
They’d be a lot more of them if iPhone supported the technology better.
I say that as someone who’s pitched PWAs to companies, but since many of the managers and owners seem to be in on the Apple ecosystem, demos often aren’t that impressive. Having to answer “kinda” to can they do x questions doesn’t go down well.
PWAs are still a thing, we’re just waiting for Apple to open the walled garden.
I’m excited for PWAs personally as this will allow everyday apps to run on devices not running Android or iOS, like Linux phones.
They’re still a thing. If your work uses Google Chat instead of Slack / Teams the only way to install an app version is as a PWA. A company I recently worked for just got most people to use the Outlook PWA instead of the traditional desktop client, and I frequently use Spotify and Soundcloud’s PWAs. One of the more popular backend API testing apps is hopscotch which is entirely a PWA, and this was also written on Voyager for Lemmy.
