-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use case 1 is too broadly scoped by its headline #3
Comments
I don't want to open an issue just for that, so forgive the slight sidetrack but I think it fits well in here: Maybe explain the term VC at least once. It took me quite a while. 😉 |
This comment is fine as a proposed clarification, but I don't see this as a reasonable issue to raise as a blocker for adoption. |
Use cases determine the scope of the problems we're adopting to solve, so this seems relevant. |
Please see the discussion's conclusion here. |
"Cross-app communication" is a means to an end, not a use case.
A descriptive headline of the use case presented would be: “User drives a captured presentation app from a VC app”.
This is important for scope.
The text was updated successfully, but these errors were encountered: