Difference between revisions of "GravidPluss:Roadmap for App Development"

From its-wiki.no
Jump to: navigation, search
(Infrastructure at the hospitals)
(Design)
Line 16: Line 16:
 
= Conclusions =
 
= Conclusions =
 
== Design ==
 
== Design ==
Design templates are ready. Use of Luton(?) font family is okay for printed brochures, but might cause problems  
+
Design templates are ready. Use of Lato font family is okay for printed brochures, but might cause problems  
 
* in Android and Apple: '''Iñaki to check''' about size of download (which will increase the app size).
 
* in Android and Apple: '''Iñaki to check''' about size of download (which will increase the app size).
 
* For powerpoint we should use standard fonts, as a distributed powerpoint should look equal on all machines, regardless if the font is installed or not.
 
* For powerpoint we should use standard fonts, as a distributed powerpoint should look equal on all machines, regardless if the font is installed or not.

Revision as of 16:20, 25 March 2014


GravidPluss:Roadmap for App Development

Title GravidPluss:Roadmap for App Development
Place UNIK
Date, Time 2014/03/25, 0900-1200
Contact Person Lisa Garnweidner
Participants Josef Noll, Mirjam Lukasse, Iñaki Garitano, Seraj Fayyad
related to Project GravidPluss
Keywords
this page was created by Special:FormEdit/Meeting, and can be edited by Special:FormEdit/Meeting/GravidPluss:Roadmap for App Development
Category:


Main focus on

  • Roadmap for App development
  • Requirements for apps
  • Bluetooth interface

Conclusions

Design

Design templates are ready. Use of Lato font family is okay for printed brochures, but might cause problems

  • in Android and Apple: Iñaki to check about size of download (which will increase the app size).
  • For powerpoint we should use standard fonts, as a distributed powerpoint should look equal on all machines, regardless if the font is installed or not.

The design is that universal that we might use it for a bigger project around pregnancy (worldwide?)

Questionnaire

Questionnaire roadmap includes three dates, prior to week 30, week 36 (og pregnancy) and 6-12 weeks after birth. The draft version of the questionnaire is ready. We will have three steps,

  • (1) prior to week 30, getting the initial data from the participants. Here we will also create the randomised participant number based on the mobile phone number and the hospital
  • (2) the second questionnaire, giving an initial feedback on habits, eating, activities
  • (3) the third questionnaire will take place 6-12 weeks after birth. We intend to use an SMS to remind participants to go to the web page and fill in the final questionnaire. The SMS will include a unique code, which will be used to relate the answer to the person.

Randomizer

Our starting point is that we use a random number generated from the phone number and the hospital. Thus, when the participant fills in the first questionnaire, she will add here mobile phone number, the week of pregnancy (to exclude if entered week 31), and the hospital. By entering the mobile phone number, and "return", the sheet will be randomised.

  • do we need to check that the number typed in is written correctly? That will require an own "sms sender" (from UNIK)
  • we need to establish Wifi infrastructure at all hospitals in order to be able to work "online"

App Roadmap

We foresee the first app being ready around July 2014, based on an Android Emulator on the PC. In order to make updates as easy as possible, we will have most of the information on the server, and only initial text and the outer design blocks on the device. This will allow and easier update of information without updating the app.

We concentrate on iOS (Apple) and Android (Google), as Microsoft is probably used only for 1-2 participants ("sorry, you can't participate).

  • Lisa will work on the outer design. Iñaki will provide a framework for the design work.
  • the first design will be created in an Android emulator on the PC/MAC.
  • The real version will then be generated as soon as the design is stable. It takes 6-8 weeks to get an app approved in Apple Market, and about 2-3 weeks in Google.

We want to limit the usage of the app. The favoured suggestion is to use the mobile phone number as a "one time login" after installation. If the phone number is on our list, then the full app functionality will be opened. Otherwise only information is provided to users of the app. Iñaki checks the conditions for company development and roll out (restricted number of devices in AppStore).

Infrastructure at the hospitals

Ullevål is probably the hospital with the most difficult solution to set up Wifi. We will first have a meeting with the data privacy responsible, which Mirjam will organise. Then we will discuss further the possibilities, probably already starting in April with checking the infrastructure.

Kick-off

  • Josef to focus on both app development, opportunities, challenges, and restrictions.
    • advantages of using Web pages
    • using Bluetooth and phone interaction
    • Bluetooth set-up and blood sugar measurement units.
  • Everyone is free to set up tasks for participants.

AOB

Forgotten something? Please add it on this page