Two mobile projects, two kinds of waiting
The portfolio connects a camera phone to a desktop, then asks a travel prototype to minimise text input and network delay.
The camera did not remove the network
The mobile portfolio describes picture sharing for architects, using the Nokia 3650 as the focus of a study. The author reports that her user group did not then use camera phones professionally, but anticipates improving resolution. Transmission cost remains a constraint in the proposal. Its selected route therefore takes a photograph on the phone and moves it to a computer through Bluetooth, rather than treating immediate network upload as inevitable.
The travel case spends effort differently
The same page describes an XHTML travel-booking prototype. Here the named constraints are slow downloads, unreliable connectivity, few clicks and little typing. The proposed test on a handset concerns the behaviour of controls such as drop-down menus. These are historical design intentions and reported study choices. They are not a booking service, a modern device comparison or proof of completed usability testing.
Follow the bottleneck
The two cases make a useful pair because the mobile device is not treated as a complete answer. One design moves a heavy file to another machine; the other tries to reduce the amount of interaction needed on the phone. The common question is where waiting and effort should occur. Related records below preserve the travel case and the photo-sharing scenario at their own addresses.
Sources and edition note
This is new independent writing at the historical /mobile.htm address. It reconnects the specific work or project described above. It does not claim byte-for-byte restoration, original browser behaviour, current artist representation or operation of an earlier service. Source images, documents and full texts remain at their archival sources.