Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First inactivity interval at 3 weeks #132

Open
kmeyersvt opened this issue Sep 23, 2019 · 2 comments
Open

First inactivity interval at 3 weeks #132

kmeyersvt opened this issue Sep 23, 2019 · 2 comments
Labels
data Related to data from cvoeo or from app design question on hold
Projects

Comments

@kmeyersvt
Copy link
Collaborator

The client said that the first reminder should be sent after 3 weeks with no activity when there are active goals. That reminder should say, "Hey there, remember us? Your Money on My Mind goals? Tap here, you've got this!"

@kmeyersvt kmeyersvt added this to To do in CVOEO via automation Sep 23, 2019
@doub1ejack
Copy link
Member

Ok, we could do this by creating a firebase function that loops through each user in the database, and checking for scheduled push notifications. When it finds a user with a create date older than 3 weeks (this should probably not be hard-coded) and determines that no notifications have been sent in the last 3 weeks it could add a generic "Hey there.." notification to the queue.

Some related decisions/actions are:

  • ensure that when a new user is created, a create date is saved.
  • how/where should push notification records be stored?
  • how to indicate that they have been sent when we send them?

@doub1ejack doub1ejack added data Related to data from cvoeo or from app design question on hold labels Nov 2, 2019
@kmeyersvt
Copy link
Collaborator Author

kmeyersvt commented Nov 4, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Related to data from cvoeo or from app design question on hold
Projects
CVOEO
  
To do
Development

No branches or pull requests

2 participants