That’s actually a good point. I’ve read Optimot’s design goals and I’m working on a new revision where é and à are moved to the base layer since they are more common than a lot of consonants.

LibreOffice Calc and a lot of free time 😅

That was actually very similar to my first prototype but I went another direction.

FX300 Angular. Basically the WipeOut Pure typeface.

I always program my arrow keys to have PgUp/PgDn/Home/End, so technically they do two things 😅. I’m working on the layout and all of the layers are crammed already. I may have to abandon features tho, the way I see it I would need to free 8 keys on the function layer to make things work.

Yeah but I really like having physical arrow keys 😅

I’ve never been a fan of the vi-style keys.

Yeah yeah, AOSP and all that. Despite, Android is made primarily by Google to push Google products and most apps depend on Google services. For all intents and purposes, Android is a first party OS for Google.

Google literally owns Android tho.

if Linux/Mac/Windows all have the same deadkey combination for ë and ê on their built-in AZERTY, use a macro that types that.

They do actually. Macro it is then.

For the ligatures, I might actually map AltGr-O and AltGr-A to some keys and Alt+0156 and Alt+0230 to adjacent keys, so there is no need to maintain layer spaghetti just for two (useful but relatively uncommon) characters.

A whole new can of worms can be opened too with accented, uppercase letters.

I’m gonna scale my ambitions down. Let’s not be more royalist than the king as we say in French, I will aim for parity with the AZERTY keyboard and we’ll see from there.

Ergogen

No, good old TikerCAD and a lot of free time :D