Replying to a6cfa19f...

nostr:npub1psdfxfpxz2cwmmnsk60y3nqpn2tqh9n24h4hstvfkwvr6eaek9js499sr7 nostr:npub1zvc3hhwp38f9lttw4f6948qvtq42vgz3ycewks53dlntcmz0z8gsud4qw0 nostr:npub1wkyrr4pnk5chvzjp4y64fjfu3xtv9c7al4sryyvy9244a5h87s2qur6c6c nostr:npub1rtlcdfujrn5kps54szzffw5txaws38xgfx2m0hp0wtk86nfca3esxnyxal

On that note, can we possibly work out some sort of scaling punishment for UI designers who randomly just move shit around for no goddamn reason in products that we are already extremely familiar with?

I can understand it (somewhat) if there is a reasonable straightforward path, but just swapping around things that worked just fine via forced updates is absolutely infuriating to me.

nostr:npub1fp92ep06wv7h8v0gztvsc3nmsktajelcxyxql6jktdprkawetn3qffwpyl nostr:npub1zvc3hhwp38f9lttw4f6948qvtq42vgz3ycewks53dlntcmz0z8gsud4qw0 nostr:npub1wkyrr4pnk5chvzjp4y64fjfu3xtv9c7al4sryyvy9244a5h87s2qur6c6c nostr:npub1rtlcdfujrn5kps54szzffw5txaws38xgfx2m0hp0wtk86nfca3esxnyxal What I want to see with any application/OS that supports online updates is a radiobutton selector for:

1. Bugfix-only channel (NO UI changes or new features)

2. Stable-UI channel (new features allowed, but need to be switched on by user individually)

3. Active channel (new features and UI changes show up from time to time, enabled by default)

4. Development/test channel (fire-hose of change)

Instead we are given a choice of (3) or (4).

Reply to this note

Please Login to reply.

Discussion

No replies yet.