Page MenuHomePhabricator

[native] enable connect farcaster prompt, display prompt after nux tips have all been dismissed
Changes PlannedPublic

Authored by varun on Sun, Mar 23, 9:22 AM.
Tags
None
Referenced Files
F5107462: D14488.id47578.diff
Tue, Apr 1, 11:08 AM
Unknown Object (File)
Mon, Mar 31, 8:58 PM
Unknown Object (File)
Sun, Mar 30, 9:12 PM
Unknown Object (File)
Sun, Mar 30, 6:06 PM
Unknown Object (File)
Fri, Mar 28, 6:06 PM
Unknown Object (File)
Fri, Mar 28, 12:44 PM
Unknown Object (File)
Fri, Mar 28, 8:49 AM
Unknown Object (File)
Thu, Mar 27, 11:33 PM
Subscribers

Details

Reviewers
ashoat
Summary

with this change, the connect farcaster prompt appears after all the nux tips have been dismissed, instead of simultaneously

Depends on D14446

Test Plan

tested on release build

Diff Detail

Repository
rCOMM Comm
Branch
master
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

varun published this revision for review.Sun, Mar 23, 9:25 AM
  1. use coldStartCount to make sure we don't display connect farcaster alert right after NUX
  2. use connectFarcasterAlertInfo in DisplayCommunityDirectoryPromptHandler to make sure we don't display community directory prompt until a day after connect farcaster prompt
ashoat requested changes to this revision.EditedWed, Mar 26, 8:51 PM

Your test plan is super incomplete. Can you please update the test plan to go one-by-one through every scenario we've had to contemplate while working on this? Eg. fresh registration, log in of existing user with Farcaster connection, log in of existing user with no Farcaster connection, existing log-in that hasn't logged out since before the new registration flow (never got prompted to connect Farcaster), etc.

native/components/display-community-directory-prompt.react.js
64 ↗(On Diff #47578)

Won't this check make it so users that register and get fid set to something other than undefined (and consequently never get the connect Farcaster prompt) will never see the community directory?

This revision now requires changes to proceed.Wed, Mar 26, 8:51 PM

make cold start count a per-alert type count instead of a global count, migrations, stagger the connect farcaster and community directory prompts

need to finish testing this