1. Equating mobility and wireless
Subtlety is everything. Even at Network Computing, we tend to lump mobile and wireless into one category, but there are important distinctions between the two.
Mobile applications running on notebooks or PDAs don't always require wireless access: If you don't need information in real time, dial-up access and/or synchronization of data onto mobile devices makes more sense.
On the flip side, wireless isn't always all about mobile access, either. It can instead be used as a substitute for wired infrastructure, like using a wireless bridge to connect two facilities in a metropolitan area rather than running a T1 between them. And even when wireless is used to support a mobile work force, these users are seldom interested in the kind of mobility you get from a cell phone (e.g., network access while driving down the highway). Instead, they typically want "nomadic" access, where they can access the network from their remote locations on the road or in branch offices rather than from the points in between.
If you don't distinguish between mobility and wireless when you install your wireless network, it may not fly. You can't settle for the nomadic approach if you're running an application like wireless voice over IP, for instance, that requires actual mobility.