Changes between Version 11 and Version 12 of BluePrint/CAPMobileApp


Ignore:
Timestamp:
01/17/16 22:19:26 (6 years ago)
Author:
Lutz Frommberger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/CAPMobileApp

    v11 v12  
    8080
    8181== Planned Implementation ==
    82 <List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>
    8382
     83* Step 1. Test the current SAMBRO GUIs for its responsiveness to mobile
     84handhelds. If necessary suggest some GUI tweaks to harmonize the
     85desktop version with the mobile screens.
     86
     87* Step 2. Design hazard specific alert authoring and issuing GUIs. For
     88example, Alerting Authorities, in a local area (Barangay,
     89Gramaniladari, Thaluk, etc) do not need the full CAP message but a few
     90attributes like the area and water level. We will target on delivering
     913-5 mobile GUIs for Landslide, Flood, Accident,
     92
     93* Step 3. Develop the requirements/design for using the concept of
     94Pictographs in Alerting and other features such as a wake up function
     95to sound an Audible Alarm etc. I think we should do the same with the
     96web GUI such that we can set a siren audio to sound for a specific
     97warning_priority threshold.
     98
     99We may have to look for funding outside of the ESCAP project for step 3.
    84100== Future Extensions ==
    85101<List of features which could be included, but are outside of the scope of this extension>