---
# System prepended metadata

title: Smartphone Application

---

# Smartphone Application

1. [Roadmap](#roadmap)
2. [Current status](#current-status)
3. [Implementation plans](#implementation-plans)
4. [Currently implemented](#currently-implemented)
5. [Discussion](#discussion)


## Roadmap
1. UI & UX design
2. architecture design
3. implement static pages for sources, compounds and molecules
4. implement routing
5. connect to API
6. implement filter & search functionality
7. implement login functionality


## Current status

Currently first 4 steps from roadmap are done. That means that the main app architecture and design language are established as well as the pages for displaying sources, compounds and molecules. Also the routing, so user is able to navigate through application.

Currently we are using static data, as soon as the API is prepared, we are able to adjust the app for consuming dynamic data and implement other functionality.


## Implementation plans
* immediately - create README, verify API design, API integration
* short term - filter functionality, search functionality
* medium term - login screen, login functionality


## Currently implemented
### Main page

Main page displays a list of sources, which redirects to Compounds page by clicking an item:

![](https://i.imgur.com/gsBnQD8.png)

### Compounds page

Compounds page consists of the name of the source and list of compounds that redirect to Molecules page:

![](https://i.imgur.com/hBSnJix.png)

### Molecules page

Molecules page contains list of parent sources and the list of molecules, by clicking parent source item, the page is redirected to the Main page, Molecule items redirect to Molecule Details page:

![](https://i.imgur.com/2tada1I.png)

### Molecule Detail page

Molecule detail page contains the details of selected molecule, such as lambda max. Also contains the list of parent compounds: 

![](https://i.imgur.com/eUl93io.png)

### Navigation between pages

For navigation between pages, routing is implemented using a third party service called Fluro.


## Discussion

* Is it possible to implement caching later?