Live data from Hacker News

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

danq.me

541–550 of 571 posts

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

#541

Earlier quoted context omitted.

> my actual app is pretty much garbage The app review process is explicitly meant to keep out garbage apps. Sounds like it worked as designed?

> Sounds like it worked as designed? It didn't, because his admittedly garbage app ended up on the app store, because the app review process doesn't actually keep out garbage apps.

Hm, I see your point, about it needing to be more restrictive.

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

#542
post #536
post #516

Earlier quoted context omitted.

webapps are inefficient, clunky, slow substitutes to actual native apps. I think decades of marketing and billions spent by Google trying to convince people that webapps are better is what makes many tech people think they are. Literally. People "want" webapps to be what users "wanted" bc it pays their salary...

That's clever rhetoric, but for most use cases it's just not true, and that's the point of the original article. There are legitimate use cases for native apps, but many of them could be converted to an instantly loading, 50-100KB web page without losing any functionality. As opposed to a 50-300MB native app, which you need a fast connection to install, and starts up more slowly than the web page every time you use i…

You’re doing native apps wrong if they’re 300mb. And also no web app in 2026 is just 50kb!

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

#544
post #530

Earlier quoted context omitted.

Electron and React apps, perhaps. It's completely feasible to build a webapp that is lightweight. I have done it several times.

put the same optimization effort into a native app

Why?

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

#545
post #66

Earlier quoted context omitted.

> While the app is awake, sure. That's not true. The browser's push service wakes the service worker on delivery, even if the PWA is fully closed. That's the entire point of Push API vs polling.

And the OS will never background the browser for battery optimization reasons? Genuine question, I'm not an expert on mobile OSs (as you already guessed).

The notification daemon lives in a separate process.

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

#546
post #226

Earlier quoted context omitted.

> Down to the manufacturer of the whole product you're buying. In case of an app, what is the "product" you are buying? Because according to Apple, they add a lot of "value" by ensuring the software is safe, performant, etc etc. Am I not buying "a safe, checked app"? Or am I buying an app and then separately pay Apple for an added service of "checking the app for safety" etc etc. I'd very much presume the first. But…

> Am I not buying "a safe, checked app"? I wouldn't presume that. Malware ends up in the app store all the time.

I was merely re-iterating the marketing from Apple on why they charge the 30%.

I personally think it's a lie at best, or a scam (on multinational level) at worst. I've always been convinced that regulation should force companies that make such statements to be held responsible. Treat them like an insurance company or such.

I pay a few dollars every month to be protected against scams and malware. So when I do get infected, Apple failed to do what I paid it for and Apple should be forced to pay me for damages.

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

#547
post #510

Earlier quoted context omitted.

This is wrong. The most important reasons why I prefer mobile apps are the same as why I prefer desktop programs. - I can download it once and then use it. - I can see when it gets updated (versus a website that gets updated every time I load it). For security reasons it's better, I can even verify my app with other people online and make sure we run the same thing. - End-to-end encryption doesn't make much sense in…

1. You can download & install PWAs for offline use too. 2. This isn't true for apps anymore. Server driven ui is a thing. 3. JS runs locally. You can inspect the network traffic more easily than you can with an app. 4. You can audit OSS websites too. 5. Your personal preferences have nothing to do with the fact that Apple makes tons of money from apps but not websites.

1. If you do it like this, then I count it as a mobile app, not a webapp. A webapp loads in the browser. We're not debating programming language here, if you run Rust in your browser via WASM it's still loading in the browser.

2. Wut?

3. The network traffic of an end-to-end encrypted app is... encrypted traffic to the server you don't trust.

4. Not sure if it's bad faith or not, you conveniently drop the other ideas: can you fork a website and use it against the original service? And again, if you audit the sources and then load the website, you have no idea if you are running those sources or not. Or if you will next time you hit "refresh".

5. Granted, they make a ton of money for apps. My solution to that is to force them to allow third-party stores.

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

#548
post #83

Earlier quoted context omitted.

I love hosting and I will never stop doing it. I keep buying servers (second hand; almost no one actually needs the latest) and hosting 1000s of companies.

For every person like you there are thousands who don't want to host!

My lovely clients!

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

#549

Earlier quoted context omitted.

I love hosting and I will never stop doing it. I keep buying servers (second hand; almost no one actually needs the latest) and hosting 1000s of companies.

How did you get companies to sign up to your website business?

I have been in business for 30 years. That helps. We don't overgrow or over hype and we discourage people who just want to overload things; we like boring companies with a lot of revenue / profit that run boring things like ERP, CRM, dashboards, LoB apps etc. And those companies just keep buying ; especially Vibe LoBbing makes for departments within companies churning out tons of apps they need to host somewhere.

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

#550

Earlier quoted context omitted.

I feel like I'm taking crazy pills reading these comments. Apps are clearly better for end users. HTML and css is SUPER slow. It doesn't feel native, it doesn't feel good to use. You also get so many weird glitches with state refreshing, sessions being cleared, log in not persisting. Has anyone here actually used a PWA? You can feel that it's slow and clunky. Apps feel SO much better with the native UI, pre-downloade…

You might be taking crazy pills or you've yet to come across an app that's just a webpage inside a web view (a lot of apps these days unfortunately)

For sure, and these apps feel bad. I notice instantly. But they manage local storage, caching, and sessions much better than a PWA anyway
Post reply on HN