Nice job. Feedback: 1. If latency is the biggest draw, I would think a native Swift app on macOS or a C++ app on Windows would be preferable. I don't see how

Nice job. Feedback: 1. If latency is the biggest draw, I would think a native Swift app on macOS or a C++ app on Windows would be preferable. I don't see how you're going to get around the inherent latency of high-level JavaScript and the browser. 2. You've got an animation where the cursor smoothly moves over the letter when you press a key. The issue is that (whether or not it's true) it creates the illusion of latency, which is probably not what you want. Conclusion: The market fit is going to be weird. There's really only two types of people using typing tools on a regular basis: 1. As a learning tool to improve their touch typing. 2. Competitively - think games like Type Racer. In the first case, people coming in at around 20-30 wpm aren't going to be overly concerned with input latency, if they notice it at all. In second case, you have the classic "cold start" problem that all social apps have. In order to attract an audience, you have to already have an audience.