This is an example of the Android app with the common master/details problem. Written with TDD and handmade DI. Can be used as a template for new projects providing restricting architectural approach, yet easy to adopt big changes. Overall this results in bugless apps cheap in maintenance.
- All elements from the design should be visible on the screen for a user. If the feature is not implemented, show "The feature is in progress. Stay tuned"! toast.
- Show list of locations with a given design
- Implement selection of a location
- If any location selected, show the Accept button. Hide the button if a location deselected (clicked again or is not selected yet). Note: these screens are part of 6-screen flow, and every screen has a similar button.
- On click on Accept button, transition to the next screen. The new screen should display the selected location name and city in a simple TextView
- Get directions button should open Maps app showing the direction
- "Close" button closes the first screen or navigates back on the second
- Nearby button should be displayed, but on click it should just log the click and show a message "The feature is in progress. Stay tuned"!
- The accept button should appear and disappear with sliding animation from the bottom of the screen. The button should appear when smth just got selected and disappear if the selection gone or before moving to the next or previous screen.
- The screens should be changed with sliding animation
- The Accept button on the second screen should be always shown and just do nothing
- Everything else that you consider part of "production-ready" app