How important is it that your users understand how your service works?
We're working on passwordless authentication which relies heavily on user's trust. We have received (usually indirectly) negative feedback which has berated us for not being transparent about how did.app works.
So, how important is it that your users understand how your service works?
And, for a bonus point, how do you strike a balance between explaining how your invention works without releasing too much IP, letting competitors get away with your IP and at the same time trying to build authentic trust with your users?
Here's our attempt:
https://did.app/articles/how-did-works
It's a plain-speaking article that tries to explain how did.app works without ambiguity but at the same time without overwhelming non-technical readers.
The problem you face that your customers will be somewhat technical people. They need more technical information about how your product works because they mostly do not trust something they don't understand. IP can be described in a way - referring to standard mostly - that is not explicit to re-implement but clear enough to gain trust. Generally speaking, I would not be afraid to go into in-depth details because your IP is worth way less without the trust of your users.
The sentence - "don't trust something they don't understand", that's got to be the essential point here. Thank you.
This comment was deleted 4 years ago