Provide less contrived sample screens

[jamonholmgren]

Currently, the first screen is FirstExampleScreen and the second is SecondExampleScreen.

It would be friendlier to name them WelcomeScreen and DemoScreen or something.

Also, it would be really nice to include a FlatList screen, as well as showing how to retrieve something from the API. (We have some code already wired up for this, but actually show it wired up to a screen.)

[cargallo]

With all due respect, I join your proposal @jamonholmgren. Personally I'm trying to understand the Mobx, MTS and react-navigation implemented on Bowser but without success. I'm reading a lot because I want to use ignite, but it seems too much effort. I think the idea behind a boilerplate is to facilitate the learning and involving of new developers to RN world (If I already knew all the concepts involved and how to code them probably I'd not need bowser). I asked for documentation at slack but one good example could replaces unnecesary documentation too. Thanks, hope you do not matter my intromission.

[surfersat]

Hello and thanks for all the work. I would glad to see more documentation and examples to test and publish my developments because i think that is the best way to get something working.

Greetings.

[jamonholmgren]

I'm planning to do this @cargallo and @surfersat !

[jamonholmgren]

WelcomeScreen and DemoScreen are done, but I'd like to add a login screen example and a flatlist screen example.

[nonameolsson]

@jamonholmgren

1. If a login screen would be added, would it do an API request or just mock it?
2. Should the current user/auth state be stored within MST?
3. And regarding form validation, what library would you use? React Hook Form, Formik or something else?

I might be able to help out with this.