> For the complete documentation index, see [llms.txt](https://zinisoft-net.gitbook.io/kindie/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zinisoft-net.gitbook.io/kindie/mobile-app/untitled.md).

# Mobile app structure

App source code structure

## App source code structure

Kindie Mobile Application is built by React Native, is an exciting framework that enables web developers to create robust mobile applications using their existing JavaScript knowledge. It offers faster mobile development, and more efficient code sharing across iOS, Android, and the Web, without sacrificing the end user's experience or application quality.

![](https://zinisoft.net/wp-content/uploads/2019/11/react-native-structure-1.png)

Now let's understand what is the purpose of each directory:\
**index.android.js and index.ios.js** are entry points for Android and iOS, respectively\
**assets** Just as the name implies, this houses static files (e.g images) used in the application.\
**src** all customize source code for the project.

* **src/components**: All presentational components will go here. They can be put as separate files or organized into folders.
* **src/config**: All configuration will be put here, such as routes, image URL list, and more.
* **src/redux**: Specify how the application’s state changes in response to actions sent to the redux store (Reducers).
* **src/navigation**: Link to navigate between the screens.
* **src/screens**: Here we will put our screen layouts.
* **src/helpers**: All utility functions will be here.
* **src/services**src/services: define REST service to call API funtion from backend


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zinisoft-net.gitbook.io/kindie/mobile-app/untitled.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.