# Test Requirements for Deem APIs

## Products
| Name | Description | Possible Features
| --- | --- | ---
| Products API | Provides APIs for Managing Products |
| Customer API | Provides APIs for Managing Customer

Product Features
- Will Provide APIs

Notes:
- Names Could Be Changes

## UX Guidelines
- Straight to Point Design

## Pages
### First Page
##### Functions
- Show the products we have
- Provide a Call to Action to start using the product. E.g get Started

#### Inspiration
- [DropBox](https://Dropbox.com)
- [Zapier](https://zapier.com)

### Second Page
#### Functions
- To get them registered
- Featured Google Sigin and Github Sigin

### Third Page
#### Functions
- This Page involves a Step by Step Onboarding Process
- **Step 1:**
This would show a set of fields that would that are already there, you can add your own fields , delete or edit editable pre-coded fields.
- PreCoded Fields: Name: Text, Price: Number and Count: Number (uneditable)
- Names has to be a text
- Type can be text, number or boolean (true or false);
- Every Field has a type and name,
- This step can not be skipped
- **Step 2:**
- They are now expected to create their first product. or skip.
- I suggest the Skip should be inspiring , like " Skip to start using APIs"

#### Fourth page
#### Functions
- This page will have a table, this table will have header names that are representative of the fields they added in the first step of last page.
- This same table will have a place where they can add new record to the table
- And a place to edit and delete each record in the table.
- THey should also be able to view a record full details
- this same page will have another section that shows the list of the API endpoints and their details.

Note: Please consider all edge cases we have not mentioned

#### Inspiration
- Any Website having a step by step onboarding process should be enough guide

#### Idea
- The first screen can be a screen and not divided screens, but when the mouse hovers on it, it will bring out the two APIs