User Details
- User Since
- Nov 30 2021, 11:14 AM (174 w, 10 h)
Yesterday
need to finish testing this
make cold start count a per-alert type count instead of a global count, migrations, stagger the connect farcaster and community directory prompts
Wed, Mar 26
- use coldStartCount to make sure we don't display connect farcaster alert right after NUX
- use connectFarcasterAlertInfo in DisplayCommunityDirectoryPromptHandler to make sure we don't display community directory prompt until a day after connect farcaster prompt
Sun, Mar 23
the hardware back button on android does close the bottom sheet, but doesn't trigger the component's onChange callback
address feedback
Sun, Mar 16
Feels like there are probably ways to dismiss the modal without setting the fid to null here. Ideally we can catch all methods of closing the modal, but if that's really hard, one alternative would just be to set the fid to null as soon as we show the modal.
Alternately, does this occur for every fresh install login?
Ended up testing the connect farcaster flow and it works. A couple things worth noting:
- The connect farcaster bottom sheet appears at the same time as the NUX tips if the user installs the app and logs in. Not sure if this edge case is worth addressing
some updates
need to think about how to sequence things a little more
Sat, Mar 15
Mar 1 2025
Feb 28 2025
CI has been stuck for a day
CI has been stuck for a day
Feb 27 2025
address feedback
Feb 19 2025
Feb 17 2025
Feb 16 2025
address feedback
Feb 11 2025
reverted this change. reopening to reintroduce the change
Ah I accidentally landed an older version of this diff
Feb 3 2025
address feedback
Jan 30 2025
Jan 29 2025
fix light mode
address most of the diff feedback