Hot&Cold is an open source, full-stack, heatmap-based social chat app. Featuring:
This is the main repository of the app, but only includes the front-end part of it; please see its complient back-end project. The app should be working on both Android and iOS, but was developed mostly with Android in mind.
The app is currently available for Android on PlayStore.
Configure the following services:
Add the following fields to gradle.properties:
# See the following guide for further info: https://reactnative.dev/docs/signed-apk-android.html
MYAPP_RELEASE_STORE_FILE
MYAPP_RELEASE_KEY_ALIAS
MYAPP_RELEASE_STORE_PASSWORD
MYAPP_RELEASE_KEY_PASSWORD
android.useAndroidX=true
android.enableJetifier=true
FLIPPER_VERSION=0.37.0
If you're developing for iOS, from XCode, go to `product > schema > edit schema > build (hotncold) > pre-actions' and add the following script:
ENVFILE=.env.development
echo $ENVFILE > /tmp/envfileDefine environment variables in .env.$ENVNAME file (NEVER COMMIT):
# A public access token to MapBox's API
MAPBOX_ACCESS_TOKEN
# The map style URL given by MapBox's API
MAPBOX_STYLE_URL
# URL to Hot&Cold's server
SERVER_URI
# URL to Hot&Cold's server GraphQL endpoint
GRAPHQL_ENDPOINT
# If specified, pressed notifications will remain
PERSIST_NOTIFICATIONS
# The maximum creation distance of statuses from GPS location in meters
STATUS_CREATION_RADIUS
# Run app with Robot. Robot files will not be bundled if this var is provided
USE_ROBOT
To enable push notifications, download google-services.json and GoogleService-Info.plist from Firebase console to android/app and ios/hotncold directories respectively. See further instructions.
Run the following commands in series:
$ yarn
$ yarn codegen
Make sure you have a device connected with adb devices.
Run the packager in one tab:
$ yarn start
Trigger the app on a second tab:
$ yarn android
You can also bundle a debug-apk file with warnings remaining (Android only, useful for troubleshooting issues). First, make sure that you have the following extension defined in your android/app/build.gradle file:
project.ext.react = [
// ...
bundleInDebug: true
]And then run the following:
# Output: android/app/build/outputs/apk/debug/app-debug.apk
$ yarn bundledebug
$ android/gradlew assembleDebug
Make sure to remove bundleInDebug option from your build.gradle file for continues work!
6E71 Hidden inputs
When signing-in, you can unlock test mode by spam-tapping on the country code field. At some point you it should turn into -0, which indicates you've just activated test mode successfully.
There's 2 methods to proceed from this point on: The first one is by filling-out the phone field with 0s, or you can select your country code and fill-out your real number. With the first method you won't receive any text message, authentication will only be done locally, and with the second method, you'll receive an actual text message. Either way, the verification code will appear on screen for testing purposes. Once you continue, the app should function normally; only difference you'll be able to see users-mocks only.
Each supported geographical area should have at least 1 user-mock that should be detectable on the map or by the radar.To get a feedback from a fake user when chatting with it, you can send the word echo to get a response. Alternatively, you can specify a delay time (in seconds) by concatenating a parameter e.g. echo 5.
Hot&Cold uses Firebase Test Lab in conjunction with an internal module called Robot. The paradigm is that Robo (notice the lack of T), a tool that Firebase uses to simulate input on real Android devices, doesn't work with React-Native. This is because React-Native wraps native Android view elements in a unique way that is not accessible to Robo, hence Robot was created. See this Meidum post about Bobcat (aka Robot) for further info.
RoboT scripts are located under the robot/scopes and have direct control over React elements. In addition to having Robot scripts, you need to record a Robo script with Android-Studio, so you can press native modals, such as alerts, date-time pickers, and permissions. It's required that the RoboT script will end end with any native modal, so it will be used as an anchor for Robo, otherwise the tests will be aborted mid-session.
Robot .apk can be assembled with yarn assembleRobot and it will override the app-release.apk file.
First, follow these instructions:
Assemble an .apk file:
# Output: android/app/build/outputs/apk/release/app-release.apk
$ android/gradlew assembleRelease
The app can be distributed as is or installed with adb:
$ adb install <path>