Setup ASSUMES a pc with wi-fi
I went to set up my TWINE for the first time using my Win7 desktop PC. Since that machine has no built-in wi-fi (CAT-5 cable only), I was stuck. Then tried my old Acer netbook, and that had trouble logging in to the TWINE "network" (and maybe java issues too). Finally I used my wife's Win7 laptop to get it going which worked flawlessly. I'm really bothered by the implicit assumption that ALL users have a PC with wi-fi connection. It would have saved me some frustration if there was a polite reminder that this is a requirement.
I suspect we're at a point in time when wifi is starting to out-number wired. I'd love to hear what the designers think about this problem.
1) We can provide an upfront reminder that this requires a Wi-Fi device to set up. I'm working on explicit requirements at the beginning of setup along with better IE and phone support. Setup works great for most people, but when it doesn't, it can be very frustrating.
2) Yes, we're well past the wired-wireless crossover point and onto the next transition: This Black Friday for the first time, tablets outsold laptops.
We've completely committed to wireless connectivity, and that's affirmed by the many interesting uses y'all have come up with that take advantage of Twine's portability. Being small, we have to make hard decisions on where to focus.
I solved that problem by setting up Twine on my iPad, which only allows one WiFi connection, and reconnects to my own network when Twine shuts off it's hub after a successful connection. Only one minor caveat - the password/passphrase entry box that iPad puts up will capitalize the 1st letter, even if that is not what you want, but, easy enough to reverse.
The amount of data actually transmitted makes any speed differences between wired and wireless negligible.