http://nospronos.com/en/a-few-questions
But again it was skewed towards the people ready to take time to answser so the answser were mainly very enthusiastic which I know now doesn't represent the majority of the users
http://nospronos.com/en/a-few-questions
But again it was skewed towards the people ready to take time to answser so the answser were mainly very enthusiastic which I know now doesn't represent the majority of the users
Power users are a mixed blessing.
Pros: they give you many ideas what to do. Often they're your best word-of-mouth evangelists.
Cons: If you take their requests too literally, they can drive the product/service into becoming something with too-narrow appeal and poor learnability. (However, if you don't listen to them, enough, they get mad and maybe you lose their evangelism, or worse it turns into anti-evangelism.)
Realistically: The early-adopter power-users will want their new features relatively quickly. It takes significant discipline and foresight to add them in a way that won't complicate and compromise the simpler experience. Yes you can hide options, etc., but eventually the complexity can start poking through.
Of course that's just my experience as a developer and user of many programs; you may be smarter and/or luckier than me.