Welcome to the worlds first drag and drop blockchain editor!

This README is designed to help you get your DeSo Enterprise app running locally.

Note that all of the commands in this document should be run using your computer's command line.

The web builder website is still being developed.

Requirements

• Node.js LTS release. As of 07/21 this is 14.17+
• Expo CLI
• Git
• Watchman for macOS users
• Yarn use this over npm install when installing dependencies

Only Node.js LTS releases (even-numbered) are recommended. As Node.js officially states, "Production applications should only use Active LTS or Maintenance LTS releases."

Recommended Tools

• VSCode Editor
  • VSCode Expo Extension for app.json debugging and autocomplete.
• Windows users: PowerShell, Bash via WSL, or the VSCode terminal.
• Expo Go for iOS and Android
  • 🤖 Android Play Store - Android Lollipop (5) and greater.
  • 🍎 iOS App Store - iOS 11 and greater.

Installing Node.js

You can install Node by going to the website directly and clicking the side that says "Recommended For Most Users". This will guide you through the process.

Once Node has been installed, run the following on the command line to make sure it's been installed correctly:

$ node -v

If you see the current version of Node in response, you've successfully installed Node on your machine.

For example,

$ node -v
v14.17.3

Installing Expo CLI

You can install the Expo CLI using the following command. This is the one spot where npm install is required!

$ npm install -g expo-cli

Verify that the installation was successful by running expo whoami. You're not logged in yet, so you will see "Not logged in". You can create an account by running expo register if you like, or if you have one already run expo login, but you also don't need an account to get started.

Install Project Dependencies

First, navigate to the project directory. The .zip will likely be in your downloads folder, so extract the .zip and move it to the desired location before proceeding.

Now, run the following commands to install the project dependencies (note that you'll need an internet connection to do so).

$ cd Desktop/New-App
$ yarn

The cd command above takes you into the project directory so you can install the correct dependencies. You should replace Desktop/New-App with the actual path to your unzipped project folder.

Running

To start your project, simply run: yarn start inside of the project directory (make sure you've installed the dependencies locally first). This should open the Expo developer tools in a browser tab.

Running in an emulator

You can run your app on your mobile device, on the iOS simulator (if you have a Mac), or on the Android emulator. If you'd prefer to run your app on an emulator, see the installation instructions below.

• iOS Simulator
• Android Studio

Running on your Android or iOS Device

The fastest way to get up and running is to use the Expo Go app on your iOS or Android device. Expo Go allows you to open up apps that are being served through Expo CLI.

• 🤖 Android Play Store - Android Lollipop (5) and greater.
• 🍎 iOS App Store - iOS 11 and greater.

File Structure

.
    ├── assets                 # Static assets like images and fonts.
    ├── config                 # JS representation of fonts, images, themes, and more
        └── Themes.js          # Example file for your app's themes
    ├── screens                # React Native code for the screens you built.
    │   └── MyFirstScreen.js   # Example file for the screen named "My First Screen"
    ├── components.js          # All your custom components
    ├── .gitignore             # List of files to ignore when comitting with Git
    ├── App.js                 # Entry point for your app
    ├── app.json               # Configuration file for your app, used by Expo
    ├── AppNavigator.js        # Code for your app's navigators
    ├── package.json           # The metadata for your project, including dependencies
    └── README.md              # This file!

Troubleshooting

Any errors that may occur in the process of developing or testing your app will show up as a "Redbox" error on the testing device. A red box will be show on the device with the error message and stack trace for the error. The Expo documentation has more information about Redbox errors.

Compilation errors or errors occurring when the expo process tries to execute commands will also show up in the browser. If you cannot fix these errors, you should refer to Expo's documentation on debugging Javascript.

FAQ

• What the hell is this?

  The No-Code movement is here. With two paradigm shifts going on, its only natural to FOMO YOLO and start building for the future of the web and society.

• Ok, that's cool and all but you still didn't answer my question?

• What libraries does this code depend on?

You can see the full list in your projects package.json file (under the dependencies section), but a few of our dependencies are react-navigation, react-native-screens, and expo-av.