Quoted from BrewNinja:LOL...You guys are all funny. Take a step back from your high horses and look at the population. Not everyone is a 40 year old dude playing a pin in their home. There are a lot of people on location that play because they cant afford to own one, don't have room, etc. There are also a lot of old people, kids, etc that play and don't have smart phones. Saying that people who don't have a smart phone don't care is ridiculous. Like having a smart phone is what defines if you care? HUH? What if there is a tournament and they can piggy back off this? What if there is some other feature that is killer or needed for something. You guys are very short sighted on what can be done or what this could be possibly used for. Why not design something that works for every single person instead of just most people? Sorry it costs $50 extra to be fully inclusive
Extra node board, QR code reader, housing, wiring (and apron for retrofit) is more than $50 extra. (Not to mention the additional engineering effort, support overhead, etc.)
Are these phoneless people actually going to go home, create an account and print off a QR code so they can use these features? If they don't have a phone -- what if they don't have a computer and printer at home? Go to the library or school to do the same? What about people that don't know how to use a computer at all? Get their niece or nephew to figure it out for them? (You can keep going on and on...)
IMO the "right" approach would've been to start with a more lean solution as a mvp ($30 wifi dongle [optional] + software) and then iterate from there based on customer feedback. You can always iterate to something more complex/expensive if necessary.
$30 per game retrofit or incremental cost on new games would've interested me as a home user. $200/300/400 or whatever it ends up costing per game, not so much. Probably not a big deal either way for an operator though, as the telemetry and remote configuration aspects alone make it worth even the higher price. (Though, even there, a more lean implementation of wifi and some software improvements would've been sufficient for the use case.)