One that may be missing and can be of relevance is having a night mode. Screens may be to bright for its night use, and sometimes this may compromise security/safety. Normally it will switch the background color to black and use red/blue/green for text.

In terms of UI, and this may be exclusively out of personal experience, persistent tabbed browsing can provide some benefits. Another path could be sliding panels to send loading apps to the background.

Anyway, will post other ideas if they come.

One that may be missing and can be of relevance is having a night mode. Screens may be to bright for its night use, and sometimes this may compromise security/safety. Normally it will switch the background color to black and use red/blue/green for text.

In terms of UI, and this may be exclusively out of personal experience, persistent tabbed browsing can provide some benefits. Another path could be sliding panels to send loading apps to the background.

Anyway, will post other ideas if they come.

2. Steganography: You might not want to be seen to be doing any kind of data collection. Can the application and data be hidden? Can the mobile device you're using just look like your personal phone?

3. Separate data from app: I agree that keeping data stored/backed up on something like and SD card is very important but makes the encryption element potentially more important. Consider keeping the configured application & state stored on the SD card too – i.e. you can rapidly swap to a “warm spare” device is the first fails or is compromised.

4. Simulation / Training / Documentation: recognise that if the application is going to be used by agencies in a relief situation, they are going to want to field trial the heck out of it, conduct training on it and provide documentation. Put effort into supporting this.

2. Steganography: You might not want to be seen to be doing any kind of data collection. Can the application and data be hidden? Can the mobile device you're using just look like your personal phone?

3. Separate data from app: I agree that keeping data stored/backed up on something like and SD card is very important but makes the encryption element potentially more important. Consider keeping the configured application & state stored on the SD card too – i.e. you can rapidly swap to a “warm spare” device is the first fails or is compromised.

4. Simulation / Training / Documentation: recognise that if the application is going to be used by agencies in a relief situation, they are going to want to field trial the heck out of it, conduct training on it and provide documentation. Put effort into supporting this.

This is a good list. I've been thinking about an emergency preparedness application so some other ideas come to mind that may apply depending upon the application…

Allow hands/eyes free audio interaction when the user may be following instructions from the device, such as when being directed to render first aid.

The application can be used to deliver timed reminders

Ideally the app adapts to a wide variety of hardware capabilities such as screen size, presence of BT, data plan etc.

The app should remain useful in an offline situation. The cell network may be temporarily down. The app should store and forward, opportunistically. All functions should be considered and designed in their online and offline modes.

The app should anticipate required actions that will occur in duress. For example, when installed, it should remind the user to input key ICE (In case of emergency) information until it is done.

Good luck in this!

I also have to reiterate from my list that all data should be persisted on removable media, like SD Cards, instead of on the device itself. That way you can always quickly switch devices, load the data on a PC, etc…. and even, if necessary, you can protect sensitive information by swallowing it!

Here is some potenital ideas on types of feedback for confirmations:

- Loud beep tone sequences: upward sequence for success, downward sequence for failure/error

- Change entire screen background color: White for input, Green for success, Red for failure

- On Android, proper use of status bar notifications is essentially… subtle notifications that don't interrupt the current workflow, while still letting you know there is new information to review when you have a minute.