desafio mobile cross developer

Mobile Cross Platform Development Challenge

Overall summary

The idea of ​​this challenge is to understand the candidate's ability to solve problems simply by creating a CRUD.
We have no interest in selling or taking advantage of the code written for this challenge.

Our culture is focused on solving problems quickly and with the best possible approach. We seek people who have confidence in themselves and are willing to make a mistake and learn from mistakes.

Read carefully all the content below feel free to contact us if you have any questions. æ

User story

Github is a social network of programmers that has an interesting feature that allows you to enjoy the repository of others. This is a written Star button found on the page of each repository. Rick is an active user of Github, who is always looking for new projects and enjoying those who are interesting. He would like to be able to add a label or tag to mark the repository so that he can filter. For example, he found a repository called react and would like to add the javascript and frontend tags. Because Github doesn't have this functionality, Rick needs a system that can help him with this task in a simple way.

About the challenge

The challenge consists of developing a web application that gets all repositories that a particular user "enjoyed". Once repositories are obtained, the application should allow tag management (add, edit and remove). It should be possible to filter the user's repositories by tags. The system should have a tag suggestion mechanism. Tag suggestion criteria are free choice of challenger (repository language, tags assigned to other repositories, the information provided by Github, etc.).

Requirements:

• Recover Github Starred repositories of a particular user.
• Manage tags of recovered repositories (add, edit, delete).
• Filter repositories by tags.
• Suggestion of tags for repositories.

There are 4 user stories to understand what is needed to do:

1. Obtain remote repositories

As a user, I want to provide my username recover all the repositories I enjoyed and then I can add my tags.

• You must get the repositories with Star using the Github Rest V3 API.
• The information that must be recovered is: repository id, repository name, description, http and language.

2. Add tags to repositories

As a user, I want to be able to add tags (labels) to each repository so I can search for tag.

• A repository cannot have duplicate tags.

3. Seek repositories by tag

As a user, I want to be able to provide a tag and get the repositories that have this tag.

• The search should work for strings in half. (Ex: When filtering for the doc String both repositories with the docker tag and the documentation tag should be returned)

4. Tag recommendation

As a user, I want to receive tag recommendations for my repository.

• Each repository should receive at least one tag recommendation.

Application

• You should use react native or nativescript.
• Using redux is no more mandatory can be used if desired.
• Repositories and their tags should be persisted in a local bank.
• The interface should be as faithful as possible in the layout available.
• The code organization should be maintained by following the good development practices.

Support material

• Below is the Figma layout that should be followed for the development of the application, this layout is a starting point to help with the development, texts and flows can be changed by the candidate to show their creativity that will also be evaluated in this test. It is very important that the development tries to follow as faithful as possible the components and colors created by our designer team as this will be evaluated as well.
• Link Layout Figma

What will be evaluated?

We want to evaluate your ability to deliver a complete product with sufficient minimum documentation for other developers to contribute to the project. It is essential that the README.md contains the intractions to configure and run the project, just one Ctrl+C/Ctrl+V on the Linux and OSX terminal to run the application.

Other points that we will consider in the evaluation:

• Well written, clean and cohesive code.
• Automated tests (test coverage).
• LINTER/STATIC ANALYSIS OF THE CODE.
• Readme.md well written, short and with the commands needed to run the application by just copying/paste to the terminal.

Delivery

• The deadline for sending the test is 4 days counting from the moment our HR passes the test to the candidate.

Delivery Instructions

1. Create a README.md file describing how to configure the project, containing the commands that must be executed to run the software and tests;
2. Climb the project in your Github;
3. Provide the link and send us the URL to [email protected].

Note: If you have used any linter, send the configuration file along with the project and describe which linter is being used in the project README .

Any questions can contact us. Good luck!