Top
Best
New

Posted by MrVandemar 3 days ago

Your 'app' could have been a webpage (so I fixed it for you)(danq.me)
696 points | 429 commentspage 5
Magicrafter13 10 hours ago|
100% agree with this.

I've been wanting to write an article on a very similar topic myself for some time now. Perhaps I'll finish it and share it here. Absolutely done with this modern 'convenience' and app culture.

khalic 9 hours ago||
I’ll always remember that dumb Wired headline screaming “the web is dead” a decade or so ago… nah I’m happy with whatever crappy webpage, thank you very much
user2722 7 hours ago||
I thought he had created an website which ran an APK server-side and was loadable in a browser. Oh well.
qurren 8 hours ago||
The absolute worst is the rare Wi-Fi hotspots in China that require you to install an app in order to connect to the Wi-Fi.
ChrisMarshallNY 13 hours ago||
If that's the case, then I agree. Lots of crapplets should be Web pages (for example, almost every corporate app).

However, there's a lot of stuff that does, indeed, require a native app.

That's the stuff I like to do. Doesn't really scale to Web pages.

bobro 12 hours ago|
examples?
ChrisMarshallNY 11 hours ago||
Nah, you can look at my GH profile, where I link to some open stuff, but I’m working on apps for a specialized demographic, right now, that don’t benefit from being HN hugged.
ChrisMarshallNY 7 hours ago||
Oh, heck. I just realized this was a PWA booster challenge.

Definitely nah. Life’s too short, and I’m already in the back nine.

Sorry. I should have known better, and refrained from commenting at all.

My bad. I thought it was a serious attempt at engagement. I enjoyed the post, and didn't really read the comments before posting.

Have a great day!

> Never wrestle with a pig. You both get dirty, but the pig likes it.

cindyllm 5 hours ago||
[dead]
esjeon 7 hours ago||
App = Information × Interface = User Experience

It's ×(multiplication), not +(plus). Interface is not simply overlaid on Information; it actively changes how information is perceived and used, thus User Experience (UX).

Users have limited screen space, attention time, context retention, etc. So, apps must be wise about what information matters at any given moment, and make the best out of those limited resources.

Developers have been crazy about this: A/B testing, CVR, retention, churn, LTV, ARPU, DAU/MAU, North Star Metrics. Deploy and analyze, develop and optimize, rinse and repeat, and apps end up as revenue-generating machines.

A side effect of this optimization loop is that, apps become a designed thinking process for users. Apps decide what to show, what to hide, what to emphasize, and what comes next. They actively shape how people see and think, all to lure them into spending money.

So, "this could have been a webpage" misses the point of what apps are for, and, by extension, who apps are for.

Still, I see a bit of potential here. Document is a natural user interface -- almost all apps, including even SPAs, have document-like or document-driven views. Perhaps we've been too obsessed with computer-program-like UI. Documents can always be dynamic and interactive without being overdesigned. Perhaps this is what folks wanted to point out.

maelito 13 hours ago||
Of course it should have been a Webpage. You can even code a whole modern map application on the Web, that's under 3 Mo gzipped, instead of the 600 Mo Java applications that we're served.
david-moore 12 hours ago||
If you're having any trouble loading it, it is cached here: https://archive.ph/ByFBN
Dwedit 12 hours ago||
A webpage cannot harvest your personal data in ways that an app can.
amelius 9 hours ago|
Someone should design a webpage that can run native iOS/Android apps. That will teach them.
More comments...