iotmeetupguildford#9: iot lab – crowdsourcing mobile app for iot experimentation - nikos loumis -...
TRANSCRIPT
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 [email protected] 2
• 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 [email protected] 3
• 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 [email protected] 4
• 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 [email protected] 5
• Download using QR-Code
Installing App
• Settings → Security →
Uknown sources → On
IoT Lab Application
Tuesday, March 17, 2015 [email protected] 6
First Boot
• User has to accept IoT Lab terms.
• Never shown again, once accepted.
Tuesday, March 17, 2015 [email protected] 7
New User (1/2)
• User has the option to offerhis personal details.
• User can provide only his/herpreferred details.
Tuesday, March 17, 2015 [email protected] 8
New User (2/2)
• Settings profile storedinside application.
• A copy of them isuploaded to IoT LabServer.
Tuesday, March 17, 2015 [email protected] 9
Side Menu
• Access to users profile.
• Navigation through theprovided functionalities.
• Follows Google’s designguidelines.
Tuesday, March 17, 2015 [email protected] 10
Survey Provider
• Surveys pushed from the Cloud.
• Stored inside the app for latteruse.
• Direct access through the IoT Labapplication UI.
Tuesday, March 17, 2015 [email protected] 11
Experiment Proposal (1/3)
• Automated procedure.
• Easy to use.
• User “forced” to providethe requiredinformation.
Tuesday, March 17, 2015 [email protected] 12
Experiment Proposal (2/3)
• Selection of the resources needed.
• User input minimised to avoid problems.
Tuesday, March 17, 2015 [email protected] 13
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 [email protected] 14
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 arenever shown again.
Tuesday, March 17, 2015 [email protected] 15
Experiment Feedback(2/3)
• Experiment resources arepresented to the user.
• Required resources categorised bytype.
• Feedback provided by the toolbarbutton.
Tuesday, March 17, 2015 [email protected] 16
Experiment Feedback(3/3)
Popup dialog with instructionsdisplayed to the user.
• Easy input method. Similar to whatuser has encountered in the past.
• Response send to the IoT Labserver.
Tuesday, March 17, 2015 [email protected] 17
Application Configuration
• User can select his exposed sensors anytime.
Tuesday, March 17, 2015 [email protected] 18
Date:
App type:
App utility:
Good:
Bad:
Missing:
What would you dodifferently?
What adjunctiveFunction wouldyou like to have?
Perceive privacy
NOTES:
Feedback
Tuesday, March 17, 2015 [email protected] 19