-
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update to version 1.2.0 Readme files with UI screens
- Loading branch information
1 parent
4575c46
commit 8791d5d
Showing
29 changed files
with
347 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
## Objective: | ||
|
||
Your primary mission is to design and implement a user-friendly interface that interacts with the `users` route for user registration. You are expected to craft this interface in your preferred language/framework. | ||
|
||
## Specifications: | ||
|
||
### Figma | ||
|
||
Access the [Figma link](https://www.figma.com/file/Q44nlEVrODE7W6iBFRVPZL/Desafio-para-devs---App-%2F-Dashboard-%7C-UX%2FUI?type=design&node-id=1%3A655&mode=design&t=aSjbTNYsb0UGO0yp-1) to follow the style guide and components in your interfaces. | ||
|
||
![Create Account Form](images/Create account-Mobile.png) | ||
|
||
### 1. User Registration Form: | ||
|
||
- Your interface should provide a registration form containing the following fields: | ||
- User ID (to be filled with an email): userid | ||
- Password: password | ||
- Full Name: fullname | ||
- Birthdate: birthdate | ||
|
||
The form structure should closely align with this JSON model: | ||
|
||
```json | ||
{ | ||
"userid": "user@example.com", | ||
"password": "string", | ||
"fullname": "string", | ||
"birthdate": "2023-09-22" | ||
} | ||
``` | ||
|
||
### 2. API Communication: | ||
|
||
- To gain a better understanding of the request details and expected API responses, you are encouraged to refer to the comprehensive API documentation available at: [http://localhost:8000/docs#/users/create_user_users__post](http://localhost:8000/docs#/users/create_user_users__post). | ||
|
||
[Online API Doc](https://dev-challenge.micheltlutz.me/docs) | ||
|
||
|
||
### Bonus: | ||
|
||
- Unit Testing: As an added advantage, we'd be highly impressed if you can integrate unit tests for the designed interface. It will provide us with a clear understanding of your proficiency in ensuring the robustness and reliability of your implementations. | ||
|
||
## Final Considerations: | ||
|
||
- Your user interface should not only be functional but also intuitive and user-friendly. | ||
- The design should take into account both aesthetics and usability. | ||
- Be sure to write a good README guiding how to run your project, dependencies and what you think is necessary to install and run the project. | ||
|
||
Challenges like this offer a unique opportunity to showcase your skills. We wish you the best and eagerly await your innovative solution! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
# Mobile Developer Technical Challenge 2 | ||
|
||
|
||
## Objective: | ||
|
||
Your primary mission is to design and implement a user-friendly interface form to user login interface that interacts with the `auth` route for user login. You are expected to craft this interface in your preferred language/framework. | ||
|
||
## Specifications: | ||
|
||
### Figma | ||
|
||
Access the [Figma link](https://www.figma.com/file/Q44nlEVrODE7W6iBFRVPZL/Desafio-para-devs---App-%2F-Dashboard-%7C-UX%2FUI?type=design&node-id=1-731&mode=design&t=1oLA9vtlXknWRtig-4) to follow the style guide and components in your interfaces. | ||
|
||
![Login Form](images/Login-Mobile.png) | ||
|
||
### 1. User Login Form: | ||
|
||
- Your interface should provide a login form containing the following fields: | ||
- User ID (to be filled with an email): userid | ||
- Password: password | ||
|
||
The form structure should closely align with this JSON model: | ||
|
||
```json | ||
{ | ||
"userid": "john.doe@email.com", | ||
"password": "string" | ||
} | ||
``` | ||
|
||
### 2. API Communication: | ||
|
||
- To gain a better understanding of the request details and expected API responses, you are encouraged to refer to the comprehensive API documentation available at: [http://localhost/docs#/auth/login_auth__post](http://localhost/docs#/auth/login_auth__post). | ||
- The API will return a JSON object containing the access token and token type. You should store the access token in the browser's local storage for future requests. | ||
- The access token should be sent in the `Authorization` header of all future requests to the API. | ||
- The access token should be prefixed with the token type and a space, like this: `Bearer <access_token>` | ||
|
||
**Response example**: | ||
|
||
```json | ||
{ | ||
"access_token": "access_token", | ||
"token_type": "bearer" | ||
} | ||
``` | ||
|
||
### Bonus: | ||
|
||
- Unit Testing: As an added advantage, we'd be highly impressed if you can integrate unit tests for the designed interface. It will provide us with a clear understanding of your proficiency in ensuring the robustness and reliability of your implementations. | ||
|
||
## Final Considerations: | ||
|
||
- Your user interface should not only be functional but also intuitive and user-friendly. | ||
- The design should take into account both aesthetics and usability. | ||
- Be sure to write a good README guiding how to run your project, dependencies and what you think is necessary to install and run the project. | ||
|
||
Challenges like this offer a unique opportunity to showcase your skills. We wish you the best and eagerly await your innovative solution! |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# Mobile Developer Technical Challenge 3 - Dashboard and Side Menu | ||
|
||
## Objective: | ||
|
||
Creation of a dashboard with a side menu with the following items: | ||
|
||
- Home | ||
- Statements | ||
- Profile | ||
|
||
*Optionals (Api under development for the items below)* | ||
|
||
- Setting | ||
- Notification | ||
- Logout | ||
|
||
## Specifications: | ||
|
||
### Figma | ||
|
||
Access the [Figma link](https://www.figma.com/file/Q44nlEVrODE7W6iBFRVPZL/Desafio-para-devs---App-%2F-Dashboard-%7C-UX%2FUI?type=design&node-id=13-4267&mode=design&t=1oLA9vtlXknWRtig-4) to follow the style guide and components in your interfaces. | ||
|
||
|
||
| Home | Side Menu | | ||
|-----------------------|-------------------------| | ||
| ![Home](images/Home-Mobile.png) | ![Side Menu](images/Menu-Mobile.png) | | ||
|
||
|
||
### 1. Home | ||
|
||
- The home page should contain a welcome message | ||
|
||
### 2. Statements | ||
|
||
Now this page is a blank page in next challenge you will create a list of statements. | ||
|
||
### 3. Profile | ||
|
||
Now this page is a blank page in next challenge you will create a profile page for edit user information. | ||
|
||
### Bonus: | ||
|
||
- Unit Testing: As an added advantage, we'd be highly impressed if you can integrate unit tests for the designed interface. It will provide us with a clear understanding of your proficiency in ensuring the robustness and reliability of your implementations. | ||
|
||
## Final Considerations: | ||
|
||
- Your user interface should not only be functional but also intuitive and user-friendly. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,83 @@ | ||
# Mobile Developer Technical Challenge 4 - Statement List and Amount | ||
|
||
Its main mission is to design and implement a screen that displays the user's balance and their list of bank transactions with pagination, hiding the display of values. | ||
|
||
You are expected to create this interface in your preferred language/framework. | ||
|
||
### Figma | ||
|
||
Access the [Figma link](https://www.figma.com/file/Q44nlEVrODE7W6iBFRVPZL/Desafio-para-devs---App-%2F-Dashboard-%7C-UX%2FUI?type=design&node-id=19-1283&mode=design&t=1oLA9vtlXknWRtig-4) to follow the style guide and components in your interfaces. | ||
|
||
![Statement](images/Statement-Mobile.png) | ||
|
||
### Pagination: | ||
|
||
The route should receive two parameters, `limit` and `offset`, the `limit` parameter will be the number of statements to be returned and the `offset` parameter will be the number of statements to be skipped. | ||
|
||
**GET:** `/statements/{limit}/{offset}` | ||
|
||
### Response: | ||
|
||
- After successfully processing the input data and CHECK the auth information, the endpoint should return a status code of 200 OK. With JSON Statement list: | ||
|
||
```json | ||
[ | ||
{ | ||
"type": "Deposit", | ||
"amount": "15000.00", | ||
"description": "Payment from Freela", | ||
"from_user": "John Doe", | ||
"authentication": "45d064afbd6cf24613daed52133320b84ece0e2cc751995a4d0b94fca84823dd", | ||
"id": 1, | ||
"created_at": "2023-09-21T18:46:45.478966", | ||
"to_user": "John Doe", | ||
"bank_name": "Adams LLC" | ||
}, | ||
{ | ||
"type": "Deposit", | ||
"amount": "88.81", | ||
"description": "Trip authority window myself hour.", | ||
"from_user": "Holly Bailey", | ||
"authentication": "0ef6dc8284c7908ce7af354b10b6f354ff355a201f8f54e22bd60d928a6670c8", | ||
"id": 2, | ||
"created_at": "2020-09-07T00:00:00", | ||
"to_user": "Caitlin Bennett", | ||
"bank_name": "Williams-Norris" | ||
}, .... | ||
] | ||
``` | ||
|
||
## Validations: | ||
|
||
- The Route is authenticated, so it is necessary to send the token, otherwise the user will receive a 401 unauthorized status code, with the following message: | ||
|
||
```json | ||
{ | ||
"detail": "Not authenticated" | ||
} | ||
``` | ||
|
||
### Bonus: | ||
|
||
- Unit Testing: As an added advantage, we'd be highly impressed if you can integrate unit tests for the designed interface. It will provide us with a clear understanding of your proficiency in ensuring the robustness and reliability of your implementations. | ||
|
||
## Final Considerations: | ||
|
||
- Your user interface should not only be functional but also intuitive and user-friendly. | ||
- The design should take into account both aesthetics and usability. | ||
- Be sure to write a good README guiding how to run your project, dependencies and what you think is necessary to install and run the project. | ||
|
||
Challenges like this offer a unique opportunity to showcase your skills. We wish you the best and eagerly await your innovative solution! | ||
|
||
|
||
### Bonus: | ||
|
||
- Unit Testing: As an added advantage, we'd be highly impressed if you can integrate unit tests for the designed interface. It will provide us with a clear understanding of your proficiency in ensuring the robustness and reliability of your implementations. | ||
|
||
## Final Considerations: | ||
|
||
- Your user interface should not only be functional but also intuitive and user-friendly. | ||
- The design should take into account both aesthetics and usability. | ||
- Be sure to write a good README guiding how to run your project, dependencies and what you think is necessary to install and run the project. | ||
|
||
Challenges like this offer a unique opportunity to showcase your skills. We wish you the best and eagerly await your innovative solution! |
Oops, something went wrong.