Sunday, December 27, 2015

Just in case anybody was wondering: I do not expect 2016 to be the year that most UX stops being horrible.

Random e.g. (not that Fotoxx is anything new to 2016, of course) is the very first thing I see when running Fotoxx for the very first time. And the kicker is I clicked 'Cancel' and while it dismissed the 'Synchronize Files' dialog, it brought up another that said something about how I was doing things wrong.

Monday, December 21, 2015

So I figured out what the root cause of the issues is with Android 5 on the Moto E (2015) I have. In the beginning the whole thing was faster better than most Androids I've had (since I am broke/cheap). But I guess it has gotten slightly more poky over time. So now it is basically thrashing now and then, often & slow enough to eff up the UI and UX. So that swipes don't work, or happen to the wrong thing, etc. Overall there's the rule that anything over, what, 25 msec is basically not interactive, and I guess it has gone over that.

I guess what seems sort of lame to me overall is that Google + Moto haven't actually planned this out together? I understand there's price/cost involved. But why would you design the interaction to be something that literally cannot work out well on the phones you intend to produce?! And that you know full well people are making e.g. the old low-end Hauweis or FoxConns or whatever. It just seems like if you know the low-end cheap shit is part of your entire game plan, you should design the user experience to not turn to kind of hateful shyte when running in those kinds of contexts.

Sunday, December 20, 2015

If you ask me, forced arbitration is evil. Forced arbitration is evil. Forced arbitration is eeeeevil.

What are we going to do about it?

What are you going to do about it?

http://constitution.laws.com/7th-amendment

Friday, December 18, 2015

I'm using an Android 5.x Moto E 2nd gen / 2015. I'm using the Gmail app. When I select text in it (well, when I try to select text, don't get me started...) and then press the "search" magnifying glass icon at the top right of the display, I get a tab/sheet for the search. And it turns out that the sheet doesn't appear in the "show all tabs" / "recent apps" list. At all. Ever. No matter what. As far as I can tell. So once I've lost it by going to some other app, I've lost whatever work I was doing hunting through the web from that search. So, like, that's kind of annoyingly stupid ux?!

While I'm on the subject, I'll mention that the ordering of the tabs/sheets in the recent apps list is not a good UX for me. Several times I've closed the wrong things due to how animations moved tabs around. And the gestalt around "which tab I was just looking at full screen" / which app I was using is not good. For example, if I'm shopping craigslist for a bargain on a sewing machine (real world use case) I open a bunch of tabs. As I try to look at each one, it is hard to know which ones I've already looked at, and which I haven't.

There's a buhzillion other things about Android 5 that drive me batty, too. I'm trying to just let go, let go, let go right now... ;-P

Thursday, December 17, 2015

It seems downright weird to me that I am using Google Chrome and yet all the Google things in the drop-down history menu are pretty much uselessly labeled. Some just say, "Google" with nothing else. Others are raw URLs so it is hard to see/know what they were about.

Wednesday, December 16, 2015

I guess there is some kind of collusion in ecommerce. Because every time I figure I should just boycott any store that has a terrible ux for eshopping, I end up not having *any* store left that I can buy from. How's that for a 1st world problem?

Tuesday, December 15, 2015

Gift giving season is a chance for me to renew my confusion, puzzlement, distaste, frustration, and all 'round hyper extremely filth-curse-word-laden BAH HUMBUG. Why is it as if every, and I mean nigh literally every, eCommerce UI/X is apparently purposefully designed to push me away from buying anything?
Oh, wait! I guess I already am in the particular circle of hell that is full of little snickering terrible usability jabs!
I did a search. I got a Wikipedia hit. I clicked. I went to Wikipedia. They showed a big banner asking for money. I went through the process of giving them money. They put up a "thank you page" ... and now I'm nowhere near the page I actually wanted to see. The page that I was coming to Wikipedia for in the first place. Would it really have been so hard to have redirected me? Could even have been the page with a smaller "thank you" banner in place of the "donate" one.

The kicker? When I go back to the page I want by using the browser history, the banner for donating still shows up.

Monday, December 14, 2015

The way shift-arrow works on selected text regions in old Xcode is like how it works in every other app on earth. Newer Xcodes change it to be really, really weird. And evil. No, sir, I don't like it.

Friday, December 11, 2015

If you search for comp.risks on Google, one of the hits is

https://catless.ncl.ac.uk/Risks/

and on that page if you click

Subscriptions, contributions and archives

then I get a certificate error. If I accept the "bad" certificate once time, then it goes through to a connection failure.

So that's impressive.
 Using the search in Google Play Store, crashes the app on a Moto E (2nd gen), for me, today, at any rate. That sorta seems like a sad thing.

The extra sad thing is that apparently the GPS app has a long history of being sorta crashy?

Of course, the Apple app store on e.g. iOS 5 was also pretty bad and crash at times, too. I just cannot really fathom how you can let such blatant bugs through for the conduit by which you make money?
 
D/AndroidRuntime(25467): Shutting down VM
E/AndroidRuntime(25467): FATAL EXCEPTION: main
E/AndroidRuntime(25467): Process: com.android.vending, PID: 25467
E/AndroidRuntime(25467): java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.google.android.finsky.protos.SearchSuggest$NavSug
gestion.docId' on a null object reference
E/AndroidRuntime(25467):        at com.google.android.finsky.providers.SearchSuggestionFetcherLegacy.getIconUri(SearchSuggestionFetcherLegacy.java:90)
E/AndroidRuntime(25467):        at com.google.android.finsky.providers.SearchSuggestionFetcherLegacy.access$200(SearchSuggestionFetcherLegacy.java:34)
E/AndroidRuntime(25467):        at com.google.android.finsky.providers.SearchSuggestionFetcherLegacy$2.onResponse(SearchSuggestionFetcherLegacy.java:170)
E/AndroidRuntime(25467):        at com.google.android.finsky.providers.SearchSuggestionFetcherLegacy$2.onResponse(SearchSuggestionFetcherLegacy.java:153)
E/AndroidRuntime(25467):        at com.google.android.finsky.api.DfeRequest.deliverResponse(DfeRequest.java:546)
E/AndroidRuntime(25467):        at com.google.android.finsky.api.DfeRequest.deliverResponse(DfeRequest.java:51)
E/AndroidRuntime(25467):        at com.android.volley.ExecutorDelivery$ResponseDeliveryRunnable.run(ExecutorDelivery.java:99)
E/AndroidRuntime(25467):        at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(25467):        at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(25467):        at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(25467):        at android.app.ActivityThread.main(ActivityThread.java:5343)
E/AndroidRuntime(25467):        at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(25467):        at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(25467):        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:905)
E/AndroidRuntime(25467):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:700)
W/ActivityManager(  812):   Force finishing activity 1 com.android.vending/.AssetBrowserActivity

Thursday, December 10, 2015

"The authorization systems we depend on to keep everything secure just cannot be understood by humans." It is to weep.
I have yet to come across a UX for managing software updates that isn't blatantly full of rather sadly bad emergent properties.

Monday, December 7, 2015

"Jeffries: In a way, the point of the book is that the things we can measure are not the things of value."
"Jeffries: Value is what you want. Features are the bits that deliver value. Feature teams build complete features. When you use feature teams, everyone builds features. Features are what deliver value. Value is what you want. That’s really all there is to it: any other organization of the work puts more levels and more stages between you, and what you want."
Web based productivity tools seems to often be a bit of a lie to me. Right now I'm waiting for Chrome on a powerful MacBook Pro to stop spinning the "I'm wedged" colorful beachball spinner, so I can keep working on the Google Docs I have open. No indication of what is causing the lock up. Probably no hint even if/after it ever comes back.
it really is greenhouse gases. from us.

http://www.bloomberg.com/graphics/2015-whats-warming-the-world/
It always amazes me when I hear about how bad company job application systems are. Why would you make the UX so bad that people turn away from the job, and even the entire company? I guess the theory is "WELL, if people REALLY wanted to work here, they'd walk uphill both ways through bad UX just to get here!" Somehow that just doesn't compute for me.
I sometimes do wish all apps that had user photos gave me a way to turn off all the user photos.

Wednesday, December 2, 2015

There has very rarely been an e-commerce experience of any sort that I've ever had, that wasn't somehow blatantly a UX train wreck. I just do not understand how the world can be run by the kind of people who make these kinds of decisions. I also cannot understand how/why the buying public doesn't boycott all these utterly horrible things and companies. The way I see it, e-commerce should pretty much have tanked capitalism by now.

Tuesday, December 1, 2015

I am very much a fan of advanced static typing; and purity, immutability, referential transparency, linearity, etc.

"Please note that data is returned by reference, this means that modifications to returned objects may change the database. To avoid such behaviour, you need to use .cloneDeep()."

(So I guess I really should be diving whole-hog into, like, Rust?)
Given that some filesystems do not use "/" as their directory separator, I would generally like APIs to filesystems to not deal in strings for paths. Rather arrays of strings. And not really arrays of strings, but arrays of pathname's or somesuch. That way I never have to worry about knowing what magical characters to have to escape or unescape. I hope.
So I tried to actually buy something on Cyber Monday. Target, Khols, Macys, etc., were all a living hell of usability and ux. I just don't grok how these things can be considered okay.