Skip to content

Latest commit

 

History

History
62 lines (44 loc) · 4.09 KB

REQUIREMENTS.md

File metadata and controls

62 lines (44 loc) · 4.09 KB
Raw

[2024] Senior Mobile Exercise (React Native)

Purpose

To evaluate the technical prowess and capabilities of a senior mobile engineer before a long term hire, we want to give a simple exercise which testing engineering and also user interface skills.

Problem Statement

When it comes to building a mobile app, there’s a handful of basic building blocks every application needs. We need to be able to authenticate, fetch some data from somewhere, potentially store it/manage the state then then visualize this for the user.

For this exercise, you have full reigns to pick an entity from any open public API or the ones found here to meet the requirements outlined below. The goal will be to make a visually appealing and well-written mobile app which is user friendly.

Requirements

For the sake of the example and requirements below, let’s assume I show to make an anime demo app.

  1. The app should be able to list all of entities for the user to pick from
    1. For example, a list of all animes
  2. The app should be able to tap on an entity from the list view and dive into the details
    1. For example, if I clicked on One Piece, I would now see a page with more information about the anime
  3. The app should be able to favorite a given entity
    1. For example, I could favorite One Piece and it would show up as favorited. I can unfavorite it and it would also show up as unfavorited (for the sake of simplicity, this can be done locally and does not need API integration)
  4. The app should be able to search for a given entity from within the list
  5. The app should gracefully handle errors/issues as it would on production
  6. The app would have a very simple onboarding screen before the user interacts with it for the first time telling them what the app is about and the features it contains

Technical Requirements

  1. You should use React-Native for this exercise.
  2. You should submit the code for the project as repository on a platform like GitHub.
  3. You should write a detailed README.md to outline the code structure, design patterns and any libraries you chose to add

Evaluation Criteria

  1. Correctness: Does the app retrieve the entity information as required and display it in a user-friendly manner?
  2. Code quality: Is the code readable, maintainable, and well-structured?
    1. How did you architect the frontend? How did you break down components? Were things made in a reusable and modular way?
    2. Did we use any design patterns for this? If so, what did we use?
  3. User experience: Is the app visually appealing and easy to use? Do you bring good intuition as an engineer on solid UI/UX practices?
  4. Error handling: Does the app handle errors gracefully and display meaningful error messages to the user?
  5. Is the application build in a way which is production ready?
  6. Documentation: You're able to use any libraries or frameworks you wish, but be prepared to explain what you used and why you made this decision in your README.md

Time Limit

  • Although this exercise should not take more than 4-6 hours for the right fit, we don't want any candidate to spend more than 8 hours on this exercise. You might not finish everything but it's important to understand how you work under time constraints and the decisions you make in a constrained way.
  • The maximum submission deadline is 3 days from the date we send this assignment to you.

Submission

✏️ Once the exercise has been received, we will review it and give a response within 48 hours on next steps.