I think to start I should clear up the intention of the web build - it's there just to demonstrate the things that the pronouns system can do. Given the different styling needs of projects, I don't expect someone to drop the screens into their project without modifying them to suit the theme of their own UI, or updating them so the input length & allowed characters suits their font. It's also designed to have as few assets as possible (mostly using coloured rectangles) so it loads quickly and there are few assets for the browser to cache.

With that in mind, 1) is intentional. You should be able to click on the input again to disable it, since particularly for mobile users this will dismiss the keyboard so they can see the rest of the screen again. I do appreciate your suggestion to make it clearer which of the input boxes is currently accepting input, however, so I'll include styling for that in a future update.

2) This is intentional. For people who aren't familiar with screen language, or don't need the fine-tuned flexibility of the terms system, I wanted to demonstrate an option that gives the player some additional control over their terms and pronouns, but doesn't require a complex screen setup beyond the pronoun input. If you have a suggestion for how to make the wording of that choice clearer, I can update it. The choices are there mostly to demonstrate increasingly complex setups you can achieve with the system, rather than expecting a user to present this exact choice menu to the player.

3) This wasn't a priority for me as I operated under the assumption that a user will need to apply their own restrictions onto the input anyways - not every font supports the same characters, they might want different length or pixel width restrictions, etc. Thus, I've only applied the bare minimum of a length restriction on the input. But in the interest of a more stable web build, this is something I can update as well.