4 ms·

I've seen Svelte used in a number of high impact tools, including in AAA videogame UI. In my experience, I've seen engineers very happy working with it, and it

I've seen Svelte used in a number of high impact tools, including in AAA videogame UI. In my experience, I've seen engineers very happy working with it, and it meets the performance needs for a videogame it should be good enough for the web.

ha4fsd3fas 6y ago
Do you have any info on that AAA game? I would be curious to read up on how/why they used svelte.
preommr 6y ago
> including in AAA videogame UI elaborate, please, because this sounds so bizarre. Are they bundling an entire web view and then interfacing it with their game engine? Not only is the tech conceptually weird, I can't think of too many AAA games that have very complex UIs other than maybe the CK series.
- turtlebits 6y ago
  A lot of games have storefronts for DLC. I've seen these used as webviews, especially payment forms.
- Macha 6y ago
  It doesn't surprise me. 5 years ago the standard solution was Scaleform, which is pretty much the same thing but with Flash.
- vbezhenar 6y ago
  It might be for main menu. I think that WC3 reforged used webview for its menu.
  - Pfhreak 6y ago
    Main menu but also in game UI. Ability timers, weapon reticles, health bars, etc.
- Pfhreak 6y ago
  Yes, it was two Svelte apps. One for the menus and one for the in game ui/hud elements. Things like health bars, reticles, ability timers, etc. The interface between the game engine was designed to be as decoupled as possible. The UI could run in a browser with a mocked game underneath it, which allowed the UI devs to iterate very quickly. This also has the advantage of allowing UI to be built before the game had a feature implemented.
mattdesl 6y ago
I’m also working with Svelte for my (non-AAA) game, and enjoying it thoroughly. The only problem I find is that complex animations/transitions can get a little messy (compared to say GSAP timelines), and it tends to create a lot of garbage out of the box so some tuning is necessary to avoid GC thrashing.
Macha 6y ago
I would wager that a middle of the road data-heavy web UI actually asks more of their framework performance wise than a video game UI. Compare the number of interactable elements in e.g. a Trello board to a FPS weapon loadout screen. Sure, the consequences of a sluggish UI in a video game can be worse than a sluggish UI in a web app if it's running on the main thread and blocking the game's execution, but plenty of games update their UI less than once a frame, or run it in a separate thread altogether.
- Pfhreak 6y ago
  Possibly. It's not just the loadouts though. Reticles and health bars need to animate at least 30 fps if not 60.

ha4fsd3fas 6y ago

Do you have any info on that AAA game? I would be curious to read up on how/why they used svelte.

preommr 6y ago

> including in AAA videogame UI elaborate, please, because this sounds so bizarre. Are they bundling an entire web view and then interfacing it with their game engine? Not only is the tech conceptually weird, I can't think of too many AAA games that have very complex UIs other than maybe the CK series.

turtlebits 6y ago
A lot of games have storefronts for DLC. I've seen these used as webviews, especially payment forms.
Macha 6y ago
It doesn't surprise me. 5 years ago the standard solution was Scaleform, which is pretty much the same thing but with Flash.
vbezhenar 6y ago
It might be for main menu. I think that WC3 reforged used webview for its menu.
- Pfhreak 6y ago
  Main menu but also in game UI. Ability timers, weapon reticles, health bars, etc.
Pfhreak 6y ago
Yes, it was two Svelte apps. One for the menus and one for the in game ui/hud elements. Things like health bars, reticles, ability timers, etc. The interface between the game engine was designed to be as decoupled as possible. The UI could run in a browser with a mocked game underneath it, which allowed the UI devs to iterate very quickly. This also has the advantage of allowing UI to be built before the game had a feature implemented.

mattdesl 6y ago

I’m also working with Svelte for my (non-AAA) game, and enjoying it thoroughly. The only problem I find is that complex animations/transitions can get a little messy (compared to say GSAP timelines), and it tends to create a lot of garbage out of the box so some tuning is necessary to avoid GC thrashing.

Macha 6y ago

I would wager that a middle of the road data-heavy web UI actually asks more of their framework performance wise than a video game UI. Compare the number of interactable elements in e.g. a Trello board to a FPS weapon loadout screen. Sure, the consequences of a sluggish UI in a video game can be worse than a sluggish UI in a web app if it's running on the main thread and blocking the game's execution, but plenty of games update their UI less than once a frame, or run it in a separate thread altogether.

Pfhreak 6y ago
Possibly. It's not just the loadouts though. Reticles and health bars need to animate at least 30 fps if not 60.