appjusto / app Goto Github PK

• Splash Screen expo/expo#10294
• Sentry expo/expo#10300

• Test to see if it it ok and connected to the flow
  ->needs a simulated order

Something needs to be cleaned up in the flows of those screens:

• Profile (courier & consumer):

• action: user signs out;

• object: user.uid;

• OngoingDelivery (courier):

• action: user navigates to screen;

• object: order.dispatchingState;

• review all the situation feedback screens and make sure that all their states - and their respective icons - are correct.

• Confirm pickup arrival
• Confirm pickup departure
• Confirm destination arrival
• Confirm delivery is done
• Send message to customer
• Open routes in Google Maps or Waze (add icons also)
• Review summary after delivery
• Give feedback
• Change buttons to Slider component

• Right now we are getting a "response is not a valid JSON object" error

• AcceptControl component;

• Change buttons to Slider component (consumer side - ongoing order);

• add back the "Fleet" item. For now, the "advance" button will not need fleet information;

• fix the "steps counter" for the image files;
  -> it only works when you reload the PendingChecklist screen. It should also work when you navigate back the first time when the user submits his images.

• review the "checked" icon display. It should appear to the left of the title and above the subtitle (check figma)

• store the docs verification so it won't happen again when you return to the pending checklist screen;
  maybe an useMemo to store all the values we need in this screen

• require fleet info to advance and add the checked icon when done

Photos

• make the "squares" clickable just as the configitems;

• take a look at the layout/distance between elements in the screen

• show activity indicator in the button

• Create LICENSE file (https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/adding-a-license-to-a-repository)
• Change license property at package.json (reference)

https://choosealicense.com/licenses/apache-2.0/

div-intro-screen

• adapt to different screen sizes (the logo is cut in smaller phones, for example);

div-terms

• set the final terms (for now, gonna use a long text as placeholder);

• add an ScrollView as the parent view.

div-checklist-confirm

• review layout

div-checklist-photos

• Check why we are seeing the icon and title increasing - therefore extrapolating the container - before the photo renders

div-new-order

• review layout according to the Figma project

• Report problem
• Tip courier

• Show list of fleets available
• Add confirmed fleet information to courier

• Show courier's profile picture(check if still needed)

• OngoingDeliveryDetail: add show courier details component (create/populate/connect the screen)

• Add highlight when courier is waiting

• add button to cancel "order";

• create the slider component;

• add logic and icons to open waze and google maps;

• review the layout.

on screen's second state

• feedback field;

• Create feedback component reflecting the delivery status (the yellow box in figma). The dispatchingState is the status

Allow user to choose another fleet

If the user doesn't press "enter" in the device's keyboard he has to tap the "Avançar" button two times to advance. check the logic to minimize the keyboard when the user touches another part of the screen

• Hide the bottom tab navigator: it should only appear in the initial screens in the "Início", "Seus pedidos", "Sua conta" flows.

• OrderStep component: check the spacing between elements.

• Consumer should not see the fleet's GainSimulation when reviewing the fleet details

OrderSummary.tsx:

• PlaceSummary: show only place.adress.main. Also check the spacing between the elements in this container for smaller devices

• "circle icon" (km • min): should be smaller. Replace with a "-" if not possible (the icon is also present in the History session).

• Require only necessary permissions at app.json

"permissions": [
  "ACCESS_COARSE_LOCATION",
  "ACCESS_FINE_LOCATION",
  "CAMERA",
  "READ_EXTERNAL_STORAGE",
  "WRITE_EXTERNAL_STORAGE",
  "NOTIFICATIONS"
],

• Configure /.well-known/apple-app-site-association to handle iOS deeplinks individually
• Complete #7
• Update validateProfile to reject courier's profile when necessary
• Create new firebase project for production environment
• Remove test flag from common/store/api/payment/iugu.createPaymentToken
• Set firestore initial dataset
• Increase fetchFleets query limit
• Conform to privacy requirements

Permissions documentation:

https://docs.expo.io/versions/latest/sdk/permissions/
https://docs.expo.io/versions/latest/config/app/#permissions
https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW1

• check if the "ongoing order" card works and looks good (simulate an order);
• add "new message" card;
• add "total couriers online" card;
• ask for location permission;

Should the route opened in these apps show the way to the destination, with the pick-up location as an intermediate point?
As of now, each dispatchingState "generates" its own single route.

Development settings:

{
  accuracy: Location.Accuracy.Highest,
  distanceInterval: 1, // 1 meter minimum change betweens updates
  deferredUpdatesInterval: 1000, // 1 second minimum interval between updates
  foregroundService: {
    notificationTitle: t('Localização ativa'),
    notificationBody: t('Para desativar, entre no app e pare de trabalhar.'),
    notificationColor: '#78E08F',
  },
}

• test to see if the screen is ok and make sure it's used when the courier denies access to his localization

• dlv-new-order-recuse-explanation;

• div-order-confirmation
  the screen is done, but it's not connected to the real flow yet

we get a "missing or insufficient permissions" error

• create the screen and connect it to its respective flow

• Text is not being cleared when submitted by the keyboard
• When push notification is received chat screen is reopened even when it's already open

Options: 'Corrente' e 'Poupança'
It's currently hardcoded as 'Corrente' but it also can be 'Poupança';

• Delivery history by periods
• Delivery summary
• Layout for empty summary

• Send push notification to available couriers close (currently 10km) to pickup location;
• When notification is select, present Matching screen to courier;
• Let courier send a match request;
• Present OngoingOrder screen after successful accepting
• Slider thumb is not showing on builded apps
• Show feedback while waiting for confirmation
• Show feedback in case of failing to accept
• Adjust icons and space according with Figma

Save notification on global state

ProfileEdit form

• Check if the keyboard types for each input are correct;
• add validation to the inputs

Bank data

• Fix styles in the bank selection screen;
• Check if the keyboard types for each input are correct;
• Submit bank data to backend;
• only submit the form if the bank data is fully set;

Courier's images uploading to backend

• Integrate with Firebase Storage
• Show previously uploaded images
• Optimistically returning to previous screen after upload starts
• Resize selfie image to be used in app
• Present UI to allow user to choose picking up image from camera or from library;
• Adapt layout according with device's height;
• Define image's size and compression;
• only submit form if the required images are fully set and uploaded
• Placeholder icons are not respecting size constraints (iPhone 11 simulator)
• Clicking on placeholders should do the same action as clicking on the buttons below;

Checklist

• Requiring completing all items before submitting profile