<aside> ❓ See the Architecture Guide for more information

</aside>

Techical

<aside> 🚧 After doing technical research, return here to fill out the technical frameworks, platforms and other architectural decisions you resolve.

</aside>

API Integrations

<aside> 🚧 See the guide for more info on what to document here.

</aside>

API Integrations

(Create a section that answers these types of questions for each new API integration)

For the back-end, we plan to use the Data Sciences image hand recognition api. The API at this time will return a percentage that indicates top accuracy of the sign to a letter. ie: 98% that this is an A sign. It will also return percent that it may be for any other letter of the alphabet. Some potential challenges with using this API are signs that require movements.

  1. What Feature(s) is/are this API connected to?

    Image hand recognition

  2. What will this API integration accomplish in the feature(s) to which it’s connected?

    It will return a percentage that indicates accuracy of the letter signed by the user.

  3. What alternatives did you consider?

    None

  4. Why did you decide on this solution? (what are the advantages?)

    Our decision was based off of what the DS team chose and worked on for the past 4 weeks.

  5. What are the potential challenges can you foresee?

    The API not recognizing images and files.

Front-end

<aside> 🚧 See the guide for more info on this section.

</aside>

Front-End

(if your product has more than 1 platform, have a section like this for each platform)

As a team we considered using React, React Native, and Vue. We decided to go with React and utilize a Mobile first thinking because it is lightweight and has a very small API surface. React also allows for us to output proper HTML instead of a bunch of div's. Because this is the first build we will do, familiarity did play a role as well as we have other new elements we wanted to learn. Also thinking about future iterations we feel using React now will allow for a more seamless transition to React Native in the future. For State management we will most likely be using Redux or Context API depending on if we feel the state can be managed from the top down or if there are components that will require state and not be in the App component tree.