Implement as much offline functionality (with AppCache) as possible

[fabacab]

See http://docs.webplatform.org/wiki/apis/appcache/ApplicationCache for details on AppCache.

Let's brainstorm: what should be do-able offline?

[fabacab]

Neat.

Let's brainstorm: what should be do-able offline?

Hm. I'd say…

• Anything the user wants to do with the profile section.
• Create/delete groups and edit group membership. (But maybe not send invites? Unless those can be cached and sent automatically next time the user is online. It's not clear from my quick skim of the AppCache documentation whether this is possible.)
• Browse lists of public responders (re: betterangels/better-angels#81)
• View most recently cached version of the map associated with any active alert (this one seems especially important in case the alerter/a responder gets kicked offline during a crisis)
• Should we allow people to set safecalls while they're offline? I think this also depends on whether that info can be sent to the server automatically next time the user is online. (And would still require warning the user that the safe call won't be activated unless they are online sometime between setting it and deployment time.)

Just a few first thoughts.

[fabacab]

:+1:

I think the priority in this issue should be to get the mapping interface to work offline, thought that might be difficult. It might also require switching away from Google Maps. This is related to betterangels/better-angels#62 and betterangels/better-angels#18.

[fabacab]

Agreed, the map seems like the most important feature to prioritize.

[fabacab]

Another thing to look into for offline functionality is PouchDB.