Most people thought it was delightful and immediately playable, especially the feeling of dropping a black hole into physical space on a phone. The real signal came from a long technical dispute over the phrase “physically accurate.” Several commenters with relevant rendering or astrophysics experience said the app gets the core gravitational lensing idea across, but the rendering pipeline is too simplified and in places wrong to justify that claim. The criticism centered on arbitrary color mapping, brightness handling,
Doppler treatment, a thin simplified
accretion disk, and a non-rotating default black hole. The author held a narrower definition of accuracy, arguing that the key black hole physics here is strong light bending and
gravitational redshift, while disk appearance and color mapping are presentation choices or missing features rather than inaccuracies.
That argument never really landed. The comments converged on a more practical standard: if a demo presents itself as educational and physically accurate, then the visible output has to faithfully communicate something physical, not just have some correct equations upstream. A lot of goodwill remained for the project itself. Several people called it a great visualization and praised the open source release. But the title set expectations the implementation could not meet, and that framing overshadowed what otherwise would have been a straightforwardly well received science toy. A secondary thread surfaced a different lesson from the demo’s AR and VR modes. Large nearby cosmic objects reliably trigger fear responses in immersive environments, which makes the app memorable but also hints at accessibility issues for VR science experiences. There was also useful implementation chatter on browser fragmentation. AR passthrough, raw camera access, and dual camera feeds still do not line up cleanly across Chrome, Firefox, and WebXR APIs, which limited the intended effect on many devices.