Roos-fs-ZIP

General
Landing page is the page that would the mobile user see first when entering the app after login. THere are 2 types of requirements that need sto be taken into consideration.
Functional and non functional (store requirements).

Expected result
Functional

• after the user logs-in he/she sees the landing page that have the same design patterns as the login page
• user can select if he is searching by vechicle or location
• If by location then the user can enter the location name or adress and sees the list of the locations sattisfyling his/her query
• If by vechicles then the user can enter the LP or VIN and sees the list of the vechicles sattisfyling his/her query
• user can see when the last time the information was synched with the server (timestamp)

Non functional Android Compliance – In-App Requirements for Google Play Publication

• Privacy Policy Display
  -- Add a visible and accessible link to the app’s Privacy Policy.
  -- Suggested locations: login screen, settings, or about section.
• Terms of Use Display
  -- Provide a link to the Terms of Use (Terms & Conditions) within the app.
  -- This should be accessible from the same sections as the Privacy Policy.
• Create a section (e.g., “About” or “Support”) that includes:
  -- App version
  -- Contact email for support
  -- Links to Privacy Policy and Terms of Use
• All sensitive permissions (e.g., location, camera) must:
  -- Be requested at runtime (not on install)
  -- Provide context before asking for permission
  -- Allow users to deny or revoke them