#realxtend

Rather than pretend I have the answers, here's some thoughts/questions:

WebTundra completeness: Is WebTundra actually a fully functional piece of software, or is it just a collection of parts that need further assembly?

Simulator WebSocket work: While 0.7.6 brought WebSockets to Opensim, it's unclear how much more work is needed to have them fully replace the standard UDP client circuits.

Content Transfer: If simulators aren't hosting their own web viewers, how do we handle the problems of content transfer?

User login/session decisions: Is each region it's own web page?  Is that page served by the simulator? Should anonymous users be allowed, and how would that work?

Prims: Do we ignore them outright and only display mesh?  Do we attempt something akin to InWorldz's DreamShare and convert prims to mesh on the server? Do we go all-in and attempt to port the prim-meshing code into Javascript?

Avatars:  Fully custom avatars are probably too much to ask for up front, so what is the alternative?

UI Design: With a focus less on avatar appearance, building, and inventory management, the UI will need a total rethink.

These are only the first few questions, some with no easy answers. Thankfully, we have the luxury of being able to start out basic and improve incrementally.    My guess at a critical path MVV (Minimally Viable Viewer) would be:

Simulator-hosted: Simplifies login, content transfer, operator consent.

Login direct to region with existing account: No sim/grid work needed.

Mesh only: If viewers are sim-specific, regions can be intentionally crafted to be compatible.

Basic Mesh Avatars: It's no fun, but it's easy to implement.  Customization can come later.

UI: KISS rule.  Chat/IM/Friends/Groups.  Everything else is probably too much.  Maybe even force first-person, just to make it even easier.