Thanks for the response! My suggestion would be that if multiplayer aspects are really the key differentiator between Obsidian and your app, you should let the user see that straightaway. Maybe drop them into a shared workspace with other people or something? That could be cool.
replyAs for the tech framing - I imagine you'll get lots of responses on that, and I'm sure it works for some people. Speaking personally, I think it irks me in particular because I feel that "React is slow" isn't really true -- but hey, we can sidestep that whole argument if you just tell me that your app loads a 100GB text file in 0.1ms or whatever :)
deleted
replyHmm. Yeah that shared workspace idea is good. Tbh I just wanted to force myself to put this out there and stop polishing the dang thing! So this was the fastest way out and now I can iterate on better journeys like the one you suggest.
replyOn the React thing, I never said React is slow! I think it's great for a lot of things. I just chose a different path because I wanted to understand every part of the main product stack. I didn't use OT or CDRT for the same reason... :|