Closed slifty closed 4 years ago
Before merging this I'm going to spend an hour or so looking into testing best practices here (which will pay dividends for future PRs).
A test is now added (also this is a useful resource: https://github.com/codepath/android_guides/wiki/Creating-and-Using-Fragments)
We aren't running travis yet so there's no proof that the tests pass, but they do locally I swear!
Going to merge.
Description
This PR adds a very simple introduction page, which is what users will see when opening the application. It features the title, a "tutorial" image (TBD), and a button to move to the next page.
Since the template we used has a starting page with a button, this re-uses (re-names) the "first fragment" that was generated by the template.
You'll notice that we're using the strings.xml for all text-based aspects of the code. This is going to be a best practice that will allow us to support multiple languages more easily some day.
For now we aren't worrying about look and feel / styles at all. This is purely about creating the UI elements.
Due Diligence Checklist
Steps to Test
./gradlew test
Deploy Notes
None
Related Issues
Resolves #15