Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Software Updates -> How To Get It Right? #14

Open
nelsonic opened this issue Nov 8, 2019 · 2 comments
Open

Software Updates -> How To Get It Right? #14

nelsonic opened this issue Nov 8, 2019 · 2 comments
Labels
discuss Share your constructive thoughts on how to make progress with this issue epic A feature idea that is large enough to require a sprint (5 days) or more and has smaller sub-issues. help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies

Comments

@nelsonic
Copy link
Member

nelsonic commented Nov 8, 2019

https://xkcd.com/2224
image
The Abyss indeed ... 😞
The number of times where Devs have broken perfectly working Apps with "updates" is mind-blowing!
Thread of people complaining about forced updates: https://news.ycombinator.com/item?id=21480590

How do we avoid this situation?
@nelsonic nelsonic added help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue epic A feature idea that is large enough to require a sprint (5 days) or more and has smaller sub-issues. discuss Share your constructive thoughts on how to make progress with this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies labels Nov 8, 2019
@nelsonic
Copy link
Member Author

nelsonic commented Nov 21, 2019 •
edited
Loading

The recent introduction of the WYSIWYG input box in Slack is a great example of a "forced" UI/UX update going wrong. https://quuxplusone.github.io/blog/2019/11/20/slack-rich-text-box

The discussion of how terrible it is made it to the_top_ of HN this morning:
slack-wysiwyg-editor-fail
https://news.ycombinator.com/item?id=21589647

You'd have thought that a company that makes one product and is worth $11Bn would have figured out how to implement "feature flags" to avoid forcing a feature on users who don't want/need it ... 💭

I firmly believe that "Progressive UI" is going to be our "secret sauce" that differentiates us from similar apps.

Long read: https://www.vice.com/en_us/article/pa7nbn/slacks-new-rich-text-editor-shows-why-markdown-still-scares-people

@nelsonic
Copy link
Member Author

GitHub are going to force everyone to use the more complex UI from next month:
github-notifications-replacing-interface

https://github.blog/2020-02-25-your-new-web-notifications-experience-is-here/
github-notifications-forced-update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discuss Share your constructive thoughts on how to make progress with this issue epic A feature idea that is large enough to require a sprint (5 days) or more and has smaller sub-issues. help wanted If you can help make progress with this issue, please comment! question A question needs to be answered before progress can be made on this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nelsonic