this post was submitted on 04 Jan 2024
71 points (94.9% liked)
Technology
59605 readers
3501 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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. 😡
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.