Loading Profile...
CHAMP
Public Development Roadmap
Is there a page/wiki that will show us what sort of new features and plans you have for Echo going forward. Mozilla do a very good one for Firefox and I'm sure a lot of us would love to see an outline of things you have planned for the product.
I’m happy
8
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
The best point from the company
-
This is a very interesting notion
There are a number of considerations with pulling it off
1. While broad themes/goals for our roadmap are set, week to week features are usually driven by customer demand and our own sense of priority in the rapidly changing landscape of blogs and social networking. So we might certainly be able to post broad goals/themes we could not really post specific features more than a couple of weeks ahead of time.
2. We would certainly put our competitive advantage at risk if we telegraphed our moves but we could also make customers much more comfortable with our goals and outcomes. It's a very interesting trade off.
3. Maintaining a public/sanitized list day-to-day when we are working full time maintaining our own internal road-maps and lists could be quite difficult.
I personally love transparency in all forms and I've not seen a closed source company pull this off before.
As you state Mozilla seems to do it fine despite competing heavily with other major browser vendors. We certainly give many tier1 publishers, advisers and friends heads up on upcoming features, but this broader approach would be quite different/innovative.
If we were able to get real traction around this idea I would certainly be open to doing it.
It is, like all things, a question of ROI.
I'd be interested in hearing what others in the community think of this.
I’m excited
The company thinks
this is one of the best points
-
Inappropriate?Thank you for this feature idea! I've passed it onto our product team for consideration.
1 person thinks
this is one of the best points
-
Inappropriate?Thanks Igor, appreciate it.
-
Inappropriate?Ah! You want to get inside our minds :-)) Maybe it's not as pretty as it may seem from outside! or maybe it is a world of vision and inspiration :-))
Will discuss internally what we can do ;-)
1 Comment Add a comment
This is one of the best points
-
Ha lol :) Just a little insight into what the plans are, I know there is a very competitive comments market out there currently so we would not want you to give away any secrets on new features that your competitors don't have but just on the general stuff. -
Inappropriate?This is a very interesting notion
There are a number of considerations with pulling it off
1. While broad themes/goals for our roadmap are set, week to week features are usually driven by customer demand and our own sense of priority in the rapidly changing landscape of blogs and social networking. So we might certainly be able to post broad goals/themes we could not really post specific features more than a couple of weeks ahead of time.
2. We would certainly put our competitive advantage at risk if we telegraphed our moves but we could also make customers much more comfortable with our goals and outcomes. It's a very interesting trade off.
3. Maintaining a public/sanitized list day-to-day when we are working full time maintaining our own internal road-maps and lists could be quite difficult.
I personally love transparency in all forms and I've not seen a closed source company pull this off before.
As you state Mozilla seems to do it fine despite competing heavily with other major browser vendors. We certainly give many tier1 publishers, advisers and friends heads up on upcoming features, but this broader approach would be quite different/innovative.
If we were able to get real traction around this idea I would certainly be open to doing it.
It is, like all things, a question of ROI.
I'd be interested in hearing what others in the community think of this.
I’m excited
The company thinks
this is one of the best points
-
Inappropriate?Thanks Chris, that's a great reply and I quite understand every point.
Could people, like me, sign up to a NDA or something similar to get on this tier 1/publishes list for heads up on new features?
I’m excited
-
Inappropriate?As a publisher using Echo I'd love to see the broad and high level goal roadmap. I think there is also room to disclosure when bugs and upgrades are planned to be pushed out.
Understandably you can't publish too much because of competition and resources.
I’m happy
1 person thinks
this is one of the best points
-
Inappropriate?Maybe a NDA is overkill - but creating a developers network requiring registration and agreement to a terms of use policy would accomplish 2 things:
First, it would separate a lot of technical type of material from the casual user - thus [hopefully] preventing the casual user from getting a) overwhelemd, b) confused and c) ticked off if JS decides to change direction and not implemet something.
Second, it would at least allow JS to know who it is that has access to the general information that JS is willing to share at any given time.
just a thought...
- m
I’m intrigued
1 person thinks
this is one of the best points
-
Inappropriate?I like the idea of how Feedly presents a live overview of feature requests; containing links to the discussions about them on GetSatisfaction.
http://blog.feedly.com/2008/12/13/fee...
I’m excited
1 Comment Add a comment
This is one of the best points
-
That is exactly the sort of thing :)
-
EMPLOYEE
EMPLOYEE
EMPLOYEE
CHAMP
CHAMP
