+
+> The install command filters out the expo package and saves a few second (and cache size) of dependency installation. The build command makes us build the application using Turbo.
+
+2. Add your `DATABASE_URL`,`NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY` and `CLERK_SECRET_KEY` environment variable.
+
+3. Done! Your app should successfully deploy. Assign your domain and use that instead of `localhost` for the `url` in the Expo app so that your Expo app can communicate with your backend when you are not in development.
+
+### Expo
+
+Deploying your Expo application works slightly differently compared to Next.js on the web. Instead of "deploying" your app online, you need to submit production builds of your app to the app stores, like [Apple App Store](https://www.apple.com/app-store/) and [Google Play](https://play.google.com/store/apps). You can read the full [Distributing your app](https://docs.expo.dev/distribution/introduction/), including best practices, in the Expo docs.
+
+1. Let's start by setting up [EAS Build](https://docs.expo.dev/build/introduction/), which is short for Expo Application Services. The build service helps you create builds of your app, without requiring a full native development setup. The commands below are a summary of [Creating your first build](https://docs.expo.dev/build/setup/).
+
+ ```bash
+ // Install the EAS CLI
+ $ pnpm add -g eas-cli
+
+ // Log in with your Expo account
+ $ eas login
+
+ // Configure your Expo app
+ $ cd apps/expo
+ $ eas build:configure
+ ```
+
+2. After the initial setup, you can create your first build. You can build for Android and iOS platforms and use different [**eas.json** build profiles](https://docs.expo.dev/build-reference/eas-json/) to create production builds or development, or test builds. Let's make a production build for iOS.
+
+ ```
+ $ eas build --platform ios --profile production
+ ```
+
+ > If you don't specify the `--profile` flag, EAS uses the `production` profile by default.
+
+3. Now that you have your first production build, you can submit this to the stores. [EAS Submit](https://docs.expo.dev/submit/introduction/) can help you send the build to the stores.
+
+ ```
+ $ eas submit --platform ios --latest
+ ```
+
+ > You can also combine build and submit in a single command, using `eas build ... --auto-submit`.
+
+4. Before you can get your app in the hands of your users, you'll have to provide additional information to the app stores. This includes screenshots, app information, privacy policies, etc. _While still in preview_, [EAS Metadata](https://docs.expo.dev/eas/metadata/) can help you with most of this information.
+
+5. If you're using OAuth social providers with Clerk, for instance Google, Apple, Facebook, etc..., you must whitelist your own OAuth redirect URL for the Expo application in the Clerk Dashboard.
+
+ In `apps/expo/app.config.ts`, add a `scheme` that will be used to identify your standalone app.
+
+ ```ts
+ import { ExpoConfig, ConfigContext } from '@expo/config'
+
+ const CLERK_PUBLISHABLE_KEY = 'your-clerk-publishable-key'
+
+ const defineConfig = (_ctx: ConfigContext): ExpoConfig => ({
+ name: 'expo',
+ slug: 'expo',
+ scheme: 'your-app-scheme',
+ // ...
+ })
+ ```
+
+ Then, in the [Clerk Dashboard](https://dashboard.clerk.dev/), go to **User & Authentication > Social Connections > Settings** and add your app's scheme and redirect URL to the **Redirect URLs** field:
+
+ ```txt
+ your-app-scheme://oauth-native-callback
+ ```
+
+ Here, `your-app-scheme` corresponds to the `scheme` defined in `app.config.ts`, and `oauth-native-callback` corresponds to the redirect URL defined when authenticating with social providers. See [SignInWithOAuth.tsx](/apps/expo/src/components/SignInWithOAuth.tsx) for reference.
-- If you can, keep lines under 100 characters.
- - consider setting a guide line in your editor
- - some times long lines are unavoidable. We won't reject a pr over this issue.
-- We prefer most functions to be declared using the `function myFunction(){}` syntax as opposed to arrow functions.
- - the exception is when you are passing an inline function as a parameter. In this case please use arrow functions.
-- We prefer functional components and react hooks as opposed to class components.
-- Limit comments.
- - We prefer where possible code to be self documenting.
- - JS doc comments do not count.
- - If you are exporting a function or a class feel free to add any documentation you deem necessary.
-- Limit single line if statements.
- - accept in certain cases please add brackets after if statements even if they are only a single line.
- - the exception is if you are checking the condition and immediately breaking the current scope. For example:
-
- ```tsx
- if(!condition) return
- ```
-- Where possible apply single responsibility principle.
+ > You can find more information about this in the [Expo documentation](https://docs.expo.dev/versions/latest/sdk/auth-session/#redirecting-to-your-app).
-### Submitting a Pull Request
-If you are not familiar with the process of submitting a pull request we suggest you check out the [docs](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) provided by GitHub.
+ You should now be able to sign in with your social providers in the TestFlight application build.
-We ask that your pull request have the following information:
+6. Once everything is approved, your users can finally enjoy your app. Let's say you spotted a small typo; you'll have to create a new build, submit it to the stores, and wait for approval before you can resolve this issue. In these cases, you can use EAS Update to quickly send a small bugfix to your users without going through this long process. Let's start by setting up EAS Update.
-#### Motivation
-> Why is this change necessary? What problem does it solve?
+ The steps below summarize the [Getting started with EAS Update](https://docs.expo.dev/eas-update/getting-started/#configure-your-project) guide.
-> If this is related to an issue which one?
+ ```bash
+ // Add the `expo-updates` library to your Expo app
+ $ cd apps/expo
+ $ pnpm expo install expo-updates
-Closes #ISSUE_NUMBER
+ // Configure EAS Update
+ $ eas update:configure
+ ```
-#### Implementation
-> How does this PR solve the problem? What technical approach is taken?
+7. Before we can send out updates to your app, you have to create a new build and submit it to the app stores. For every change that includes native APIs, you have to rebuild the app and submit the update to the app stores. See steps 2 and 3.
-#### Testing
-> How did you verify that this works? Were automated tests written?
-> What manual tests were performed?
+8. Now that everything is ready for updates, let's create a new update for `production` builds. With the `--auto` flag, EAS Update uses your current git branch name and commit message for this update. See [How EAS Update works](https://docs.expo.dev/eas-update/how-eas-update-works/#publishing-an-update) for more information.
-#### Related PRs
-> Optional: if any other PRs provide context to this change
+ ```bash
+ $ cd apps/expo
+ $ eas update --auto
+ ```
-If your pull request does not have this information or some equivalent attached it will be rejected without further consideration.
+ > Your OTA (Over The Air) updates must always follow the app store's rules. You can't change your app's primary functionality without getting app store approval. But this is a fast way to update your app for minor changes and bug fixes.
-### Issues
-If you don't want to contribute directly or don't feel ready to file a pull request you are welcome to contribute by filing issues.
+9. Done! Now that you have created your production build, submitted it to the stores, and installed EAS Update, you are ready for anything!
-We want Iris to be as great of an experience as possible and the only way for us to accomplish that is to get feedback. Please if you see a problem, let us know!
+## References
-If you don't know how to file an issue here is a [guide](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue) from GitHub.
+The stack originates from [create-t3-turbo](https://github.com/t3-oss/create-t3-turbo).
diff --git a/app.json b/app.json
new file mode 100644
index 0000000..42e5bfa
--- /dev/null
+++ b/app.json
@@ -0,0 +1,17 @@
+{
+ "expo": {
+ "extra": {
+ "eas": {
+ "projectId": "0fa37b39-ff25-4053-ba33-a30409f8546e"
+ }
+ },
+ "android": {
+ "package": "com.jasonboyett.projectIris"
+ },
+ "ios": {
+ "bundleIdentifier": "com.jasonboyett.projectIris"
+ },
+ "owner": "jasonboyettsoftwareconsulting",
+ "slug": "iris"
+ }
+}
diff --git a/apps/expo/.expo-shared/assets.json b/apps/expo/.expo-shared/assets.json
new file mode 100644
index 0000000..1e6decf
--- /dev/null
+++ b/apps/expo/.expo-shared/assets.json
@@ -0,0 +1,4 @@
+{
+ "12bb71342c6255bbf50437ec8f4441c083f47cdb74bd89160c15e4f43e52a1cb": true,
+ "40b842e832070c58deac6aa9e08fa459302ee3f9da492c7e77d93d2fbf4a56fd": true
+}
diff --git a/apps/expo/app.config.ts b/apps/expo/app.config.ts
new file mode 100644
index 0000000..f1c0060
--- /dev/null
+++ b/apps/expo/app.config.ts
@@ -0,0 +1,40 @@
+import type { ExpoConfig, ConfigContext } from '@expo/config'
+
+const CLERK_PUBLISHABLE_KEY = 'pk_test_bGVuaWVudC1tdXN0YW5nLTIxLmNsZXJrLmFjY291bnRzLmRldiQ'
+
+const defineConfig = (_ctx: ConfigContext): ExpoConfig => ({
+ name: 'iris',
+ slug: 'expo',
+ version: '1.0.0',
+ orientation: 'portrait',
+ icon: './assets/icon.png',
+ userInterfaceStyle: 'automatic',
+ splash: {
+ image: './assets/IRIS-LOGO.png',
+ resizeMode: 'contain',
+ backgroundColor: '#2e026d',
+ },
+ updates: {
+ fallbackToCacheTimeout: 0,
+ },
+ assetBundlePatterns: ['**/*'],
+ ios: {
+ supportsTablet: true,
+ bundleIdentifier: 'your.bundle.identifier',
+ },
+ android: {
+ adaptiveIcon: {
+ foregroundImage: './assets/icon.png',
+ backgroundColor: '#2e026d',
+ },
+ },
+ extra: {
+ eas: {
+ projectId: '0fa37b39-ff25-4053-ba33-a30409f8546e',
+ },
+ CLERK_PUBLISHABLE_KEY,
+ },
+ plugins: ['./expo-plugins/with-modify-gradle.js'],
+})
+
+export default defineConfig
diff --git a/apps/expo/assets/IRIS-LOGO.png b/apps/expo/assets/IRIS-LOGO.png
new file mode 100644
index 0000000..2ebf1c9
Binary files /dev/null and b/apps/expo/assets/IRIS-LOGO.png differ
diff --git a/public/flying-butterfly.gif b/apps/expo/assets/flying-butterfly.gif
similarity index 100%
rename from public/flying-butterfly.gif
rename to apps/expo/assets/flying-butterfly.gif
diff --git a/apps/expo/babel.config.js b/apps/expo/babel.config.js
new file mode 100644
index 0000000..b96b882
--- /dev/null
+++ b/apps/expo/babel.config.js
@@ -0,0 +1,12 @@
+module.exports = function(api) {
+ api.cache(true);
+ return {
+ plugins: [
+ "nativewind/babel",
+ "react-native-reanimated/plugin"
+ ],
+ presets: [
+ "module:metro-react-native-babel-preset"
+ ],
+ };
+};
diff --git a/apps/expo/expo-plugins/with-modify-gradle.js b/apps/expo/expo-plugins/with-modify-gradle.js
new file mode 100644
index 0000000..2fc40f0
--- /dev/null
+++ b/apps/expo/expo-plugins/with-modify-gradle.js
@@ -0,0 +1,41 @@
+//@ts-check
+
+// This plugin is required for fixing `.apk` build issue
+// It appends Expo and RN versions into the `build.gradle` file
+// References:
+// https://github.com/t3-oss/create-t3-turbo/issues/120
+// https://github.com/expo/expo/issues/18129
+
+const { withProjectBuildGradle } = require("@expo/config-plugins");
+
+module.exports = (config) => {
+ return withProjectBuildGradle(config, (config) => {
+ if (!config.modResults.contents.includes("ext.getPackageJsonVersion =")) {
+ config.modResults.contents = config.modResults.contents.replace(
+ "buildscript {",
+ `buildscript {
+ ext.getPackageJsonVersion = { packageName ->
+ new File(['node', '--print', "JSON.parse(require('fs').readFileSync(require.resolve('\${packageName}/package.json'), 'utf-8')).version"].execute(null, rootDir).text.trim())
+ }`,
+ );
+ }
+
+ if (!config.modResults.contents.includes("reactNativeVersion =")) {
+ config.modResults.contents = config.modResults.contents.replace(
+ "ext {",
+ `ext {
+ reactNativeVersion = "\${ext.getPackageJsonVersion('react-native')}"`,
+ );
+ }
+
+ if (!config.modResults.contents.includes("expoPackageVersion =")) {
+ config.modResults.contents = config.modResults.contents.replace(
+ "ext {",
+ `ext {
+ expoPackageVersion = "\${ext.getPackageJsonVersion('expo')}"`,
+ );
+ }
+
+ return config;
+ });
+};
diff --git a/apps/expo/index.ts b/apps/expo/index.ts
new file mode 100644
index 0000000..0ae9b1e
--- /dev/null
+++ b/apps/expo/index.ts
@@ -0,0 +1,8 @@
+import { registerRootComponent } from 'expo'
+
+import { App } from './src/_app'
+
+// registerRootComponent calls AppRegistry.registerComponent('main', () => App);
+// It also ensures that whether you load the app in Expo Go or in a native build,
+// the environment is set up appropriately
+registerRootComponent(App)
diff --git a/apps/expo/metro.config.js b/apps/expo/metro.config.js
new file mode 100644
index 0000000..2bad241
--- /dev/null
+++ b/apps/expo/metro.config.js
@@ -0,0 +1,26 @@
+// Learn more: https://docs.expo.dev/guides/monorepos/
+// eslint-disable-next-line @typescript-eslint/no-var-requires
+const { getDefaultConfig } = require('expo/metro-config');
+// eslint-disable-next-line @typescript-eslint/no-var-requires
+const path = require('path');
+
+const projectRoot = __dirname;
+const workspaceRoot = path.resolve(projectRoot, '../..');
+
+// Create the default Metro config
+const config = getDefaultConfig(projectRoot);
+
+// Add the additional `cjs` extension to the resolver
+config.resolver.sourceExts.push('cjs');
+
+// 1. Watch all files within the monorepo
+config.watchFolders = [workspaceRoot];
+// 2. Let Metro know where to resolve packages and in what order
+config.resolver.nodeModulesPaths = [
+ path.resolve(projectRoot, 'node_modules'),
+ path.resolve(workspaceRoot, 'node_modules'),
+];
+// 3. Force Metro to resolve (sub)dependencies only from the `nodeModulesPaths`
+config.resolver.disableHierarchicalLookup = false;
+
+module.exports = config;
diff --git a/apps/expo/package.json b/apps/expo/package.json
new file mode 100644
index 0000000..058f484
--- /dev/null
+++ b/apps/expo/package.json
@@ -0,0 +1,64 @@
+{
+ "name": "@acme/expo",
+ "version": "0.1.0",
+ "main": "index.ts",
+ "scripts": {
+ "start": "expo start",
+ "dev": "expo start",
+ "clean": "rm -rf .expo .turbo node_modules",
+ "android": "expo start --android",
+ "ios": "expo start --ios",
+ "web": "expo start --web",
+ "lint": "eslint . --ext ts,tsx"
+ },
+ "dependencies": {
+ "@acme/api": "*",
+ "@acme/helpers": "*",
+ "@acme/tailwind-config": "*",
+ "@acme/types": "*",
+ "@acme/validators": "*",
+ "@clerk/clerk-expo": "^0.17.7",
+ "@expo/webpack-config": "^19.0.1",
+ "@react-native-async-storage/async-storage": "1.18.2",
+ "@react-navigation/drawer": "^6.6.6",
+ "@shopify/flash-list": "^1.4.3",
+ "@tanstack/react-query": "^4.16.1",
+ "@trpc/client": "^10.1.0",
+ "@trpc/react-query": "^10.1.0",
+ "@trpc/server": "^10.1.0",
+ "expo": "^49.0.0",
+ "expo-auth-session": "^5.0.2",
+ "expo-background-fetch": "~11.3.0",
+ "expo-constants": "~14.4.2",
+ "expo-linking": "~5.0.2",
+ "expo-random": "^13.2.0",
+ "expo-router": "^2.0.14",
+ "expo-secure-store": "^12.3.1",
+ "expo-status-bar": "^1.6.0",
+ "expo-task-manager": "~11.3.0",
+ "expo-web-browser": "^12.3.2",
+ "nativewind": "^2.0.11",
+ "react": "18.2.0",
+ "react-dom": "18.2.0",
+ "react-native": "0.72.6",
+ "react-native-async-storage": "^0.0.1",
+ "react-native-gesture-handler": "~2.12.0",
+ "react-native-reanimated": "~3.3.0",
+ "react-native-safe-area-context": "4.6.3",
+ "react-native-screens": "~3.22.1",
+ "react-native-web": "~0.19.10",
+ "uuidv5": "^1.0.0"
+ },
+ "devDependencies": {
+ "@babel/core": "^7.19.3",
+ "@babel/preset-env": "^7.19.3",
+ "@babel/runtime": "^7.19.0",
+ "@types/react": "^18.0.38",
+ "@types/react-native": "~0.70.6",
+ "eslint": "^8.28.0",
+ "postcss": "^8.4.19",
+ "tailwindcss": "^3.2.4",
+ "typescript": "^4.9.3"
+ },
+ "private": true
+}
diff --git a/apps/expo/src/_app.tsx b/apps/expo/src/_app.tsx
new file mode 100644
index 0000000..3540ce1
--- /dev/null
+++ b/apps/expo/src/_app.tsx
@@ -0,0 +1,104 @@
+import type { NavigationProp } from '@react-navigation/native'
+import { TrainingScreen } from './components/Train'
+import { StatusBar } from 'expo-status-bar'
+import React from 'react'
+import { SafeAreaProvider } from 'react-native-safe-area-context'
+import { TRPCProvider } from './utils/trpc'
+
+import { HomeScreen } from './screens/home'
+import SignOutScreen from './screens/signout'
+import { SignInSignUpScreen } from './screens/auth'
+import { ClerkProvider, SignedIn, SignedOut } from '@clerk/clerk-expo'
+import { tokenCache } from './utils/cache'
+import Constants from 'expo-constants'
+import { NavigationContainer } from '@react-navigation/native'
+import { createNativeStackNavigator } from '@react-navigation/native-stack'
+import { createDrawerNavigator } from '@react-navigation/drawer'
+import SettingsScreen from './screens/Settings'
+
+export type ScreenNames = [
+ 'Home',
+ 'Iris',
+ 'SpeedTest',
+ 'Train',
+ 'SignOut',
+ 'Settings'
+]
+export type StackParamList = Record