homepage pop up motivator: current daily reports counter [10h]

[noamoss]

follow up of #196, part of #255

What:

Preconditions:

• [ ] automatic data serve mehchanism

When:

Desktop:

• user enters the homepage and doesn't click on the first chat button and doesn't expand the map within 3 secs.
• user expands the map on the homepage in the first 4 seconds after the user clicks on the map,

Mobile:

• user enter the homepage and doesn't click on the start chat button within 3 secs.

• user expands the map on the homepage in the first 3 seconds after the user clicks on the map,

• don't show the popup if a report was sent during the current browser session/current date

Steps:

• [ ] finalize texts + labels: 0.5h

• [ ] translate the standard sentence (with counter) and the fallback sentence (when total_daily_users < X): 0.5h (the idea is to avoid a situation telling a user at 9pm something like "Wow, we have 25 reports nationwide, join them!")

• [ ] create a function to query an updated total number in Israel: 1h

• [ ] Install a periodic task to requery every x minutes and store the results in a static location 3h

• [ ] Read the file at appropriate time 0.5h

• [ ] Implement timeout logic and (current_report_number > 2000): 3h

• [ ] QA: 0.5h

[noamoss]

I will add a specified suggestion later today, and then ask Mushon to review/design

[noamoss]

@akariv can you estimate?

// cc @mushon (following our talk today)

[mushon]

updated the image…

[akariv]

don't show the popup if a report was sent during the current browser session/current date

Not sure what this means.

Also I'm confused now, because I started commenting on a mockup that had a per-location pop up and it changed to a non location-specific pop-up (but the description remained the same)

[mushon]

don't show the popup if a report was sent during the current browser session/current date

meaning we only show this after a few seconds that the user has browsed the site without reporting today

As for the location-specificity, @noamoss I think after discussing the location-specific polygon, we agreed that we will use the general number for everyone so Bekoa will not be a depressing 0 that discourages reporting especially when it results in a no-data polygon. This approach also allows us to prompt new users without data.

[noamoss]

we agreed that we will use the general number

Correct, @akariv fixed description.

[akariv]

Can you explain about the current_report_number > 2000 ?

[noamoss]

I am not sure it would be 2000, we might change this value as we check effect - but the idea is to avoid a situation telling a user at 9pm something like "Wow, we have 25 reports nationwide, join them!"

[akariv]

Can you add that explanation to the description? What should happen in that case?

On Fri, Apr 24, 2020 at 1:53 PM noamoss notifications@github.com wrote:

I am not sure it would be 2000, we might change this value as we check effect - but the idea is to avoid a situation telling a user at 9pm something like "Wow, we have 25 reports nationwide, join them!"

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hasadna/avid-covider/issues/247#issuecomment-618942394, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5PFKW6E6WZZGZOE2B3ROFVRRANCNFSM4MO234QQ .

[noamoss]

@akariv done, anything else missing? please approve/relate to the time estimation as well.

[akariv]

I assume that the first desktop item should read - doesn't click on the chat button or expands the map?

[noamoss]

correct, fixed.

[akariv]

Updated the description

On Fri, Apr 24, 2020, 17:27 noamoss notifications@github.com wrote:

correct, fixed.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hasadna/avid-covider/issues/247#issuecomment-619043811, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAY5PHKNBOB54YRF3ZUG3ROGOVJANCNFSM4MO234QQ .