React Native application (iOS + Android) for our API, all strictly according to the finished design layout in Figma.

Goal

Create a React Native application (iOS + Android) that implements strictly all scenarios that are actually present in the API documentation (and only those). We are not developing the backend as it is already implemented on our API.

Sources

• Base URL: https://carcheck24api-production.up.railway.app/api
• Docs: https://carcheck24api-production.up.railway.app/docs or https://carcheck24api-production.up.railway.app/redoc
• Figma: CarCheck24 – Figma
  
  

Design/UX Note

• In Figma, it is described how the screens should look.
• If there are questions about user interaction with the interface, navigation logic, button/form behavior, or anything is unclear — I am available and ready to provide prompt assistance.
  
  

Constraints

• Any screen/button/field is created only if there is a corresponding endpoint in the API (docs/redoc).
• /api/users/set-photo is not implemented (not called, no UI for it).
  
  

Functionality (scope)

The application must cover all groups of endpoints from the API docs:

• Auth/Session: login/registration/refresh/logout/password recovery - only those that are in the docs.
• User/Profile: getting/updating profile — only those that exist (except set-photo).
• All other API entities (whatever is in the documentation):
  • List (if there is a list endpoint)
  • Create (if available)
  • Read details (if available)
  • Update (if available)
  • Delete/Cancel (if available)
  • Search/Filter/Pagination (if parameters/endpoints are available)

UI is created according to Figma, but if there is something unnecessary in Figma that is not in the API - we do not implement it.

Non-functional (minimum)

• iOS + Android.
• Unified API client: baseURL, token, handling 401, basic errors/timeout.
• Token storage: Keychain/Keystore.
• Screen states: loading / empty / error.
  
  

Acceptance

• For each endpoint from the API docs (except users/set-photo), the application has a way:
  • to call it from the UI (screen/action),
  • to see the result/error,
  • to go through the full scenario (create → view → update, if supported).
• The application does not have functions that are not confirmed by endpoints in the docs
  
  Current Road map: