Frontend & Web

Web Games Portal: Ditching Unity for HTML/JS Simplicity

The web game scene is drowning in Unity. One developer is fighting back, building a portal focused on pure HTML and JavaScript.

Screenshot of a simple web game portal interface.

Key Takeaways

  • Web game portals are overwhelmingly dominated by Unity, leading to similar experiences and bloated downloads.
  • A developer has created a simpler web game portal using pure HTML and JavaScript, accessible and tweakable.
  • This alternative approach prioritizes lightweight design, transparency, and ease of modification over complex game engines.

Another Tuesday, another deep dive into the digital abyss, only to find the same damn Unity logo staring back.

That’s the reality when you search for “web gaming portal.” Or anything vaguely close. Most of the results? Identical. A digital landfill of Unity projects, each website a pale imitation of the last. It’s less a curated experience, more a corporate-sanctioned echo chamber. Where’s the fun in that?

The promise was simple: play lightweight games. No logins, no installs, just pure, unadulterated gaming. The kind built with HTML and JavaScript. The kind you can actually tinker with. Not this Unity-packaged behemoth that feels more like a locked vault than a playful sandbox.

These portals, often targeting students, are built on a foundation of ads. Loads of them. Not just the easily blocked banners, but the inescapable, game-disrupting kind. They serve their purpose, I suppose, if your sole goal is to numb your brain for a few hours. But for anyone with a spark of curiosity, a desire to peek under the hood and maybe — just maybe — tweak a line of code? Forget it.

Revisiting the glory days of 13kb challenges or even wanting to poke around a pure HTML/JS game means digging through GitHub repos, downloading, hosting locally. It’s work. Why should playing a simple game demand that level of effort?

What if there was a portal where you could just play these games? Anytime. No fuss.

Apparently, it’s not that complicated. One developer tried it, first with a basic Python server, then scaled it up. The recipe? Download MIT-licensed games. Host them in a Docker container. Create a JSON file to catalog everything. Spin up a React Single Page Application to tie it all together.

It’s remarkably straightforward. The JSON, acting as a makeshift database, looks something like this:

{
"id": "unique-uuid-here",
"title": "My Awesome Game",
"slug": "mygame",
"category": "arcade",
"thumbnail": "",
"emoji": "🚀",
"description": "A detailed description shown in the intermediate view.",
"players": 1000,
"rating": 4.5,
"badge": "new",
"path": "/games/mygame/index.html",
"source": "https://github.com/user/mygame",
"isPlayable": true,
"license": "MIT"
}

Sure, some fields like rating or players might be placeholders now. But the foundation is there. An iterable, expandable system. Themed with a little help from Gemini. Even ran on a Pentium 3 with Puppy Linux. Proof that simplicity still has a place.

This whole endeavor is a quiet rebellion against the Unity-ification of the web. It’s a reminder that sometimes, the most elegant solutions are the ones that don’t require a massive engine to run a simple game. It’s about accessibility, not just for playing, but for understanding. For learning.

The corporate gaming world, much like its entertainment cousin, loves to package things. To control the experience. To plaster it with ads. This project, however minimal, represents a counter-narrative. A space for games that are actually playable on the web, without the baggage.

It’s a stark contrast to the monolithic engines that demand significant resources. Unity, while powerful for complex 3D experiences, feels like overkill for a quick browser game. It bloats load times, increases complexity, and inherently limits the ability for users to inspect or modify the game’s code. The author’s approach sidesteps all of that. It’s a breath of fresh air in a market choked by proprietary software and heavy frameworks.

Why is this approach a good thing? Because it fosters a more open and adaptable web. When games are built with standard web technologies, they become more accessible to a wider range of developers and hobbyists. This encourages innovation and collaboration, rather than locking down experiences within a specific engine’s ecosystem. It’s the spirit of the early web, alive and kicking.

The Unity Problem: Is it Really That Bad?

Let’s be clear. Unity is a fantastic tool. For making complex games, for cross-platform development, it’s a powerhouse. But for what it’s being used for on many web game portals? It’s like using a sledgehammer to crack a nut. The sheer overhead, the download sizes, the complexity involved in just launching a Unity web build – it often outweighs the benefit for simple, ad-driven web games. The author points to the near-identical nature of these sites, suggesting a lack of unique development and a reliance on engine templates. That’s a symptom of the problem. When the tool dictates the outcome so heavily, creativity suffers.

Why Does This Matter for Developers?

It matters because it highlights a growing divide. On one hand, you have the push towards massive, complex game engines, often leading to bloated, unmodifiable web experiences. On the other, there’s a persistent, perhaps even growing, desire for simpler, more transparent development. For developers who want to build for the web without getting bogged down in proprietary systems, this approach offers a viable, and frankly, more enjoyable path. It’s a call to arms for those who believe the web should remain open and accessible for creation and modification. The code is available on GitHub, inviting anyone to learn from, adapt, and build upon this philosophy. It’s the kind of transparency that builds community and drives genuine innovation.

Frybahn, the demo website, is the proof. It’s playable. It’s simple. And it’s a world away from the Unity-choked portals that dominate search results. It’s a small victory, but a significant one.



🧬 Related Insights

Frequently Asked Questions

What does Frybahn do? Frybahn is a web portal that hosts simple games built using only HTML and JavaScript, providing a lightweight and accessible gaming experience without the bloat of game engines like Unity.

Will this replace Unity? No, Frybahn is not a replacement for Unity. It offers an alternative approach for simpler web games, focusing on accessibility and direct code manipulation rather than the complex capabilities of full-fledged game engines.

How can I contribute to this project? The project’s code is hosted on GitHub, allowing anyone to review, download, and contribute to its development. The author encourages engagement and iteration on the basic setup.

Written by
DevTools Feed Editorial Team

Curated insights, explainers, and analysis from the editorial team.

Frequently asked questions

What does Frybahn do?
Frybahn is a web portal that hosts simple games built using only HTML and JavaScript, providing a lightweight and accessible gaming experience without the bloat of game engines like Unity.
Will this replace Unity?
No, Frybahn is not a replacement for Unity. It offers an alternative approach for simpler web games, focusing on accessibility and direct code manipulation rather than the complex capabilities of full-fledged game engines.
How can I contribute to this project?
The project's code is hosted on GitHub, allowing anyone to review, download, and contribute to its development. The author encourages engagement and iteration on the basic setup.

Worth sharing?

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to

Stay in the loop

The week's most important stories from DevTools Feed, delivered once a week.