6peterlu / coherence-chat

Chatservice for Coherence

coherence-chat

Chatservice for Coherence

Deployment pattern

During development, test with a dev flask server: NOALERTS=1 python bot.py.

Unit tests:

NOALERTS=1 pytest -vv

Before pushing to prod, test with gunicorn locally: NOALERTS=1 gunicorn -b 0.0.0.0:5000 bot:app --workers 1

Build the frontend into prod mode with yarn build inside the web/ directory.

Then you can safely push to prod.

alembic usage

python manage.py db migrate

python manage.py db upgrade

When you make a db migration, go to the alembic file and remove all the apscheduler references. There's some weirdness because those tables are not created by sqlalchemy.

ngrok for local dev

ngrok http 5000

Update twilio URL

git

reset N commits locally: git reset --hard HEAD~N

push a non master branch to heroku master: git push heroku +HEAD:master

data analysis

dump prod DB to local: delete local analysis_db, then heroku pg:pull postgresql-slippery-57674 analysis_db --app coherence-chat

stripe local testing setup

open new terminal tab and do stripe listen --forward-to 5000 to forward stripe test events to local

coherence-chat's Issues

NLP: "1 hour 30 minutes" -> 1 hour

• regex is only grabbing the first part

ux: people saying yes instead of T

reminders: saying T@ current time while in a dose window doesn't cancel reminders

launch blocking UX

TODO:

• card number styling
• cvc explanation
• link to homepage from payment verification page
• make go home button more intuitive from payments page
• make a settings page for timezones
• bury subscription cancellation button
• remove subscription section of menu unless user is within 7 days of trial end
• add more stuff to profile settings so its clearer what it is
• login screen responsiveness
• link to this page from vancouverprimarycare.com
• testimonials on the landing page [BLOCKED on someone's testimonial]
• flip on prod stripe

ux: "dose window" should trigger change dose windows help response

ux: settings page is slow to load

ux: if people attempt rerecord, just update the time

onboarding: autosend multiple followup texts for signed up users

devops: test APScheduler writing to real db

• in testing, APScheduler writes to the actual app's db, which makes it not a clean test and could cause prod errors if run in prod.

tech debt: separate payment in onboarding from normal payment component

onboarding: separate it from paused status

onboarding should be its own flag. also, more thought needs to be put into its flow

scheduler: still lets you schedule a reminder with minutes after marking a dose as taken.

login: for some users, login flow doesn't let them through

The token being stored in the browser doesn't match the one we're sending back.

Ex: miki:

setting cookie to eyJhbGciOiJIUzUxMiIsImlhdCI6MTYyMTgzNzY2MywiZXhwIjoxNjI0NDI5NjYzfQ.eyJpZCI6MTUyfQ.9WocLs5DpnI13EQ-CmBAfdTQYQDA0601AM5Fn5JGSlvmKiGJPPjEV1uk36ZewBcDvKYZTCko4EpFCEiZmhTiaQ
became
eyJhbGciOiJIUzUxMiIsImlhdCI6MTYyMDg0MjkyMCwiZXhwIjoxNjIzNDM0OTIwfQ.eyJpZCI6MTUyfQ.1jQ9u6Ggi25AU-NzcxPLCmSPYU2uyajBW6J9G2k1y9Pf8QNk6aw8YzxotgsJzrgrvQvSTD1PAq18bltkL2ophA in the browser

cause is still unknown and doesnt repro on my end for chrome or firefox.

ux: let people set day boundaries

ux: taken out of range

• make it easy to change dose windows

bug: updating dose window dosent update dose window

history taking: sanely handle past events in case of time zone change

performance / devops: use redux to manage frontend state

right now, we just fresh load everything

also, separate loads into each request instead of updating the entire payload each time

onboarding guides: taken semantics

anyone who says "taken/took" but we can't understand what they mean, tell them the correct semantics

LAUNCH CHECKLIST

REQUIREMENTS

• one URL in app: hellocoherence.com.
• augment login screen with marketing info
  TODO:
• add marketing material to coherence login page
• transfer heroku app to hellocoherence.com
• fix ipad rendering issue
• test early access code flow
• create way to see signups in admin dash
• allow easier filtering per user in admin dash

ssl: going to https://hellocoherence.com leads to insecure site

tz parsing: "in 1.5 hr"

• in 1.5 hr
• in one hour
  also "ten minutes"

onboarding: autosend website link to new users after a few days of using the service

history taking: taken slightly outside of dose window

People mark T both before and after their dose windows, and we should be smart enough to "snap to" the nearest one

bug: after midnight, dose window jobs are not cancelled

website: if you flip iphone sideways it has huge whitespace

it's happening on medium size screens

ux: remind me at is very flaky

• things that don't work: remind me at 1:30, remind me at 1

nlp: taken @ 7:30pm

need to record the right time

admin: alerting for users falling off the wagon

• devise interventions, automate

nlp: 1pm interpreted as "1"

fast follow UX

TODO:

• 7 days before subscription expiration, show a banner to push people to enter payment info
• autoresume after subscription renewal
• tell expired service people that their service is expired and give them customer service number
• subscription renewal should put user in active state regardless of past orientation
• send subscription end message instead of scheduled message if subscription expired (tabled)

data integrity: marking a past dose as taken doesn't remove boundary

security: saner 2fa needed

bug: resume doesnt send text

only on boabs acct

payments: payment method not attaching during paid onboarding

ux: sort dose windows by start time

not by order of entry

manual takeover is broken

bug: activity + reminder causes bad followup message behavior

2 "On a walk" leads to walk estimation instead of 2 overriding reminder time.

cost mitigation: send action menu only once/day

nlp: 3 "making chicken enchiladas" doesn't register the 3 command

hmmmm

scheduling: ignore activity data if its too sparse in the dose window

• right now, user data outside of dose window may allow sparse dose window data to produce bad predictions, for patients like Leann and Cheryl.

ux: automatically determine month range for user

this should be resolved before may is over ideally

patient portal ui: handle multiple dose windows in same semantic time range

• like two afternoon doses, display that correctly

ux: bot should respond in paused state to tell people its paused

ux: more intelligent snap to for T @

T @ should locate the nearest time (tear out the am/pm sketchiness) for the last dose window and mark it

automation: determine day boundaries intelligently

• we're going to run into scaling issues if we have to hard code this

onboarding: autosend initial setup text

ux: timezone sanity

TODO:

• move dose windows on tz change, get it to work with the manual dropdown
• show UX when web tz doesn't match tz on record and offer option to change.

testing: build a sane way to test stripe flows locally

stability: Porting master tracker

• manual event setting (take, skip)
• manual job scheduling