1 / 20

Developing Responsive Mobile Web Systems Using an Open Source Framework Christopher Siege, Debra Fleischmann

Developing Responsive Mobile Web Systems Using an Open Source Framework Christopher Siege, Debra Fleischmann. FedCASIC Washington, DC March 20, 2014. Outline. Mobile Data Collection Options Driving Factors for Approach Project Requirements Open Source Framework Case Study Challenges.

gefjun
Download Presentation

Developing Responsive Mobile Web Systems Using an Open Source Framework Christopher Siege, Debra Fleischmann

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Developing Responsive Mobile Web Systems Using an Open Source FrameworkChristopher Siege, Debra Fleischmann FedCASIC Washington, DC March 20, 2014

  2. Outline • Mobile Data Collection Options • Driving Factors for Approach • Project Requirements • Open Source Framework • Case Study • Challenges

  3. Mobile Data Collection Options • Traditional Websites • Viewable on mobile devices but often times difficult to navigate menus, perform tasks and view content • Native Mobile Applications – “Apps” • Written specifically for device platform (Android, iOS, Windows Phone) and is installed on the local device • Mobile Websites • Optimized for mobile devices by incorporating responsive web designs that visually adapts to the device size

  4. Driving Factors for Approach • Labor Costs • Software Licensing • Hardware • Schedule • Usability • Web Accessibility • Performance • Rich Functionality • User Expectations • Survey Mode • CAPI • Web SAQ • Device Support • Security • Bring Your Own Device (BYOD)

  5. Driving Factors for Approach • Each option addresses some factors with some overlap • No single best option for all scenarios • Solution must match project and user needs Mobile Websites Traditional Websites Native Mobile Applications “Apps”

  6. Case Study Project Requirements • Cost Effective • Rapid Development • Respondent Data Collection • Study Data Collection • Operational Management • Multi-Device Support (BYOD) • Section 508 • FIPS Moderate Security

  7. Project Requirements Chosen Solution • Respondent Data collection • Study Data Collection • Operational Management • Microsoft .NET Framework • Multi-Device Support (BYOD) • Section 508 • Mobile Web Approach • Open Source Toolkit • Accelerate Development • Multi-Device Support • Security - FIPS Moderate • RTI Virtualized Private Cloud • Cost Effective • Rapid Development • Applies to all solutions

  8. Case Study Project Requirements Mobile Web Solution Selection • Open source and commercial options assessed • Responsive Web Design options increasing • Selection of Web Experience Toolkit solution • Mobile Web Approach • Open Source Toolkit • Accelerate Development • Multi-Device Support • Multi-Device Support (BYOD) • Section 508 • Cost Effective • Rapid Development

  9. Web Experience Toolkit • Led by Government of Canada • Open source • First-Class Mobile Device Support • Community Development / Support • Featured: • http://government.github.com/ • http://howto.gov

  10. Web Experience Toolkit • Built using latest web technologies • HTML5 • CSS3 • JavaScript • Reusable • Themes • Plug-ins • Web Accessibility • Conforms to WCAG 2.0 level AA • Leverages WAI-ARIA to further enhance web accessibility • Addresses many Section 508 provisions

  11. Case Study: REDS-III • Recipient Epidemiology and Donor Evaluation Study-III • National Heart, Lung, and Blood Institute (NHLBI) • National Institutes of Health (NIH) • Data Coordinating Center • RTI International • Numerous Data Collection Efforts • Electronic Medical Record Extraction • Clinical Study Management • Enrolled Subject Data Collection • Computer Assisted Personal Interviewing • Web-based Self Administered Questionnaires 11

  12. Case Study: REDS-III 12

  13. Case Study: REDS-III 13

  14. Case Study: REDS-III 14

  15. Case Study: REDS-III 15

  16. Case Study: REDS-III 16

  17. Case Study: REDS-III 17

  18. Challenges • Development Integration • Toolkit Customizations • Predictability of Change • Legacy Browser Support • Modern Browser Differences • User Expectations

  19. Conclusion • Success • Multi-study / multi-mode data collection • Positive end user experience • Flexible device support • Web Experience Toolkit • http://wet-boew.github.io/wet-boew

  20. More Information Christopher Siege Senior Software Engineer 919.485.5605 Research Computing Division csiege@rti.org Debra Fleischman Data Management Director 919.541.6367 Environmental and Health Science dmf@rti.org

More Related