# Challenges and best practices when designing a mobile application for the ELIPSS panel

Geneviève Michaud, Quentin Agren

## ► To cite this version:

Geneviève Michaud, Quentin Agren. Challenges and best practices when designing a mobile application for the ELIPSS panel. CSDI. International Workshop on Comparative Survey Design and Implementation Program, Mar 2019, Varsovie, Institute of Philosophy and Sociology, Polish Academy of Sciences, Poland. hal-02874080

HAL Id: hal-02874080

https://sciencespo.hal.science/hal-02874080

Submitted on 19 Dec 2022

HAL is a multi-disciplinary open access
archive for the deposit and dissemination of sci-
entific research documents, whether they are pub-
lished or not. The documents may come from
teaching and research institutions in France or
abroad, or from public or private research centers.

L'archive ouverte pluridisciplinaire HAL, est
destinée au dépôt et à la diffusion de documents
scientifiques de niveau recherche, publiés ou non,
émanant des établissements d'enseignement et de
recherche français ou étrangers, des laboratoires
publics ou privés.

<figure><img src="image_1.png" /></figure>

Distributed under a Creative Commons Attribution 4.0 International License
# Challenges and best practices when designing a mobile application for the ELIPSS panel

CSDI workshop 18–20 March Warsaw
Institute of Philosophy and Sociology, Polish Academy of Sciences

Quentin Agren, Geneviève Michaud, CDSP Sciences Po Paris
# Presentation outline

## 1. ELIPSS Study

a probability-based internet panel

## 2. ELIPSS Infrastructure

## 3. Challenges

a. challenge #0 getting the timing right

b. challenge #1 providing a connected device

c. challenge #2 choosing a device model

d. challenge #3 managing a mobile fleet

e. challenge #4 designing a mobile app

f. challenge #5 developing for interactive surveys
# Longitudinal Internet Studies for Social Sciences

- 9-year grant from the French National Research Agency (ANR-10-EQPX-19-01) [DIME-SHS](https://dime-shs.fr/)

- probability-based sample (from 18 to 83 years old)

- sample size:

- pilot study: 2012 - 2016 +1000 panellists

- main study: 2016-2019 +3200 panellists

- 2 full-time staff members dedicated to support and follow-up respondents

- panellists unconditionally equipped with a 4G-enabled touchscreen tablet
# a software infrastructure backing a mobile fleet

A mobile fleet:

- one single device model at a time

- managed in-house from stock management to troubleshooting

Incrementally built software suite, including:

- sample management interfacing with

- survey platform

- fleet management

- monitoring dashboard

- native mobile application

<figure><img src="image_2.png" /><figcaption>Self-hosted infrastructure</figcaption></figure>
# a survey platform and a mobile application

early choice of a survey platform: [Blaise®](#)

**assets:** complete set of social sciences survey methods

**shortcomings:** basic web rendering, not mobile-friendly

<figure><img src="image_3.png" /></figure>

**Best of two worlds:** a mobile app to enhance survey rendering while leveraging the proficient survey backend for development

<figure><img src="image_4.png" /></figure>
## challenge #0 getting the timing right

- **Synchronise** project planning and manufacturer's schedule.

- Ensure hardware **quality** guarantees a study-long **lifespan**.

- Anticipate losses and maintain model homogeneity by ordering **spare stock**.
## challenge #1 offering a durable incentive

attractive device + mobile subscription = **timeproof incentive**

- at **recruitment** time: appealing device

- to control **attrition**: data subscription is a stable incentive, whereas device attractivity may quickly drop in a fast evolving market
## challenge #2 choosing a device model

<table><thead><tr><th>pilot study (Samsung GTP3100)</th><th>main study (Archos 80b Helium)</th></tr></thead><tbody><tr><td>good hardware quality</td><td>limited hardware quality</td></tr><tr><td>no technical support from constructor</td><td>support from constructor's R&D enabled customisations simplifying management</td></tr></tbody></table>

The choice of a model affects **device management capabilities**.
## challenge #3 managing a mobile fleet

**hardware inventory**

real-time fleet **inventory**

**software update control**

ELIPSS application and software dependencies must always be installed and match a specific version

**remote control**

remote **support** demands a tool to take remote control of devices
<figure><img src="image_5.png" /></figure>

<figure><img src="image_6.png" /></figure>

2. on boot and
recurring
requirements
checking

<figure><img src="image_7.png" /></figure>

<figure><img src="image_8.png" /></figure>

ELIPSS application repository

<figure><img src="image_9.png" /></figure>

<figure><img src="image_10.png" /></figure>

<figure><img src="image_11.png" /></figure>

1. production (or
pre-production)
firmware installation

3. application download
(if missing or out of date)

<figure><img src="image_12.png" /></figure>

4. hardware and software
inventory data pushed by
application

<figure><img src="image_13.png" /></figure>

real-time inventory information available for support staff
## challenge #4 designing a mobile app

a minimal app to serve the needs of research

- staff-editable welcome message

- native pop-up messages

- offline features

- FAQ and staff contact

- online features

- change password and edit profile information

- available survey(s)

- closed surveys with global statistics

<figure><img src="image_14.png" /></figure>
**collecting paradata frugally**

Developing a custom Android application allows **passive and comprehensive** paradata collection.

But without prior panellist consent, paradata collection must be kept:

- frugal

- device-management oriented
<figure><img src="image_15.png" /></figure>

actual ELIPSS app permissions

# permissions

Permissions requested by ELIPSS application are a combination that must allow for:

- limited paradata collection

- survey data collection

<table><thead><tr><td>Permission Group</td><td>Permissions</td></tr></thead><tbody><tr><td>CALENDAR</td><td><ul><li>READ_CALENDAR</li><li>WRITE_CALENDAR</li></ul></td></tr><tr><td>CALL_LOG</td><td><ul><li>READ CALL_LOG</li><li>WRITE CALL_LOG</li><li>PROCESS_OUTGOING Calls</li></ul></td></tr><tr><td>CAMERA</td><td><ul><li>CAMERA</li></ul></td></tr><tr><td>CONTACTS</td><td><ul><li>READ_CONTACTS</li><li>WRITE_CONTACTS</li><li>GET_ACCOUNTS</li></ul></td></tr><tr><td>LOCATION</td><td><ul><li>ACCESS Fine Location</li><li>ACCESS Coarse Location</li></ul></td></tr><tr><td>MICROPHONE</td><td><ul><li>RECORD AUDIO</li></ul></td></tr><tr><td>PHONE</td><td><ul><li>READ PHONE_STATE</li><li>READ PHONE NUMBERS</li><li>CALL PHONE</li><li>ANSWER PHONE CALLS</li><li>ADD VOICEMAIL</li><li>USE_SIP</li></ul></td></tr><tr><td>SENSORS</td><td><ul><li>BODY Sensors</li></ul></td></tr><tr><td>SMS</td><td><ul><li>SEND_SMS</li><li>RECEIVE_SMS</li><li>READ_SMS</li><li>RECEIVE WAP PUSH</li><li>RECEIVE MMS</li></ul></td></tr><tr><td>STORAGE</td><td><ul><li>READ_EXTERNAL_STORAGE</li><li>WRITE_EXTERNAL_STORAGE</li></ul></td></tr></tbody></table>

"dangerous android permissions"
# user interface

Designing a straightforward, accessible interface

<figure><img src="image_16.png" /></figure>

<figure><img src="image_17.png" /></figure>

same but different: pilot study (7") and main study (8") application homepage
## challenge #5 developing for interactive surveys

Over time, growing library of survey questions interactions.

- fine-tuning non response options

- auto-complete, ordered items list

- experimenting with rich interactions and multimedia content (video, maps)

- use of device sensors (voice recording, camera)
<figure><img src="image_18.png" /></figure>

<figure><img src="image_19.png" /></figure>

<figure><img src="image_20.png" /></figure>
<figure><img src="image_21.png" /></figure>

<figure><img src="image_22.png" /></figure>

<figure><img src="image_23.png" /></figure>
feedback
thank you!

SciencesPo-CDSP IT team throughout the ages:

Adam Schaal, Daniele Guido, Adrien Ferreira, Alexandre Chevallier, Raphaël Paoloni, Anthony Jacques,

<u>Jérémy Richard, Romain Mougin, Baptiste Rouxel, Quentin Agren, Simon Dellac</u>
<figure><img src="image_24.png" /><figcaption>ELIPSS software toolbox fact sheet</figcaption></figure>
pilot study and main study equipment: comparison

<table><tr><td></td><td>Samsung GTP3100</td><td>Archos 80b Helium</td></tr><tr><td>Size</td><td>7.0 inches,<br>(~58.2% screen-to-body ratio)</td><td>8.0 inches,<br>(~72.46% screen-to-body ratio)</td></tr><tr><td>Resolution</td><td>600 x 1024 pixels,<br>(~170 ppi density)</td><td>768 x 1024 pixels,<br>(~160 ppi density)</td></tr></table>

<figure><img src="image_25.png" /><figcaption>Samsung GALAXY Tab 2 (7.0)</figcaption></figure>

193.7 x 122.4 x 10.5 mm | 344 g

<figure><img src="image_26.png" /></figure>

<figure><img src="image_27.png" /><figcaption>ARCHOS 80b Helium 4G</figcaption></figure>

210 x 122 x 9.3 mm | 320 g