It was quite a challenge. Not as much in the technical aspect as trying not to get carried away with too many details. There is so much more that I could have done but I did not have time for. I easily put double the suggested hours into this project! I tried to stay as true to the linked dependencies as much as possible, even though some of them I had no prior experience with. For the dependencies that I have added (some being nicer UI, some being technical), I have included an explanation inside the build.gradle. That being said, I can understand why the team went with Koin over Dagger after learning about it while implementing. It was a great learning experience.

1. Return businesses based on users' input in the search field. Each business should have the name, image, and top review of the business.
2. Endlessly scroll based on API's paging functionality.
3. Unit testing for important functionality.
4. Requesting the user's location and sending that up in the business search request.
5. Save the list of a user's recent searches and display them as autocomplete suggestions.
6. Integration tests that verify the behavior above.
7. Provide caching of the API requests which is invalidated after 15 days.

1. Improved error management.
   • Dialogs for permission rationale over the Snackbar.
   • Handle network/general issues with a better UI design.
   • Haptic feedback.
2. Better thread management to meet the maximum Yelp Fusion API request limit in a more efficient manner.
3. Creating a mock web server for testing mock Retrofit server values. This one I felt was important but would have taken additional time to set up infrastructure for.

1. Creating a bi-function of the business and review APIs (since they are separate network calls) and returning 5 APIs as a single batch. This was more difficult because I have not used coroutines as much prior to this challenge. I've done this with RxJava though, and the API's turned out fairly similar after searching around.
2. Unit testing with coroutines was not my strong point. I've written unit tests for RxJava and LiveData, but with the given dependencies I was having trouble in the allotted time.
3. Fully understanding of the caching implementation for Retrofit (moreso OkHttp).

Hi there! Thank you for taking the time to conduct the Weedmaps Android code challenge. Please use this as a foundation to help you save time setting up your workspace; this project already contains some common dependencies and frameworks used in most Android projects.
If there are other dependencies and/or frameworks that you'd like to introduce/use please feel free to add them!

• Kotlin Ext
• Kotlin Coroutines
• Mockito Kotlin
• Koin
• Retrofit
• Moshi
• Glide

Register and get a token for the Yelp Fusion API https://www.yelp.com/developers/documentation/v3/authentication

1. You will be creating a yelp clone with the designs here. The data will be coming from the Yelp api linked below. You should return businesses based on the user's input in the search field.
2. Each business item in the list should have: name of the business, an image of the business, and the top review of the business(reference here for how to get the business review).

3. The list must endlessly scroll based on the API's paging functionality.
4. Include Unit Tests for parts of your code with important functionality (no need to get 100% code coverage on the whole project).

1. Requesting the user's location and sending that up in the request
2. Save the list of a user's recent searchers and display those to the user as autocomplete suggestions
3. Provide integration tests that verify the behavior established above
4. Provide caching of the api requests which is invalidated after 15 days

• What if a link is broken above? Please reach out and we'll get those fixed.
• What if I have any questions? Pretend your PM is on vacation, please use your best judgement and be able to speak as to why you made certain decisions.
• Can I modify the designs? Yes, within reason. Stay as true to them as you can, and be prepared to explain any changes you make
• Can I use other/additional libraries that aren't listed? Yes, just be ready to talk about them

• Important: The Fusion API has a query-per-second limit of 5. Keep this in mind when configuring your API requests, otherwise you’ll receive a 429 HTTP error code for some of your requests. It would be a good idea to throttle the speed of your subsequent network requests.

• Yelp Fusion API Documentation

Please submit either of the following to the link from the email containing your coding HW: A) your completed .zip file B) the link to a public repo with your completed project