diff --git a/package.json b/package.json index 3d559f2..ce8d240 100644 --- a/package.json +++ b/package.json @@ -22,7 +22,8 @@ "react-native-web-linear-gradient": "^1.1.1", "react-router-dom": "^5.2.0", "react-scripts": "3.4.1", - "react-view": "^2.3.2" + "react-view": "^2.3.2", + "v8": "^0.1.0" }, "scripts": { "start": "react-app-rewired start", diff --git a/public/index.html b/public/index.html index ecab673..297aef2 100644 --- a/public/index.html +++ b/public/index.html @@ -57,7 +57,7 @@ - + - + - + React Native Elements -
+ +
- Exploring possibilities + Exploring + Possibilities with React Native Elements @@ -32,17 +34,12 @@ function HomePage() {
-
- + {FEATURES_LIST.map((feature, idx) => { return ( @@ -60,21 +57,38 @@ function HomePage() { style={{ justifyContent: "space-evenly" }} > - Why? - + + Why? + + React Native Elements houses a lot of components, and these components come with a lot of customisation and tweaks via props. Sometimes the user gets confused and wastes a lot of time in achieving the desired result.
We came across a lot of such questions every day and sometimes user - reports bugs which aren't bugs but just improper + reports bugs which aren't bugs but just improper implementation/usage of the components. +
- How it solves the problem? - + How it solves the problem? + With Playground, users can explore components and tweak them as per their use-case and generate production-ready code. Or they can explore new possibilities with the components and improve the