What do you do if after 8 years of development your data looks like this?
- Do you try to remove the features that aren’t getting used much? Do you keep adding more features?
- What if supporting all these features you added means your ability to make fixes/changes is getting slower & slower?
- What if there’s loyal (and loud) existing users who love & use some of the most rarely used features you added over the years?
Welcome to software development.
- Do you try to remove the features that aren’t getting used much? Do you keep adding more features?
- What if supporting all these features you added means your ability to make fixes/changes is getting slower & slower?
- What if there’s loyal (and loud) existing users who love & use some of the most rarely used features you added over the years?
Welcome to software development.
View 20 previous comments
Hello +Luke Wroblewski
This is a very very interesting issue and I hear it well.
On my sight, this is NOT a technical issue that can be solved by numbers. It's a question that concerns ethics, sociology or even politics. And we've learnt to fear the democratic rule of majority because it's not inclusive and it lets people aside.
I know I would be very bad in your situation because my strongest reaction is to hold things still. And now, I admire youths that are able to take the decisions for change. But they loose my faith if they cannot prove me I was wrong, that is, if the result of the change is not better than before.
Note that I'm not talking
in theory. I'm close to the developer of the "Black Menu" extension for Chrome. He made changes I was not for that revealed to be very good at the end.
The usual solution in your case, is to build a beta version (of course, you did). But you need to prove to everyone that the new version is better than the previous, not only technically but by the ease to reach the users' purpose.Jul 16, 2016
The point is not whether you implement new stuff to make it better and you remove some features after years. It's about the period of time. If you keep changing things you changed a few months or a year ago it's getting chaotic. The secret in all this is to have a vision and to improve things in a sustained way. Your work becomes implausible if you remove and change things permanently. The reflection of a good design is noticeable if the design you created is futureproof.
So, this is my thought regarding G+. You had many things in the old G+ that were good and many things you had to improve or to make little adjustments at least. A few months ago you started with a naked preview. But the most favored things ppl. requested are still not implemented AND it seems to me that your priorities are wrong.
Next example: Who had the idea regarding the style of our profiles with this pop-up window? From a web-design perspective this is absolutely terrible. Instead of keeping the information on the website itself you make them pop-out, and further more unclear because the user has to scroll miles down to the bottom of this pop-out page. But these are design concerns and I'm sure that the responsible ppl. for design made the wrong choices in this case.
One more thing: The bottom bar and the posting bar (or however it's called) on nearly every screen. I doubt that the community sent you a bunch of feedback like: "Hey guys, it would be awesome if you implement a bottom bar and a bar additional to the FAB to make posts." Errrmm...what on earth? This was never ever suggested by the community and you still implemented those unnecessary "features". So, if you would have listened to the community, you would be nearly done after over a half year of working on G+ and, besides, the functionality would be better than it is atm. Working on the right thing makes it easier regarding the work-flow instead of working on wrong things ppl. never asked for. Working on wrong tasks also cause new work because the things that have been implemented have to be adjusted...
However, I hope you are going to listen more to the good feedback and at least, you are capable to know, what good feedback is. ;-)Jul 18, 2016- +Eddi Szilard So true!!Jul 18, 2016
- +François Bacconnet Thanks mate. This had to be said.Jul 18, 2016
Is there only 1.6% users switching front/rear camera? It should be much more, shouldn't it?Jul 26, 2016- +Hiệp Lê tuấn
it's not the number of users (probably every user has switched once in a lifetime, so 100%) but the number of situations when you do that is 1.6% - as far as I understand. Most of the time you just take regular photos not selfies. Even if you can see the crazy selfie-type tourists everywhere, they quickly take plenty of regular pictures, too.Aug 30, 2016 
Aumg19w
Add a comment...