All products have a life cycle. You’re comparing Sparki, which its hardware barely out of design mode, to products that have had years of existence. I understand that it may be your first experience with a product right at the beginning of its life cycle. Yes, it’s painful. I too was surprised when my remote stopped working, it took me a few seconds to think it through.
I teach robotics and computer engineering to kids 8 and up. I’m also a software engineer, or I was before becoming a mom. And I’ve dabbled with hardware while in university. I’ve also played with real industrial robots back then. Talk about lack of tutorials… That may be why I’m not reacting the way you are. Mind you, I have no idea what your background is.
Your points are valid for the current state of Sparki’s ecosystem. But that will change. The hardware is out. And it looks good. Not great (I expected a bit more speed, and more volume, that beeper will be useless in a classroom), but good. The hardware is here, and I, for one, am happy Arcbotics didn’t wait for everything to be in place before releasing Sparki.
What we have in our hands is a finished “hardware”, not a finished “product”.
ITA. Soon, but not this week, not even this month, everything will be in place.

