This page is intended to outline the process of working with the University to develop and publish a mobile application.  Please note that this is a general outline, and that your own mobile application development may take a slightly different path to publication, in particular if you decide to hire a 3rd party development firm to assist with your app development.

Proposal: University student/faculty/staff proposes idea or concept for mobile application

  • At time of proposal, developer may or may not have a working prototype application to demonstrate
  • Appropriate points of contact will be published via appropriate communication mediums
  • Proposer should contact an appropriate member of the mobile computing advisory committee to schedule a time to propose and/or demo their application
  • If proposed application will impact students, STAC should review the proposal and stay informed of future developments

Development: University student/faculty/staff develops mobile application on their own, through a WUSTL course, or in conjunction with WUIT (via future WUIT mobile development “sandbox”)

  • Developer may use their own hardware and/or software to create mobile app
  • Applications developed in a WUSTL course should have the support of the instructor before submitting for review
  • Developers may request access to WUIT sandbox resources (future) through STAC or the WUIT Mobile Computing Advisory Committee

Review: The developer of the application submits application source files for review of:

  • Stability and functionality
  • Appropriate commenting of code for future support
  • WUSTL branding
  • Security and regulatory compliance (if accessing secure data)
  • Privacy assurance (FERPA)
  • Provided to end-users at no charge
  • Exclusion of any advertisements or in-app purchase proposals

Publication: WUIT submits app for publication via Apple’s App store, or other mediums

  • In order for a mobile app to have access to WUIT data, or be published in conjunction with the University, the developer must sign an agreement with WUIT that they will abide by appropriate policies and procedures
  • Once the review is complete and agreements signed, an appropriate member of the WUIT Mobile Computing Advisory Committee will submit app for publication
  • WUIT will monitor status of approval/publication process and report back to developer and/or STAC if any changes in the application are required
  • WUIT will inform developer, STAC and other affected parties when application is published and available for download

Support: Ongoing support for published applications will be provided by developer

  • Application developer responsibilities:
    • Maintaining and updating application
    • Fielding support requests from end-users of the application
    • Submitting re-run through the WUIT review process before the update is published
  • WUIT Responsibilities:
    • Supporting the “handshake” to WUIT maintained systems and databases
    • Testing how changes to WUIT systems will impact existing mobile apps
    • Submitting approved application updates for publication
    • Managing mobile application “portfolio”