-
Notifications
You must be signed in to change notification settings - Fork 2
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
Suggestions for the minimum viable unit? #2
Comments
I don't think there will really be a concept of a minimum viable concept/unit/product. We'll just have to begin with the foundations and see where it ends up. Initially I see:
|
Broadly speaking, I agree with what you've just written, but I think such a product needs to gain visibility and traction in order to gather both users and more collaborators. Also, we need not to get discouraged and the endeavour itself it's not small. I am a fan of the "divide and conquer" strategy when it comes to make things, and maybe instead of "minimum viable unit" I should have said "first milestone" or "release 0.1". Something to show the world that Yip is not only a brilliant concept, but something that can be used right here right now. If we set the hefty lot as minimum goal, we'll end up like some startups that wait way too long for the first release and risk losing relevance or interest even before they're really born. |
I like the idea of developing the whole through a number of smaller modules/sub-units -- but I don't know if these modules will be usable in themselves by the mass public. Do you have any examples of sub-units that can be released separately? Tbh, my feeling is that the concept is still insufficiently built up to be broken down into individual pieces yet. |
(* to report events? to browse events?)
The text was updated successfully, but these errors were encountered: