User Tools

Site Tools


android:track:trackstories

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
android:track:trackstories [2014/03/26 22:47]
mikeclapp [Settings]
android:track:trackstories [2014/03/28 00:29] (current)
mikeclapp [Identifying the machine at startup]
Line 277: Line 277:
 The simplest path is inputting nothing (pressing cancel) at the Vehicle selection window. All we can do in this case is log a unique identifier and attach the tracks to it. The simplest path is inputting nothing (pressing cancel) at the Vehicle selection window. All we can do in this case is log a unique identifier and attach the tracks to it.
  
-The second simplest path is picking a predefined machine the first time and confirming that vehicle choice at the start of every session. This is probably the desire ​first release behaviour.+The second simplest path is picking a predefined machine the first time and confirming that vehicle choice at the start of every session. This is probably the desired ​first release behaviour.
  
 For a more dynamic environment where machine-tracker associations change frequently, implementing a bar code scanning function could be more desirable than picking from a list. For a more dynamic environment where machine-tracker associations change frequently, implementing a bar code scanning function could be more desirable than picking from a list.
Line 284: Line 284:
  
 {{:​android:​track:​startupmachineselection.png?​300|}} {{:​android:​track:​startupmachineselection.png?​300|}}
 +
 +
 +The imagined flow is this:
 +
 +  - Start SmartTrack and background login occurs. Do we have to scan for new vehicles and download them here? 
 +  - Display the Vehicle selection. Pressing select assigns the machine in the combo box. Picking from the combo box displays the vehicle characteristics. Pressing Cancel bypasses machine assignment and then all we have is a tracker id.
 +  - After vehicle selection SmartTrack needs to check with the server for configuration and/or configuration changes and load them.
 +
 +Other future options may include bar codes or RFID tags. RFID would be fairly unobtrusive to the user but dependent on mounting that I'm not sure we can rely on. Scanning requires user action in scanning the codes and also limits devices to those with cameras.
 +
 +
  
 ==== Information Flow & Requirements ==== ==== Information Flow & Requirements ====
android/track/trackstories.1395874022.txt.gz · Last modified: 2014/03/26 22:47 by mikeclapp