kursivee
commented
4 years ago - Obfuscation will mess up the code.
- I need to follow practices defined https://developer.android.com/guide/navigation/navigation-pass-data#proguard_considerations
- Or annotate with field:Json
- I’m missing unit tests for the results section due to time
- I'm missing espresso tests due to time
- The espresso tests definitely need some refactoring. I wasn't to familiar with it.
- Had to use thread.sleep in the espresso test cause of the debouncer I’m using. I couldn’t figure out how to get the idling resource working
- Missing splash page
- Bug when clicking the clear button in search. Hides keyboard then immediately shows
- Disable Logging in production
- Expire cache results.
- Could make it so that pull-to-refresh always fetches data
- Caching is too simple. Since it's based on search term, you could have results with different values. e.g searching "a b" vs. "ab" could have same results but the thumbs up/down count would be different
- voting capability
- sharing capability
- Add refresh as a menu item. (https://developer.android.com/training/swipe/add-swipe-interface#AddRefreshAction)
- add an icon or menu item that allows you to get random results
dm17