Updated React Native example

[iujames]

There aren't really that many updates here, but I think the package-lock.json makes it look that way.

key updates:

• fully implemented RN SDK wrappers for remaining functions: reset(), anonymous() and group(id, props)
• build out an example app that mirrors the native samples - sign in page, then pages for events, profile, group - to exercise SDK functionality
• updated bundled Android lib to include new startup logic André recently added

The example app contents is probably the most interesting thing here. The structure of that example is now:

example/
|-- ios/ --> generated xcodeproj stuff
|-- android/ --> generated android studio project stuff
|-- components/
|--|-- { three custom button styles - filled, plain, tinted }
|-- contexts/
|-- |--UserContext.js --> for passing User ID state through app
|-- screens/
|-- | main/
|-- |-- MainScreen.js --> root tabs
|-- |-- EventsScreen.js
|-- |-- ProfileScreen.js
|-- |-- GroupScreen.js
|-- | signin/
|-- |-- SignInScreen.js --> initial page for user ID input
|-- style/
|-- |-- AppcuesStyle.js --> theme, text, input shared styles
|-- App.js --> main entry point

[andretortolano]

Looks good, I dont have much to say about the react implementation.

[mmaatttt]

FYI iOS navigation titles are semi bold if you want to match it exactly.

[iujames]

ah ok, looks like that is 600 in RN terms, no semibold out of box https://gist.github.com/knowbody/c5cdf26073b874eae86ba96e7cf3a540

[mmaatttt]

Tangential, but I wonder if it's better if we use those values in the experience model for fontWeight instead of the named ones. The names ones might be pretty iOS-specific?

@andretortolano any preference?

[evandavis]

I could add more comments about various lines and things, but I don't think it's all that important for this example to look like our in-house style 🤷

[evandavis]

This should probably be inside a useEffect so that it only runs once; this component can re-render if setUserID is called.

useEffect(() => {
  Appcues.setup('ACCOUNT_ID', 'APP_ID');
}, []);

[iujames]

ah got it, will do thanks

[iujames]

turns out this does cause some additional complication, as the useEffect hook only runs after the first render, and there is some code during that render that attempts to access/use the SDK for a screen view during a useFocusEffect hook. Not sure what best practice there would be yet.