Spike: Rx Refill Tracking + Map

[b-rocha]

Description

Initial wireframes for Rx refill incorporate a tracking page that details tracking statuses, as well as a map view that illustrates where the package is located. Before finalizing designs, we want to investigate:

• Whether we can pull the package statuses from the appropriate shipping service API (primarily USPS)
• What libraries we could use to implement a map view
• If a map view is accessible
• What options do we have for maps in React Native? What are the costs associated with it?

Acceptance Criteria

• [ ] Review the USPS API documentation
  • The VA has been known to use UPS and Fedex as shipping service providers, when there is too much volume for the USPS to process. Review their documentation as well
• [ ] List the sample statuses we get back from the APIs (e.g. "Out for delivery", "Shipping label created")
• [ ] Determine whether we can integrate with the USPS API, as well as Fedex and UPS
• [ ] Discuss potential approach with the Backend team
• [ ] Review documentation for react native map implementation
• [ ] Find libraries we could use to implement a map view (assuming we get coordinates from the shipping service API)
  • Verify that we can use these libraries without additional fees
• [ ] Investigate and list any map view a11y considerations
  • Note: Since the map view would be a supplemental view, we are considering incorporating an a11y hint that would provide a brief description of what is shown, e.g. "Map view shows location in ___" Question on this: Would we get a city/ location name with coordinates?

Any documentation should be written in a comment or word document, and included as part of this ticket.

Article: How I built awesome package tracking app with React Native and Node.js in record time

Design for reference

[aherzberg]

The RX service used for other Mobile RX endpoints also has a tracking endpoint. It does not include the shipment current status ("In transit", "delivered", etc), periodic updates (EX: "departed post office"), expected delivery date or a map. Given the number of missing fields, use of the USPS api will be necessary. Calling the USPS api can happen either on BE or FE. If done on FE, FE will need to call a separate mobile endpoint for just the tracking # then call the USPS api with that tracking #.

[rarroyo23]

For the map view there are two libraries we can use https://github.com/react-native-maps/react-native-maps and https://github.com/rnmapbox/maps. Both maps use coordinates which we will have to use a geocode library to find the lat and long for an address. For react native maps we will need to use google geocode api which the cost are seen here https://developers.google.com/maps/documentation/geocoding/usage-and-billing. For mapbox we can use the mapbox geocode which the prices for the map and geocode api are seen here https://www.mapbox.com/pricing/#search.

For the package tracking we will need to have an account for the USPS Web Tools API Portal . https://www.usps.com/business/web-tools-apis/. If we want to track for all carriers we can use shipEngine prices are here https://www.shipengine.com/pricing/ and tracking api is here https://www.shipengine.com/docs/tracking/

For accessibility investigation is kind of blocked until we figure out what are we going to use and what not.