Hypothesis
The problem we are trying to solve is how we can best to get the information about the cards that the user searches for in a fast reliable way
For our customers, if we have an app that is difficult to register an account for it could deter customers form wanting to use our product before they get started
To elaborate, customers may get frustrated when there are too many pages and forums to create an account
For our main focus we are attempting to figure out how many screens are needed to best reach our customers to increase our adoption rate
For our hypothesis we can make a snack bar/pop up page to have the users chose their preferences versus having it on a seperate page
Experiment:
We will have half of our users have access to the api being called by the user, and the other half will have the json for all off the cards as returned by the cloud function saved on device. And we will have the back end of the app send back how long it took for the card results to show up
Variations:
One variation will be our app will directly call the api and the other will consult the json that it has saved locally
User Story Number: Is a task under US5 (API)
Metrics: card fetch time
Hypothesis The problem we are trying to solve is how we can best to get the information about the cards that the user searches for in a fast reliable way For our customers, if we have an app that is difficult to register an account for it could deter customers form wanting to use our product before they get started To elaborate, customers may get frustrated when there are too many pages and forums to create an account For our main focus we are attempting to figure out how many screens are needed to best reach our customers to increase our adoption rate For our hypothesis we can make a snack bar/pop up page to have the users chose their preferences versus having it on a seperate page Experiment: We will have half of our users have access to the api being called by the user, and the other half will have the json for all off the cards as returned by the cloud function saved on device. And we will have the back end of the app send back how long it took for the card results to show up
Variations: One variation will be our app will directly call the api and the other will consult the json that it has saved locally