This kind of gray with silver body please. Blue is a disappointment.

Plastic of unsaturated colors, preferably blue-grey aka navy, with bare metal. Google for images of Urbanears - they switched their color selection regularly and always kept in their lineup something in calm unsaturated blue-green-gray range - always had something appealing.

I just hope it won't come with white plastic in this case... The grey option is yet to be seen, bit most likely will be less repulsive.

No prior experience, so tells me nothing. At most, I've probably seen someone polishing their old watch to get rid o the worn out coating. Would prefer to not having to do it on a new watch with plastic parts nearby.

I won't judge your taste. Don't judge mine.
I consides aftermarket paint and stickers unacceptable on high wear items.
Current colors lineup leaves no comfortable choices for me. Black plastic comes with painted metal. Bare metal comes with painfully bright plastic.

And I don't want the black coat on metal - I don't like the worn down look it will get over time, compared to worn down clear metal. Blue is the kind of blue that the person who also loves red would choose. Give subdued calm colors to people who are disgusted by bright colors and black. Thanks.

For me, the colors are awful. You basically have nothing on offer for me. If you go with silver+white - you will have the situation "everything is either painfully bright or is black". 1/

... doesn't give me confidence if you choose to keep trying to build the product on top of two entities that don't go along well already. I have little to no faith in humans ability to agree on anything. Rather, be the "benevolent dictator" and shape the platform for communication on your rules.

Clarification to connect both comments: a new store as one of possible store service providers.

For a store, I'd rather started from a blank and really thought about licenses people choose when publishing their apps/watchfaces there, including redistribution and force majeure. With the power of hindsight, it should be possible to prevent similar dispute.

You make devices - you should be defining your APIs. Make service providers pluggable (if not already) - to avoid gatekeeping behavior. Also, the history of difficult communication doesn't give me as a user a confidence in the final product.

Blue-grey. I'm so tired of saturated colors companies are pushing so hard for some reason. Black is often the choice not because it's black but because everything else is uncomfortably bright.

Also, I don't know when to stop with v0.x.0 versions and declare the next one to be v1.0.0.
Every time it feels like this:
"Now it is perfect, but the next time will still be like the last time - I'll find something that will make it perfect for production for real."

And `leac` - lexer/tokenizer.
github.com/mxxii/leac
(I'm surprised I've already had more feedback on this one, considering how trivial of a feature it may seem.)

Still way to go through my 'tech stack' but feels good making some progress again.

What special do you need? Can it be done with plugins for Obsidian or VScode? From my observation, Obsidian is good to deal with messiness and extensible for niche domain needs.