Mobile App Offline Storage

### A brief description of the feature or enhancement you'd like to see:
A clear and concise description of what the feature or enhancement is, Ex. Using this tool be would be much easier if [...]
Provide offline storage in mobile application.

### How will this feature be used?
A clear description of how, who, and when this feature would be used. Ex. User A wants to create a new Incident [...]
Store incident data which cannot be submitted, possible reasons
- No internet
- Poor internet

### What is the impact of this feature/enhancement?
Describe the impact of this feature or enhancement, how will it help users or adoption of this project. Ex. All users will be less frustrated when [...]
Provides the option to store data on device to allow user to pick up where left off, saving time.

### Acceptance Criteria
What does it look like if we've implemented this enhancement or new feature correctly? Ex. User A was able to create a new incident 5s faster than previously [...]
Improve end-user experience and save time.

The issue does not name files, tests, or an entry point. Begin by identifying the mobile incident-submission flow and its current handling of unsent data; completion should cover saving incident data without connectivity and allowing users to resume and submit it later.

Written by the indexing model from the issue text.