lanekatris / lkat-climb Goto Github PK

This how I want to be able to work with my data from sql

this can work with energy-rock too

Steps

• Delete the existing integration because it blows

• onUpdate/onCreate of firestore
• Publish climb to pub/sub raw
• Cloud function formats it and writes to bigquery

What?

Sometimes there are gaps between climbs. What were you doing? Well sometimes you are traversing or hanging or something or other work outs.

Why?

Work outs, traversals, hangs; these are different than sending problems. They are a different focus. Therefore you need a different way to track them. You get more of a picture of what your doing with sessions while also getting credit for improving! For example, traverse time, if your on the wall 20 seconds one week, and 60 seconds the second or third week, that's progress!

Acceptance Criteria

• Ability to create/delete timers
• Ability to name or tag or both timers

How?

• Events
  • TimerCreated
  • TimerStarted
  • TimerStopped
  • TimerDeleted
  • TimerTagAdded
  • TimerTagDeleted
• https://www.npmjs.com/package/react-compound-timer

What?

Currently we track sends for a difficulty. It is useful to know if you did a lot of easy climbs or a few hard climbs. You only see climb count and max difficulty. These are nice to know but a "overall understanding" metric of what you did isn't easily understood.

Some could think if you climbed 100 easy routes you could have the same number as you climbing 50 or 30 medium to difficult routes. This isn't necessarily true, just depends on the algorithm 😉 The goal isn't to even out, the goal is to see where effort was put. Since doing 10 V1 climbs is low points compared to 2 or 3 V5 climbs.

It also possibly could show where effort was put in, a lot of easy or a smaller amount of hard or maybe attempts?

Eventually, maybe this volume threshold could be a determinant of if you had a good workout, if you worked at your potential.

Acceptance Criteria

• On the climb list page show a "volume metric"

How?

For now go with climb difficulty * metric
And then maybe sum of above / total climb count - This would help mitigate if you climb 20 V0's, that doesn't mean you did more effort than 5 V5s.

0. 5
1. 6
2. 8
3. 10
4. 13
5. 18
6. 30

Examples

What?

It's useful to know when you are working on a project. How do you know your working on a project? You don't really. You see large gaps on the event log; i.e. I climbed a V5, and 1 hour later I climbed a V1. What was going on in-between?

There is a button that negates a climb, is this useful, do we want this? Could we change that button or keep it and add another that does something with attempts?

Acceptance Criteria

• Be able to create attempts via the RN app
• Show the attempt count on the climb detail page
• Show the attempt sum on the climb list page

How?

• Add a button that logs an attempt
• Create an event called AttemptCreated

{
  "createdOn": ISO Date,
  "difficuilty": 7
}

Yosemite Decimal System

Could remove it and hold down the plus button to serve the same functionality.

Use the mobile app to:

1. Login or use cookies
2. Ask which time block?
3. Am I already signed up for the time block?
4. Sign up for class on RhinoFit

Could show webview I guess

Trying out RN web to see how it treats me

1. Change firebase config
2. import firebase data
3. Change user ids?

• Talk about why it was built and what I was going for
• Give props to the template
• Make some GIFs of what it looks like
• Give expo link
• For iOS give email to request access

Based on a set time or amount of climbs tell the user they can't get at it

Right now it does an isBefore instead of a isBefore and isToday