This issue describes an improvement to an existing feature.
This issue is descriptive and declarative, but not imperative. It describes the end goal but does not prescribe actions.
This issue is not a duplicate.
Details
Describe the improvement.
For the "Message" button on each card, keep the exact same functionality but have the button be a grey color if they have an EMTPY value for handle in the database.
Describe the use case.
The UX of "Message" when 95% of apps aren't connected to message yet is bad.
So on the home page, XMTP, Lens, and Lenstube will be green to message. This is a pretty clear call to action for apps to get connected with us. And if they click the grey button, they get the same-as-current functionality to message with relaycc.eth in Receiver.
killthebuddh4
commented
1 year ago 
Guidelines
Details
Describe the improvement.
For the "Message" button on each card, keep the exact same functionality but have the button be a grey color if they have an EMTPY value for handle in the database.
Describe the use case.
The UX of "Message" when 95% of apps aren't connected to message yet is bad.
So on the home page, XMTP, Lens, and Lenstube will be green to message. This is a pretty clear call to action for apps to get connected with us. And if they click the grey button, they get the same-as-current functionality to message with relaycc.eth in Receiver.
Describe alternatives you've considered.
Development
Background Information
Product Definition
Functional Spec
UI Prototype
Technical Primer