Open zhangzhongnan928 opened 2 years ago
We should go with one name and scrap the other to avoid confusion. Let's just go with Brand Connector
We should go with one name and scrap the other to avoid confusion. Let's just go with Brand Connector
My concern is Brand Connector is a good name for businesses and consumers, but may not be good for developers.
We should go with one name and scrap the other to avoid confusion. Let's just go with Brand Connector
My concern is Brand Connector is a good name for businesses and consumers, but may not be good for developers.
The challenge i have seen, is that we refer to the product with 2 different names (sometimes in the same conversation). My view is that we should reduce this confusion. Maybe Brand Connector is not the right word for developers. Maybe it is Token Negotiator or (new idea) we call it Token Connector for developers so that it is closer to Brand Connector
I am not 100% sure what is best to be honest.
We will start sharing the examples with people who want to integrate Devcon ticket attestation. We should use the name Brand Connector instead of Token Negotiator, or use "Brand Connector (Token Negotiator)" to have both names.