Live data from Hacker News

App Should Have Been a Website (and Probably Your Game Too)

rogueengine.io

111–120 of 384 posts

Re: App Should Have Been a Website (and Probably Your Game Too)

#111

Earlier quoted context omitted.

A web app that cannot handle a text file bigger than X bytes doesn't become useless, in the same way that a native app isn't useless even though it, too, has a limit on the maximum file size it can handle.

Any text editor that struggles to load a large text file on a modern computer is, simply put, inefficient. If 20 years ago they managed to write programs that could handle such cases and today many (web) apps fail at this task means we're going backward. My point is that it's much harder to write efficient code in the web ecosystem because you're bound to specific abstractions from the browser. Once deviating from sa…

I don’t know that I completely agree. It depends on the functionality offered, right? Like vim, for example, can struggle with very large files if you ask it to do syntax highlighting all the way from the beginning (or, it can give you syntax highlighting that is just wrong if you don’t). I don’t think vim is very inefficient (could be wrong there, though), and I don’t see any way to generally do syntax highlighting without looking at the whole file (although, of course, in practice there are often shortcuts for specific languages…)

Re: App Should Have Been a Website (and Probably Your Game Too)

#113
post #98

One comment that I haven't seen yet and that puts PWA for Games in jeopardy: the maximum caching allowed for Safari PWA's (thus the whole iOS ecossystem) is only 50mb. Most mid-core / hardcore mobile games are bigger than that after downloading remote assets when the app loads for the first time, and this means a player of a mid-core PWA game would have to redownload a good chunk of the assets everytime the game load…

The 50mb limit no longer exists, it's much higher now https://bugs.webkit.org/show_bug.cgi?id=198133#c15 Safari will delete your cached data if your app goes unused for a little while though. Native apps may do the same thing though... at least on Android I get notifications about it deleting cached data for native apps I haven't used recently.

That's nice, thanks for correcting me! Although it's quite a nuisance that most PWA info I looked for before posting had the old 50mb (mis)information.

Re: App Should Have Been a Website (and Probably Your Game Too)

#114

I generally agree, but not for any critical workflow. You can't easily archive copies of web software. One day any website you rely on could introduce user-hostile regressions or simply disappear. Apps in the mobile ecosystem also have this problem, but at least you can archive and sideload old APKs on Android (for now).

> you can archive and sideload old APKs Only as long as external dependencies (like APIs) are satisfied.

Very true, but you can also keep around an old Android phone, or even emulate an old AOSP distribution if your really need to. Obviously this is not ideal, but if you're trusting your hobby or business to an app, it is in your best interest to make sure that it doesn't poof out of existence randomly before you can upgrade.

Re: App Should Have Been a Website (and Probably Your Game Too)

#115
post #103

As a consumer, I understand the need of a native app for something that is performance intensive or that requires a level of OS access that the website doesn’t provide. OTOH, in tired of everyone pushing apps that could easily be a website. I had an xfinity technician aggressively pushing me to install their xfi app when they came to install the service. They told me it was the only good way to configure the WiFi (!)…

I don't think it has anything to do with performance. Apps make it far easier to advertise to users. You can send the users a notification even when they aren't using the app It's much harder or impossible for users to block in-app advertising It's easier to track users via apps, and your tracking data will be richer, more accurate and therefore more valuable. Until this changes, we'll get stupid apps that should hav…

> Apps make it far easier to advertise to users.

And to obstruct users e.g. from screenshotting content such as my bank transaction data.

Re: App Should Have Been a Website (and Probably Your Game Too)

#116

One of my kids recently started playing travel basketball and being a nerdy, into stats tech dad I wanted to take stats on the game. Instead of downloading an existing app, I decided to see if I could write my own web app with the following constraints: - no frameworks - just basic javascript - track multiple stats - be able to enter stats via phone and only using one hand - while also holding a 4 year old in my othe…

I don't understand what this has to do with the topic.

Re: App Should Have Been a Website (and Probably Your Game Too)

#117
post #73
post #2

I disagree. The problem is more nuanced. A well implemented (native) app is always better than a well implemented web site. The problem is poorly implemented apps which are just UI wrappers hitting dumb APIs or embedding entire web stacks which hit dumb APIs. A well implemented web app isn't much better than that. They don't work offline, they use way more resources than anything native and they leak data like a siev…

> A well implemented (native) app is always better than a well implemented web site. No, because it fails to support the feature of running virtually anywhere. For many people this is the #1 feature. Everything else is just icing on the cake. Who cares about an app that is 2x faster but doesn't run?

I've watched Logseq (note app) go from a perfect little browser-based app that did exactly what I wanted--block-based markdown notes synced through git--to an app with dozens of features that are pure bloat for me that I can't use in half the places I need it because I cannot install apps.

It was an interesting process to watch start, because people were like "finally an app!" and "moving on from 'just' a website!" but without any real justification for it. The app itself was the accomplishment.

And I should note the Logseq app is a good piece of work. In absolute terms it's great. It is, however, not what it used to be and not really what I want. I'd like to fork Logseq, deprecate the app, and have a self-hosted browser interface with storage on the server, synced to a git repository for backup.

Re: App Should Have Been a Website (and Probably Your Game Too)

#118
I'm playing https://www.twilightwars.com it's a turn based game. You get a notification once it's your turn. If you don't click on the notification but just open the browser, the browser thinks you don't want the notifications and stops them. There is no way of whitelisting the notifications.

Re: App Should Have Been a Website (and Probably Your Game Too)

#119
This reasoning is why I'm keen to try out RomM[0], a ROM library manager that has EmulatorJS[1] built in. Rather than having to setup emulation on each device where I want to play a simple game, I can instead use this combination to do it from any web browser on my local network.

[0] https://github.com/rommapp/romm

[1] https://github.com/EmulatorJS/EmulatorJS

Re: App Should Have Been a Website (and Probably Your Game Too)

#120

A couple of weeks ago I was with a friend who was looking at a website for unusual holiday properties and he bemoaned the lack of an app. I asked him why bookmarks didn't work for him, and he explained it all just got lost - he wanted this to be in the "hotels and holidays" section of his phone's home screen. So I showed him how to add a website to his home screen (well, sort of, I've been iOS since ~2009 and he uses…

> I showed him how to add a website to his home screen

Some sites prevent rhis, diverting you to install their app.

Post reply on HN