We can't handle them. The only thing we can do is to try to check the
connection speed/IP address on each request and adapt content if required.
Devices that support multiple networks are a good thing for users. Some devices
make a transition from one available network to another automatically. Some others
require manual selection. All these complications can affect the application in use
at that time. Consider that the user has selected all the pizzas and side dishes she or
he wants to order, and even entered her or his address. In the final order processing
step, the network changes. If we had code that will accept requests only from the
previous IP address, the user will have to start the whole process again. And if the
Chapter 11
[ 209 ]
user moved from a fast network to a slow one, and we showed large size images on
the order confirmation, it will be a pain for the user to wait for things to load.
As developers, we will have to learn and balance these things. User experience
matters and we have got to do everything to make it easier. Remember that many
mobile users will be non-geek. Most non-tech too! What matters to them is simply to
get the job done.
Pages:
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279