= SAMBRO Mobile Application =
[[TOC]]

== Introduction ==
The app is supposed to be a mobile app to issue alerts for several hazards to be included into SAMBRO/Sahana.

The app will complement the web based GUIs for issuing alerts to enable a mobile solution even working in 
areas with weak internet connectivity.

An existing similar solution is [http://www.capacitylab.org/mobile4d mobile4D], a bi-directional hazard reporting and alerting tool developed at
the Capacity Lab at the University of Bremen.


{{{#!comment
<Briefly describe the solution?>[[BR]]
<What problem is this solution solving?>[[BR]]
<How will this solution add value to Sahana?>[[BR]]
<Name any similar existing solutions>[[BR]]
}}}

== Stakeholders ==
<Who will be the users of the solution?>[[BR]]
<Who else will be affected by this solution? eg. Developers, Users of Existing Functionality that may be changed?>[[BR]]
<How will stakeholders be affected?>[[BR]]
Tip: Engage these stakeholders in the development of your !BluePrint.

== User Stories ==
An authorized user finds himself in a situation where he/she is in the need to issue an alert, but does not have access to a computer or/and a sufficiently stable internet connection. The user can now use the app and fill in the data via a structured interface. After confirming the data, the app takes over and sends the data to the Sahana server as soon as internet connection is available again without the user having to take care of it. (Alternatively, the app uses SMS to send the data. This is transparent to the user.)

{{{#!comment
<http://en.wikipedia.org/wiki/User_story>
<A good User Story should answer the following questions:>
<* Who the user is>
<* What they want the solution to do for them?>
<* Why they want it to do that? (goal)>
<eg. A <type of user> wants the solution to <do something for them> so that <can achieve a goal>.>
}}}

== Requirements ==
<Group requirements in subsections, e.g.,, etc.>
<http://en.wikipedia.org/wiki/Requirements_analysis requirements>
<Identify different types of requirements:>
=== Functional ===
 * Simple interface
 * step by step input
 * must work without internet connectivity
 * alerts are a buffered and automatically sent as soon as the internet connection comes up again
 * satisfies a subset of CAP
=== Non-functional ===
http://en.wikipedia.org/wiki/Non-functional_requirements
=== Interoperability ===
=== Standards ===
 * Results are sent out in CAP
=== System Constraints ===

The system has to be operational by late March. 
== Design ==
<Where relevant include alternative design options>
=== Data Model ===
(e.g. EER or class diagrams)
=== Workflows ===
<Diagrams or Pseudocode> 
=== Site Map ===
<for User Interface solutions>
=== Wireframes ===
<for User Interface solutions>
=== Technologies ===

== Current Implementation ==
{{{#!comment
<Leave open for a list of existing implementation of this solution in Sahana Eden:>
<*a brief description of the implementation (date/time, name, design options chosen)>
<*a link to the code>
<*list of deployments of the implementation>
<*links to case studies>
<*short analysis of achievements/problems>
}}}

Currently, there is no implementation within Sahana Eden.

* Step 1. Test the current SAMBRO GUIs for its responsiveness to mobile handhelds. If necessary suggest some GUI tweaks to harmonize the desktop version with the mobile screens.

* Step 2. Design hazard specific alert authoring and issuing GUIs. For example, Alerting Authorities, in a local area (Barangay, Gramaniladari, Thaluk, etc) do not need the full CAP message but a few attributes like the area and water level. We will target on delivering 3-5 mobile GUIs for Landslide, Flood, Accident,

* Step 3. Develop the requirements/design for using the concept of Pictographs in Alerting and other features such as a wake up function to sound an Audible Alarm etc. I think we should do the same with the web GUI such that we can set a siren audio to sound for a specific warning_priority threshold.

We may have to look for funding outside of the ESCAP project for step 3.
== Planned Implementation ==

To meet the time constraints given above, the plan is as follows:

 * Use a stripped-down version of the mobile4D mobile client (for Android)
 * enhance the functionality by the needed report types not supported yet
 * have the client deliver valid CAP directly from the device (the current implementation uses the mobile4D protocol and converts this to CAP server-sided)

The current functionality includes:

 * Send hazard reports:
  * filling in needed fields (numbers, contact details, urgency, etc.)
  * detect the current location
  * alternatively give a location and specifying a polygon on a map

* Buffer issued reports and re-send them upon network connectivity.

* Retrieve alerts and display them as list and map. This will most probably not be included.

* Many more communication features that might not be included either. 

== Future Extensions ==
<List of features which could be included, but are outside of the scope of this extension>

== Outstanding Questions ==
<Questions about the features or design that haven't been (and need to be) answered>

== References ==
* [http://eden.sahanafoundation.org/wiki/BluePrint/CAPBroker SAMBRO CAP Broker Blueprint]