A few thoughts immediately come to mind: 1) No pain point.
A few thoughts immediately come to mind: 1) No pain point. The project has a gee-whiz, neato factor to it. While it would be cool to have this level of automation there's no strong need or urge to have it. The thing is mini-blinds suck. The cords get tangled. One side almost always gets stuck when rolling up/down. If your product addressed this pain point and you tied the automation feature to taking the suck out of mini-blinds that might gain more traction. Instead of having to fumble with cords, just press a button. 2) Where's your team? Is it just you taking care of everything? Product design, product testing, order fulfillment, press releases/management, manufacture - all of these are major tasks. It's seems like a herculean effort for one guy. And makes me hesitant that there will be a final, shippable product.
Posted by leepowers on Jun 16, 2014, 10:42 PM
Tags
Related issues
- Huh, this is not my experience.
- For some reason an Azure outage does not faze me in the same way that an AWS outage does.
- The triplet of wind, pole, dragon appears multiple times in the same order, so is possibly a single phrase that has been broken up into t...
- Option to skip refreshing resource instances whose configuration hasn't changed since the last apply
- [YouTube] Unable to extract uploader id
- Add ability to prioritize GitHub Action runners
Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments
reliability (E-commerce)
Huh, this is not my experience.
For some reason an Azure outage does not faze me in the same way that an AWS outage does.
The triplet of wind, pole, dragon appears multiple times in the same order, so is possibly a single phrase that has been broken up into t...
Option to skip refreshing resource instances whose configuration hasn't changed since the last apply
[YouTube] Unable to extract uploader id
Add ability to prioritize GitHub Action runners
Microsoft Flight Simulator (2020) (1250410)
Codegen collaboration with Apollo Codegen and GraphQL Code Generator
A few thoughts immediately come to mind: 1) No pain point.
A few thoughts immediately come to mind: 1) No pain point. The project has a gee-whiz, neato factor to it. While it would be cool to have this level of automation there's no strong need or urge to have it. The thing is mini-blinds suck. The cords get tangled. One side almost always gets stuck when rolling up/down. If your product addressed this pain point and you tied the automation feature to taking the suck out of mini-blinds that might gain more traction. Instead of having to fumble with cords, just press a button. 2) Where's your team? Is it just you taking care of everything? Product design, product testing, order fulfillment, press releases/management, manufacture - all of these are major tasks. It's seems like a herculean effort for one guy. And makes me hesitant that there will be a final, shippable product.
Comments (0)
No comments yet. Start the discussion.