Live data from Hacker News

Your 'app' could have been a webpage (so I fixed it for you)

danq.me

341–350 of 571 posts

Re: Your 'app' could have been a webpage (so I fixed it for you)

#341
post #278

I once read that app users are seven times more profitable than web users. That easily answers the author's question about why a company would bother make an app when a web page is the natural fit for the use case. I don't remember the source or methodology for that number, but I have no trouble believing it. An app gives the developer a foothold on the user's device. It can more easily send notifications, track the…

Apps bypass ad and tracking blockers too. They do have OS permissions as a potential roadblock, but most users just click "OK" on those prompts the first time when they install or open the app.

Re: Your 'app' could have been a webpage (so I fixed it for you)

#342

Nobody here is talking about the fact that a significant number of users want apps, too. I'm responsible for an internal tool at the company I work for, hosted as a website, that handles a bunch of miscellaneous tasks that other employees need. Think reimbursements, documentation and reporting, gathering and presenting business data. That sort of thing. When I took it over, it was desktop only ( a lot of formatted pa…

I really wish PWAs were more well-known among average users. If people knew and expected they could install certain websites as apps, that would simplify things so much and really balance the power of the app stores.

Unfortunately apple accomplished their goal of killing that entire idea. The time for it to take off was 10 years ago. They begrudgingly support it now but it's too late. gg

Re: Your 'app' could have been a webpage (so I fixed it for you)

#343
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.

Re: Your 'app' could have been a webpage (so I fixed it for you)

#344
post #303

I recently decided to publish an app on the App Store just so I could say I accomplished that, and maybe even make a little bit of beer money on the side. Now, I’ll be the first to admit that my actual app is pretty much garbage. I don’t expect it to be popular. It’s basically a worse version of stuff that is already available. I expected this to be a learning exercise about the process of getting stuff published. Lo…

I did something similar, for similar reasons. In the end I just did whatever to get it published. If you show up at my door, I'll pour you your choice of beer/coffee. But I agree, it feels very invasive! On the web side of things DNS only recently started being more private - 10+ years ago it was common to have your phone + postal address on whois. Two take aways from my experience 1. I'm happy that I invested more i…

>10+ years ago it was common to have your phone + postal address on whois

This is the .dk TLD today, and it's the reason I've never posted my website here. The .dk registry (punktum.dk) is run by absolute clowns.

On the other hand, the first thing I do before spending money on a danish website is "whois eksempel.dk", and if it doesn't return a danish address (and wasn't created recently), I'm out.

Re: Your 'app' could have been a webpage (so I fixed it for you)

#345

Earlier quoted context omitted.

That sounds less like wanting apps, than simply having no idea what's going on.

Honestly, they probably would have been perfectly happy with a bookmark on their home screen, but have you ever tried walking someone who doesn't know how to enter a url into their browser through the process of making a home page bookmark on their phone? Ultimately I ended up making a PWA that does nothing except act as a bookmark. Which was way more of a PITA than it should have been.

Sounds like what could be a useful built-in OS feature. Along the lines of:

"Aim camera at QR code to put "open-link" icon on your home screen"

Does something like that not exist?

Re: Your 'app' could have been a webpage (so I fixed it for you)

#346

Earlier quoted context omitted.

It's because apple pushed towards apps and didn't want web apps on their phone. Likely due to the profits they can gain from appstore sales Native apps would be the better platform in my eyes if the Operating Systems would be better in terms of letting a user manage what a native app have access to and can do. But currently they are preferred by companies despite more dev effort because they can get more user data wi…

You're not wrong at all, but it's interesting that iOS launched with only web app support for third party software, and it took community pressure to persuade them to support native apps. There was not even an app store to begin with.

Pretty much every single feature added in the early days (and later) of ios was simply copying what was popular on cydia. That well started to run dry as they got better at whack a moleing jailbreaking exploits, severely contracting that community of tweak developers, and we've seen the resulting product stagnation for some time now.

Re: Your 'app' could have been a webpage (so I fixed it for you)

#348
post #147

Earlier quoted context omitted.

examples?

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.

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.

Re: Your 'app' could have been a webpage (so I fixed it for you)

#350
post #77
post #33

Earlier quoted context omitted.

Apps took off because Apple did everything they could to make PWAs work badly, with no reliable notifications, no access to some data, etc. Apple did that because they want their sweet 30% from in-app purchases, which they couldn't enforce in PWAs.

apps took off before browsers had the capabilities required for native-like behaviour (fast graphics, hw functionality, notifications) and then were used even for apps that could have been web-apps.

When apps took off they weren't really making use of any of that either. Top apps back then were either using the standard ux libraries, or they were something like a simulated beer pint. Rehashing of popular flash and flip phone games like bejeweled.
Post reply on HN