@Applet
You're absolutely correct. Normal keyboards are not optimized for battery use, and they don't need to be. Newer keyboards tend to be more power efficient, and LEDs are pretty efficient nowadays as well. I don't have other keyboards to test, so the runtime on my website is based on my keyboard, with the LEDs turned off. When I finalize the design I will run more tests to have an accurate representation of many use cases, and of course I will be very transparent about the whole process. Like @invismonk mentioned, there was another similar kickstarter product which was a scam, and it had many red flags, I'm doing my best to prove that my product actually works and it can exist.
@invismonk I've read all the comments on that kickstarter campaign a few months ago, I'm aware of that project, and in my opinion it was very very obvious that it was a scam. They never showed the product actually work, all the gifs look like stock footage, and the "new" design is only a CGI render. No progress was made on that at all.
As for the standby mode, in my implementation I have a touch button on top of my device, so just by touching it, it wakes the device up and in a few seconds (1-2 max) it automatically reconnects to the connected devices. Having an mcu that constantly reads from the keyboard is not possible, for obvious reasons, as it would require the keyboard to be turned on all the time, which would drain the battery, and without direct access to the internals, which cannot be done through USB, there's no other way to detect keyboard presses unfortunately. The touch button is a very nice way of doing it personally. The RGB will indeed drain more battery, I will do my best to optimize at least my mcu to maximize the runtime. In the current prototype, RGB (at max brightness) is an issue. At low brightness it actually works pretty decently, but I don't have accurate measurements, yet.
