Crowdsourcing mobile app for IoT experimentation

1. IoT Guildford Meetup

2. Crowdsourcing & Crowdsensing
• Direct interaction with the crowd
• Crowd at the spotlight of the research
cycle
• Align research with the society/users
needs and requirements
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 2

3. • IoT Lab is building and providing a Testbed as a
Service to the research community
• Integration of IoT testbeds with crowdsourcing
resources
Testbed as a Service
• Introducing
multidisciplinary
research potential
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 3

4. • IoT Lab is researching the potential of the crowd to
interact through the whole cycle of the research, from
its inception to the evaluation of its results
Crowd-sourcing Driven Research
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 4

5. • Extend test beds with crowd sourcing for richer and more
distributed experiments.
• Bring researchers and end-users together, with pervasive /
ubiquitous experiments and closer interactions with the
society.
• Support multidisciplinary experiments.
• Increase test bed economic sustainability
• Crowd-sourcing driven research
• Testbed as a service
IoT Lab Vision
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 5

6. • Download using QR-Code
Installing App
• Settings → Security →
Uknown sources → On
IoT Lab Application
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 6

7. First Boot
• User has to accept IoT Lab
terms.
• Never shown again, once
accepted.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 7

8. New User (1/2)
• User has the option to offer
his personal details.
• User can provide only his/her
preferred details.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 8

9. New User (2/2)
• Settings profile stored
inside application.
• A copy of them is
uploaded to IoT Lab
Server.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 9

10. Side Menu
• Access to users profile.
• Navigation through the
provided functionalities.
• Follows Google’s design
guidelines.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 10

11. Survey Provider
• Surveys pushed from the Cloud.
• Stored inside the app for latter
use.
• Direct access through the IoT Lab
application UI.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 11

12. Experiment Proposal (1/3)
• Automated procedure.
• Easy to use.
• User “forced” to provide
the required
information.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 12

13. Experiment Proposal (2/3)
• Selection of the resources
needed.
• User input minimised to
avoid problems.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 13

14. Experiment Proposal (3/3)
• Review of the proposed experiment.
• Experimenter can go back to any
stage to change the experiment’s
preferences.
• Confirmation popup dialog before
finalising the proposal.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 14

15. Experiment Feedback(1/3)
• New proposed experiment is pushed
to the user.
• A notification leads the user to the
“feedback Activity”.
• Instructions are displayed to the user.
• If selected by the user, instructions are
never shown again.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 15

16. Experiment Feedback(2/3)
• Experiment resources are
presented to the user.
• Required resources categorised by
type.
• Feedback provided by the toolbar
button.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 16

17. Experiment Feedback(3/3)
Popup dialog with instructions
displayed to the user.
• Easy input method. Similar to what
user has encountered in the past.
• Response send to the IoT Lab
server.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 17

18. Application Configuration
• User can select his exposed sensors anytime.
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 18

19. Date:
App type:
App utility:
Good:
Bad:
Missing:
What would you do
differently?
What adjunctive
Function would
you like to have?
Perceive privacy
NOTES:
Feedback
Tuesday, March 17, 2015 n.loumis@surrey.ac.uk 19

20. THANKS.
www.iotlab.euTuesday, March 17, 2015 n.loumis@surrey.ac.uk 20