If you operate with a mindset of, "what you ship, you can't take back or modify," you're on the right track. It's in partial conflict with the software ideology of, "build an MVP and iterate fast." You can still do that, but the MVP can't suck.
Source: Shipped a pretty great product, still stay awake at night.
How does the board feels if you don't use the motor in case of empty battery. Are the motors braking per se or do they spin freely if no power is applied?
The motors spin freely when unpowered. It will skate like a normal board, but with a bit more drag.
(Can't ride anyway before April due to SWEDISH WINTER)
Swapping out the bearings is still a lot of maintenance for a piece of equipment that otherwise requires very little.
> If you're in the market for their product, you can probably afford it.
You make it sound like they're ridiculously priced and only those with lavish lifestyles are their target market.
For the convenience that you get out of the product, it's well worth the price. It costs no more than a mid-range bicycle. With the recent price drop, they're even more affordable.
One of the most interesting things we've learned about recently is the temptation to cut corners using cheaper parts or processes or relaxed quality control procedures. It's easy to get quoted prices much lower than what we currently pay, but the long-term cost of choosing those parts (greater failure rates, manufacturing problems, and warranty costs, not to mention unhappy customers) is hard to quantify at decision time.
This is where experienced supply chain and hardware engineers are especially valuable. They understand the implications of these decisions and know the right way to account for them. For example, major manufacturers set aside "warranty accruals" as liabilities in their financials to cover the average future cost of servicing a unit that ships today.
I suspect this is a problem facing many hardware startups, Kickstarted or not. It feels non-intuitive to build hardware carefully and at such high initial costs, especially in the "move fast" culture of software development. And it's especially dangerous if a company goes "in the red" without realizing it by shipping many units that may fail or incur high warranty costs that exceed the margin on the product, but at a later date.