It was an issue with Firefox and the codec we use for the audio samples. I just changed the codec for the audio to something that works on all browsers.
862 karma · joined July 20, 2019
It was an issue with Firefox and the codec we use for the audio samples. I just changed the codec for the audio to something that works on all browsers.
- Ours has an actual mechanical switch (with a spring and contact leaf) that is pressed, the butterfly switches were a metal dome
- Our switches have much more vertical travel (1.8mm) compared to the butterfly switches (~0.5mm). A big part of the issues with the butterfly switches was they had tiny tolerances, so specks of dust or dirt could jam them. Since our switches are so much larger, this is less of a problem
- Butterfly switch arms were made from plastic, our arms are made from steel.
Firstly it makes no sense for a backlight to be anything but a warm colour at night because it strains your eyes exactly when they are most prone to it (at night, in the dark).
And secondly because it allows us some modest power savings. The chemistry used in our red LEDs (AlGaInP) is more power efficient than that used in other colours. Being a very thin device, we have a small battery, and therefore need to save power wherever we can.
Altar II is quite a quiet keyboard, and there is a special sandwich of materials specifically designed to make it as quiet as possible.
The built-in speaker is interesting. Really it's just there because it's fun, and its nice to get the odd bleep or chime when your keyboard connects or begins charging.
The firmware source code will be published publicly on Github in the future, as our other keyboard (Altar I) is: https://github.com/electronicmaterialsoffice/firmware-altar-.... Anyone is welcome to play around with it.
Do also bear in mind the final retail price is $349. the $249 price is for early pre-orders only.
People are raising a good point RE Touch ID. It is possible to add a fingerprint sensor. But that fingerprint sensor will never be able to do the things that Touch ID is most useful for: i.e. use Apple Pay. It would be incredibly confusing to have a fingerprint sensor that was usable for some things and not for others. Therefore the better experience today is to not include a fingerprint sensor at all, imo.
If you'll indulge me for a moment, because I never get to talk about this stuff: the corner radii of the cards on the site are actually "squircles" rather than perfect rounded corners. To me this is much more pleasing to the eye. The squircles are achieved by creating a PNG mask which is then 9-sliced and expanded to mask off the edge of the cards. Another mask is used for the stroke and laid on top of the first mask, to give the gradient border effect.
With regard to Windows keys that is a possibility. We shipped our previous keyboard, Altar I, with both Mac and Windows markings on the keys.
Rest assured we are building a sustainable business that will be around for the long haul.
They feel quite different to the Chocs, unsurprisingly. Although the required actuation force is close to the Choc Reds (40gf on our switch vs 50gf on the Choc Reds), because it's spread over such a small vertical travel it feels much "snappier". There is also very little pre-travel. It's kind of like a much sharper/tactile feeling chiclet switch with more vertical travel, if that makes sense.
There are a couple of small quality-of-life features that do require the app: for example if you want haptic feedback when you receive a notification. This is because the keyboard has no idea what is happening on your OS, and requires some middleware. But all the core functionality requires no app at all.
To answer your second question, the firmware for Altar II will be open-sourced, as the firmware for our Altar I keyboard is. You can see the Altar I firmware source code here: https://github.com/electronicmaterialsoffice/firmware-altar-...
Both Altar I and Altar II firmware are based on the open-source ZMK (https://zmk.dev). We try to contribute back to ZMK whenever we can because we have benefitted so much from it. Two members of our team are also long-standing ZMK contributors.
If we did a numpad I would probably do it as a separate device. Personally I don't like how the numpad sits between the edge of my keyboard and mouse. I'd prefer it to the left of my keyboard or to the right side of my mouse.