Below are interaction triggers (i.e. initiate an interaction) from within mobile applications. These interaction triggers (or the technologies behind them) show a path or succession, which also implies technology gaps and time-frames to be dealt with, meaning that short-term alternative(s) to “ideal” approaches must be considered.
(a) +-> Dial + Voice | (b) +-> Texting | (c) +-> The (typed) URL (mobile web) | (d) +-> Visual Tags (2D Codes, etc) | (e) +-> Radio Tags (NFC, etc)
- (a) Dial + Voice: is past, present and future but with practical restrictions (number of steps taken such as dialing and giving voice commands/talking) , costs restrictions (voice-plan) and potential linear navigation that affects the user experience. This method is the most consistent across.
- (b) Texting: is past, present and future but with practical (number of steps taken such as starting the texting application and type) restrictions and costs restrictions (text-plans), that affects the user experience. Other restrictions is difficulties (how many clicks) it takes to start the texting application. This method is consistent across to initiate interactions, but receiving text messages (for example with an embedded URL) may or not be supported by certain network carriers today. MMS is not practical, as it is not well supported across carriers today.
- (c) The (typed) URL (mobile web): is past (WAP), and present and future but with practical (number of steps taken such as starting the browser application and type) and costs restrictions (data-plans) that affects the user experience. This approach is pretty consistent across.
- (d) Visual Tags (2D Codes, etc): is present and future, but with practical restrictions (number of steps taken such as getting the application, starting the application, taking the photo) that affects the user experience. To be useful, must be able to be triggered automatically and asynchronously (ala PushRegistry). This approach is not consistent (standard), yes because all it requires is a camera and software, it is easier to deploy than radio tags.
- (e) Radio Tags (NFC, etc): is future, and provides the best experience. It does require downloading an application, but once downloaded, starting the interaction itself is as simple as tapping or waving the handset, automatically triggering the interaction. This approach is not consistent yet. While standard -based, it is not fully deployed/adopted and requires more hardware (radio) resources. Personal networks such as Bluetooth (while not radio tags per se) fall into this category, but Bluetooth also has its practical concerns with respect to discovery and pairing authentication.