Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

rogueengine.io

Post reply on HN
Print view View original

191–200 of 384 posts

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

#191

Post by Multiplayer »

alternatex wrote: post #174
rubymamis wrote: post #22

While the web platform is catching up due to the continuous supply of abstractions by modern browsers, once you must deviate from those abstractions, you quickly find yourself needing to implement something yourself that is much less efficient than a native implementation. I wrote about developing my own block editor from scratch[1] using C++ and QML after finding that Notion (and so many other web apps) are extremel…

This app looks exactly like one I had used in the past. Took me a while to find it: https://www.notes-foss.com/ Even the logo is almost identical. Is this the same project? Looks like two separate GitHub repos by the same author. Why two similar projects/websites?

I was wondering about that too. This is in the article linked to https://rubymamistvalove.com/block-editor

7. The previous version of Daino Notes, called Notes is FOSS (free and open-source software) available at https://www.notes-foss.com/ and the source code is available at https://github.com/nuttyartist/notes. I decided to make Daino Notes closed source due to difficulties in monetizing FOSS. In order to comply with Notes' MPL license, all common files between Notes and Daino Notes are published in https://github.com/nuttyartist/daino-notes-public

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

#192

Post by Animats »

debugnik wrote: post #189
Animats wrote: post #186

> Thanks to HTML5, WebGL, and WebAssembly, browser games are catching up to native ones in ways we couldn’t have imagined just a few years ago. Meta’s Oculus browser already delivers web games that rival native apps in performance. And once WebGPU becomes standard, the differences will be practically invisible. If only. Have you tried Google Earth on Firefox lately? You can't even zoom in and out any more without wai…

> Is it a deliberate attempt by Google to force people to Chrome? For the last several months, the YouTube player takes me several seconds to load on Firefox and freezes on me for a couple of seconds every other time I press play/pause... And changing the user agent fixed it! So I say yes. But I found the extensions to do so quite clunky so I gave up.

> And changing the user agent fixed it!

Send a note about that to the legal team at the Department of Justice managing the Google antitrust lawsuit.[1]

[1] https://apnews.com/article/google-search-antitrust-case-5911...

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

#193

Post by adastra22 »

polotics wrote: post #5
adastra22 wrote: post #3

Earlier quoted context omitted.

> at Rogue Engine, we’re committed to being the go-to game engine for Three.js and the web and there you go, author has a vested interest in you making web apps.

well the article is well reasoned enough. what I gave up on was finding actual pricing information for this engine. all it say is free if you earn less than 80k... so what's the price please?

I don’t think the article was well sourced. WebGL technologies might be adequate for casual games… maybe. But it will be a very long time before they approach AAA gaming performance. And there is still a ton of funkyness about input (gamepad? multitouch?) and latency that is hard to address on a web stack.

He just asserts that the underlying technology has come along. It hasn’t.

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

#194

Post by adastra22 »

Animats wrote: post #186

> Thanks to HTML5, WebGL, and WebAssembly, browser games are catching up to native ones in ways we couldn’t have imagined just a few years ago. Meta’s Oculus browser already delivers web games that rival native apps in performance. And once WebGPU becomes standard, the differences will be practically invisible. If only. Have you tried Google Earth on Firefox lately? You can't even zoom in and out any more without wai…

> On the other hand, there is absolutely no reason that Uber or Waymo needs to have an "app".

Here’s one: I don’t give websites my location or the ability to interrupt me with notifications. Ever. I’ve blocked the browser from doing this entirely.

I have Uber and Lyft apps installed and granted those permissions though.

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

#195

Post by serial_dev »

Animats wrote: post #186

> Thanks to HTML5, WebGL, and WebAssembly, browser games are catching up to native ones in ways we couldn’t have imagined just a few years ago. Meta’s Oculus browser already delivers web games that rival native apps in performance. And once WebGPU becomes standard, the differences will be practically invisible. If only. Have you tried Google Earth on Firefox lately? You can't even zoom in and out any more without wai…

> Anyone know what went wrong in there?

Knowing, I don’t know, could be related though…

Google Earth uses Flutter on web, too, which is in my opinion, the platform where Flutter is giving its users the worst experience.

Though the root cause of the bug could also be non-Flutter related, because in Google Earth’s case, Flutter mainly just wraps the interesting bits (maps stuff in c++???) with a unified UI skin.

And does Google break Firefox all the time on purpose? Good question…

https://medium.com/flutter/extreme-ui-adaptability-in-flutte...

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

#196

Post by adastra22 »

Dig1t wrote: post #142
fidotron wrote: post #99

Earlier quoted context omitted.

The Google Play update emails kill me with the level of irrelevant noise. “This is an important tax update for [country you didn’t think existed anymore].” etc.

Good lord this is so true. I somehow got my personal email associated with the classroom Google Play account from back when I was at university, so every app uploaded by all students for each new semester I get emails for still. Every few months I get a batch of 30+ emails telling my that my app is not in compliance and it's at risk of being removed.

We’ve wandered off topic, but there should be a safe harbor provision if your app has <500 installs or something.

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

#197

Post by nostromo »

Animats wrote: post #186

> Thanks to HTML5, WebGL, and WebAssembly, browser games are catching up to native ones in ways we couldn’t have imagined just a few years ago. Meta’s Oculus browser already delivers web games that rival native apps in performance. And once WebGPU becomes standard, the differences will be practically invisible. If only. Have you tried Google Earth on Firefox lately? You can't even zoom in and out any more without wai…

Yes, Google has adopted lots of dark patterns.

I use YouTube via browser (Safari or Brave) on mobile and it's clear they don't care about the mobile web experience at all - to the point it seems like they are deliberately trying to force you to use the app.

I assume it's because they know the browsers support adblocking and limitations on tracking and notifications.

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

#198

Post by codazoda »

thot_experiment wrote: post #159

I man don't get me wrong, I love the idea of PWAs but this dude is out to lunch. It's so painful making anything complex work cross browser/cross platform. On iOS iirc they don't even support adding PWAs to the homescreen? You definitely can't Bluetooth outside of Chrome (probably only on Android and Windows too because nothing fun is ever allowed on Macs). Multiplayer games you kind of need UDP. You cannot UDP in th…

You can add PWAs to the Home Screen on iOS; Share, Add to Home Screen. This is how I build apps to scratch my own itches.

Edit: Err, sorry to pile on. I see others have already mentioned this.

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

#199

Post by hot_gril »

thot_experiment wrote: post #159

I man don't get me wrong, I love the idea of PWAs but this dude is out to lunch. It's so painful making anything complex work cross browser/cross platform. On iOS iirc they don't even support adding PWAs to the homescreen? You definitely can't Bluetooth outside of Chrome (probably only on Android and Windows too because nothing fun is ever allowed on Macs). Multiplayer games you kind of need UDP. You cannot UDP in th…

iPhones support PWAs on homescreen. However, there's no way to trigger the "install the PWA?" prompt. The user has to do it, which very few know about, and maybe that's what you were thinking of.

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

#200

Post by GoblinSlayer »

ilrwbwrkhv wrote: post #151
ndileas wrote: post #134

Earlier quoted context omitted.

I look at these things as essentially aesthetic preferences. There's certainly cases where a certain medium is the objectively right one for a task, but there's many others where it really just a matter of taste.

I actually think of them as more than just an aesthetic preference. It is fundamentally about proof of work. Something that will become more and more important as we move into a post AI world. Every single piece of art, music, game or any other creative piece, has three things to it. One, the actual artifact itself of the music, the art and the game. Second is who is making it. And the third is how much have they put…

That's monopoly problem. Text retains quality, because it's more democratic, and AI can democratize visual art.
Post reply on HN