tclarke We did think about piggy-backing through the phone. However I think we would have more flexibility and possibilities when The Hyperboard is always connected to the internet.
In the case of using the phone to supply the internet connectivity, we have to somehow persuade the user to connect the phone to the Hyperboard.
For example when the user has to update the firmware he/she would need to through the process of pairing and only then updating the firmware. Whilst with persistent connectivity we would do it while The Hyperboard is in idle mode.
Actually this bring a question. How would the user be informed about a new update? We don't want to push updates while driving . Also I don't want the updates to impede the use of the Hyperboard (e.g. windows updates in the middle of a meeting) .
Maybe with @Albert 's nunchuck we can prompt a confirmation. Or maybe we can make it part of the initial configuration. Hm.. I think the best way would be to do that while The Hyperboard is charging. That's what I like about the Android way of updating apps This way we also ensure that The Hyperboard does not run out of power