I'm stoked that you're building this open with Linux! I'm willing to tolerate a lot of (what's the opposite of polish?) but for me it has to be open and workable with my current setup (which is all Linux), and I don't want it loaded with privacy invasive analytics. I'll put down a lot of money to buy something like that.<p>My advice in no particular order (I know you probably already know all this but I already typed it so I'll post it):<p>1. Get something shipping ASAP. This space is rocketing forward now at an electic pace and the ecosystem for the average person is going to get locked behind walled gardens if something open doesn't get out there. If it were me I would try to get beta units available soon and let the open source community and early adopters run with this thing while you stabilize/polish. Don't rush to "stable" too quickly, but also don't prevent shipping too long that competitors beat you to the release line.<p>2. When you market this to consumers, don't hide the "Linux" part since people like me will be very attracted by that, but don't emphasize it either because most people don't know what it means. Just describe "computer workstation on your face" rather than "linux machine on your face."<p>3. Provide factory images so people can hack with the hardware but still escape back to supported territory. If you do this, there will be a ton of open source interest and efforts and they will not only develop awesome apps for you, but they'll port a lot of stuff too. If I were you, I'd be making open source collaboration a huge part of my strategy.<p>4. I would also be looking at things Valve did with the Steam Deck for tips/guidance.