Mobile SDK > Implementation strategy
 
Implementation strategy
The strategies for implementing mobile applications are based on the application's connectivity requirements.
The disconnected strategy supports true mobile personal interviewing similar to the existing UNICOM Intelligence Interviewer - Offline for Windows product. The mobile device is preinstalled with an application that coordinates interviewing. The interviewer downloads a survey (or set of surveys) to the mobile device, interviews respondents, and enters respondent answers with the device. The interview data is later uploaded for analysis.
The connected mode solution requires a connection for every interview page. It provides value, over using the device’s browser to conduct interviews, in that the respondent interface can be better customized to the each individual device.
The connected mode solution can also be extended to support a partially connected option. The solution is accomplished by setting up the survey as a single large block that can be retrieved in one connection. The survey is then broken into individual pages for ease of interaction with the respondent. This option supports minimal routing but requires less effort to implement than the disconnected solution.
Connection modes
The following table compares the Disconnected, Partially Connected, and Connected modes. Later sections discuss the Connected and Partially Connected implementation strategies together, as the Partially Connected strategy is an extension of the Connected strategy.
 
Disconnected
Partially Connected
Connected (online)
Primary usage
Interviewer led mobile personal interviewing.
Respondent led interviewing.
Respondent led interviewing.
Connectivity requirement
A connection is required for downloading projects and uploading respondent data.
No connection is required during interviewing.
A connection is required to download and submit each interview block.
The interview block can be divided into multiple pages and presented to the respondent.
A connection is required to download and submit each interview.
Retrieve/Submit fragment
Full projects are synchronized down.
Full respondent records are synchronized up.
A page of questions (can be a page, block, or loop iteration) is retrieved and submitted.
Each page is retrieved and submitted.
UNICOM Intelligence mode
Personal (mobile)
UNICOM Intelligence Interviewer - Server Admin activities support assigning interviewers to projects and tracking their progress.
Web
Web
Required components
Mobile application that manages projects and interviews.
Mobile application that processes routing and question information, and interacts with the respondent to gather data.
Mobile web service that translates client style files to UNICOM Intelligence style files (examples are provided in the Mobile SDK).
Interviewing shell that submits and retrieves interview blocks, separates blocks into interviewing pages, and presents each page as required (an example is provided with the Mobile SDK).
Rendering component (an example is provided with the Mobile SDK).
Interviewing shell that submits and retrieves interviewing pages (an example is provided with the Mobile SDK)
Rendering component (an example is provided with the Mobile SDK).
Advantages
Stand-alone application that requires no connection during interviewing.
Supports simple routing, for example diary style studies, without requiring a permanent connection.
All routing logic is run on the server, which is the easiest method for providing full routing support.
Disadvantages
A more complex mobile application is required to handle project management and routing.
Supports only simple routing (Paper support).
Requires a permanent network connection.
See also
UNICOM Intelligence Mobile SDK