chore: update splash screen

[geastwood]

PR for #313

Probably making it the background black is better.

[parity-cla-bot]

It looks like @geastwood hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement at the following URL: https://cla.parity.io

Once you've signed, please reply to this thread with [clabot:check] to prove it.

Many thanks,

Parity Technologies CLA Bot

[geastwood]

[clabot:check]

[parity-cla-bot]

It looks like @geastwood signed our Contributor License Agreement. 👍

Many thanks,

Parity Technologies CLA Bot

[Tbaut]

Thank you very much for that !

Probably making it the background black is better.

absolutely, it'd be great with a background using #1d1d1d, that's the color of the logo.

[geastwood]

Updated the color.

[Tbaut]

Thanks a lot, I'll let @hanwencheng test on an iphone (I don't have a mac :)) before merging

[hanwencheng]

Thanks @geastwood for the PR! Tested on iOS devices. It all looks good, I just remove a duplicated image file in 54cf3a9.

And I am thinking to remove the white react native bridging splash screen on both iOS and Android, it seems we have to use the react-native-splash-screen dependency. I would suggest us to create another issue about that.

[geastwood]

Thanks for merging!

What value does it bring to introduce react-native-splash-screen?

[hanwencheng]

It hides the white react native bridging splash screen on both iOS and Android.

[geastwood]

The screenshot is only for development. And RN uses for iOS the LaunchScreen which is the essential way for implementing splash screen. Afaik, the lib makes sense when you want to show a splash screen programmatically, e.g. show an advertisement while the user is back to the app, namely hooking into the lifecycle of user interaction.

[hanwencheng]

Thanks for the explanation, we will ignore that screen then.