The documentation of all components lists the props as well as their usage. It would be great if we arrange the props list alphabetically to make it easier to find the required props.

Just like the expo docs and others.

Proposed Fix
The docs are written using markdown and can be found [here](https://github.com/react-

Add 8.7 and 8.8 for android and ios: show how you can delay the attacker or report tampering to the backend as a response to a tamper detected
8.7: The app implements multiple mechanisms in each defense category (8.1 to 8.6). Note that resiliency scales with the amount, diversity of the originality of the mechanisms used.
8.8: The detection mechanisms trigger responses of different types, includ

Steps to reproduce

1. Launch the app.
2. Go to app settings.
3. Select data locations from general settings.

Expected behaviour

• Visible Cancel button.

Actual behaviour

• Invisible Cancel button.

![obraz](https://user-images.githubusercontent.com/47037

Arrange the app's common assets neatly in the js/assets folder with sub-folders named by type:

• fonts
• audio (e.g notification sounds)
• images (e.g default avatar)
• etc...

And properly wire the different layers of the app (js/RN, iOS and Android) so that they can access them. For example: add a "Build Phase" in XCode that copies the sound files of the notifications to the IPA.

Note: An

The CI checks the commit conventions. To prevent to note the problem just in CI, we should add a check in the pre-commit hook. This would require an extra tool installation on the client though.