DEV Community

Chani Lee
Chani Lee

Posted on

From one 3D river to 16: questions about social spaces on the open web

Earlier this month, I wrote here about K-HANGANG, a browser-based walk along Seoul's Han River. At that point, rivers in other countries were only a plan.

This is an update from my work as an independent developer in South Korea. The project now connects river-inspired digital spaces for 16 countries, as well as a shared meeting area called NOWHERE.

I am not trying to build another game with quests or rewards. My question is much smaller: can a 3D website become a place someone visits for five minutes, simply to walk or say hello?

What changed since the first version

The original experience was centered on Seoul's river. Expanding to 16 country-based spaces made me think about two different layers:

  • The sense of place: scenery and atmosphere should feel tied to the river being visited, rather than all 16 spaces looking identical.
  • The shared social experience: people should understand how to walk, meet and communicate without learning a different interface in every country.

For the browser experience, I've worked with Three.js/WebGL for 3D scenes and Node.js/WebSockets for shared presence. Supporting different screens and keeping interactions lightweight are continuing concerns.

The hardest challenge isn't adding another feature

A quiet virtual river is nice when other people are present. When nobody is there, however, a new visitor may walk around briefly and leave.

That is a product and community problem, not just a rendering problem. Adding more 3D objects would not necessarily solve it.

To help people find each other, I added NOWHERE, a shared space where visitors from the different country-based rivers can meet. I also introduced short, scheduled five-minute meetings. The idea is to make a human encounter possible without expecting people to spend hours online.

I still don't know whether those choices are enough to make people return.

Three design questions I am wrestling with

1. First-visit clarity. When a visitor opens the URL, how quickly should the experience explain where to go and what they can do? Too much UI can spoil a peaceful scene; too little can feel confusing.

2. Presence without pressure. Would visible signs of other visitors make the space feel more welcoming? Or would a quiet, almost empty environment be part of its appeal?

3. Web-first social interaction. Is a simple URL enough of an advantage, or does a shared virtual space need one very specific reason for people to return?

I'd value a developer's perspective

If you've built a multiplayer web experience, a WebGL scene or an online community, I'd especially appreciate your thoughts on onboarding, browser performance and helping newcomers encounter real people.

Disclosure: I built the project described here. I used ChatGPT to help organize and edit this English post; the project details and questions are mine.

Top comments (0)