This is getting out of hand. Though we're used to ts, flow is easier to integrate with create-react-app and works similarly.
https://facebook.github.io/create-react-app/docs/adding-flow

Schedule view screen which has the search bar and table view with dummy clickable workshop cells (name, time, short description...)

• Add support to configure notifications on different events and enable push notifications when they are to be at their shift

Once the ground truth authentication is resolved (#10 ), we should be able to pair with Josh's [https://github.com/HackGT/QA/tree/master/qa](generic QA backend) to have a working scavenger hunt backend.

The UI required by scavenger hunt will be

1. A camera module that can scan QR codes (probably the HackGT dressed up QR codes that @Nicholas714 played with a while ago) -> which will provide an id for a particular question, or the json specifying the corresponding question screen.
2. Once the id is provided, open the scavenger hunt question screen using the payload (probably will need React.Context or redux to track this payload)

• Nonmvp requirement would be to build out a module on QA backend to track user sessions on who is actively working on a problem/who has scanned to prevent fraudulent answer passing

3. The user will probably have a text input, the answer to the puzzle, which should be submittable. The screen should not be dismissed on submit, but internally allow up to some constant (3?) tries. The screen should also have a timeout.
4. There should be a simple screen to track scavenger hunt progress (I can extract this to a separate issue at relevant time)

The backend will need to be deployed, which I can do when this issue is arrived at.

Add CI for builds for both iOS and Android so builds can be submitted for distribution easier. For example, we can setup with fastlane and use GitHub actions for automatically distributing test builds and releases.

There are a few UI changes on the admin side that will greatly improve the user experience

• Make it work for dark and light mode (fix font color, background color, etc.)
• Fix text-overflow for event descriptions
• Fix back button positioning to make it more intuitive once you select an event
• Add tab to switch between QR code scanning and NFC scanning

Add some system to check that iOS and Android at least build successfully cc @ehsanmasdar - this would be new docker steps and then the same cloudbuild and deployment.yaml right? Any anticipated different steps?

Instead of admins having a separate view, there should be a new tab on the participant view to do NFC and QR code scanning

display push notifications from slack on the app

On checking people in to an event, show more statistics like # of users already checked in to an event, etc. This should be mostly a backend endpoint where a request is made with an event id

According to Apple review, we need to integrate Apple login to be approved in the app store

Workshop/Minievent View screen which displays when workshop cell is clicked in schedule view (summary, links, add to schedule button...)

Something's inconsistent and we're not getting firebase notifs in-app on Android.

Configure the app to support local notifications: https://github.com/zo0r/react-native-push-notification.

This also includes #7 - furnish the notification view (according to design from kimberly). Then, enable scheduled notifications from schedule file (from a mocked schedule json - coordinate with nick).

Instead of storing scavenger hunt data locally on device, use api backend to get completed interactions

Don't make people (admins + participants) have to use laptops for swag. Swag checkout is just tapping NFC/QR code and you can see your swag points on app

For Horizons, we used QR code scanning, but for future events, we need NFC badge scanning capability, but we should still retain QR code scanning ability for check in

Look here to setup remote config, a way to seamlessly roll out new changes without having to upload app updates

Switch from using ground truth to using firebase auth to be consistent with login.hexlabs.org.

“View Account” that takes to a new page where you can see account info like name, email, etc. and then have the delete button on there. It kinda seems a little out there having it on the main page.

Every 5 minutes, repull the event data to keep the app schedule in check.

The old code was written in class based components, so switch these over to functional components and using hooks (especially useReducer).

Implement a tagging system that is specified in a json or yaml file.
Tags should be specified as a dictionary of { <codeName>: <prettyString> } i.e. { food: Food }. Ok, dumb example, but we shouldn't just be uppercasing, so you get the point. Specify tags as a field on the workshop and event schema i.e.

workshops: [{
name: "AI Security for the Modern World"
tags: ["ai", "workshop", "security"]
}, ]

We should be concerned about typos in the tags above (probably have readme warnings) but I'm pretty sure any CMS besides Github files should have solved this kind of problem, so we'll just have to be careful for now.

Selected tags should be stored in a global React.Context and should be toggle-able in a tag selection component - (Design TBA)

Tags should be displayed on events, and workshops (there's a working design posted on zeplin - follow up w/ me or Kimberly about this)

Add a filter by tag on main schedule, and automatically filter my schedule page using followed tags. (use mock data to test)

The schedule fetches from the old CMS, and we'd like to switch over to our simpler blocks system here

Food lines are hard to manage, create a virtual queue to better manage this.

• Divides people into batches and sends them notifs when their batch can come for food

Pull a QR code from registration (or make it yourself) and show it once you're logged in.

In order to support scavenger hunt progress, it makes sense for the app to have login. This opens to doors for many further integrations and was an inevitable step.

UI wise, this means a simple login screen, that should be accessible via the homepage (as a button prompt - please log in to track scavenger hunt!). No backend is yet needed since ground truth is separately deployed.
However, dealing with OAuth (which ground truth implements) on react native can be fairly sticky. The following references should be useful, along with @petschekr for any questions about ground truth.
https://github.com/fullstackreact/react-native-oauth - Existing library for boilerplate
https://blog.usejournal.com/persisting-user-authentication-in-a-react-native-app-778e028ac816 - Medium article, classic
*** https://github.com/FormidableLabs/react-native-app-auth - I think this is the standard library, with more documentation

When you launch the app, the wrong tab schedule is shown

Change workshop view to notification view (basically just rename the files and change the buttons titles or you can also delete those files and references and create a new one for the Notification screen and add functionality to be able to navigate to it)

Add the ability to scan QR codes directly in scavenger hunt

Add screen for homepage and add navbar buttons to be able to navigate

Navbar will toggle between schedule and workshop views

Firebase has a lot of integrations for mobile apps. Of note, we should add crashlytics for better error reporting

Allow users to manually follow individual events by exposing a starring mechanic. IDs should just be provided on the queried schedule items, again, we should be able to hold a list of starred items in React.Context.

Starred items should show up under "My Schedule," on top of the followed tags.
Do after #12