Schlagwort-Archive: twitter

Features for Twitter for Mac

Twitter’s nati­ve app for Mac OS has been my pri­ma­ry Twit­ter envi­ron­ment for some time now. I used it befo­re it got that ent­i­re­ly new (non­stan­dard) user inter­face. I still like it bet­ter than the other Twit­ter app’s I’ve seen out the­re, but the­re are a few gri­pes with it that I have. 

  • I like to be able to drag apps by taking their top­most ele­ment in the win­dow. I don’t like to see that bit of UI con­ven­ti­on out the door; I don’t like the fact that I have to pick up the Twit­ter win­dow by it’s right-side margin. 
  • I would like the default of pre­sen­ting Twit­ter user­na­mes to indi­ca­te whe­ther I alrea­dy fol­low them or not; this would be espe­cial­ly use­ful on fri­days. May­be give the names two dis­tinct back­ground colours, very light but noti­ca­ble. That way, I could see the over­lap with others, and not have to access each name seperately. 
  • Some­ti­mes, loading images from twit­pic does not work reli­ab­ly, and I have no idea as to why. I have to clo­se the popup and reopen it for the image to load. 
  • Hand­ling blo­cking users is not con­sis­tent: When I am on the “Men­ti­ons” tab and block a user, the tweet I am on disap­pears right away. If I am doing the blo­cking in the user’s pro­fi­le, the tweets of that user remain in my time­li­ne and men­ti­ons. I’d much rather see them disap­pe­ar everywhere. 

But I’m sure they’ll all be addres­sed in later versions. 🙂 

Lessons in customer support

I — pro­bab­ly along with many, many others of the iPho­ne Twit­ter App — dis­co­ve­r­ed some­thing that I con­si­der a bug. As soon as you rota­te the pho­ne, your posi­ti­on in your time­li­ne is utter­ly garbled. Whe­re you are after tur­ning has no resem­blan­ce whatsoever to whe­re you were befo­re. That means: Take the pho­ne, rota­te it, rota­te it back and you’­re at a com­ple­te­ly dif­fe­rent place than before. 

This qui­te goes against the law of least sur­pri­se for the user. So I tried to inform Twit­ter of that bug. I sear­ched for a place for such feed­back, did inde­ed file the report and inclu­ded what I take to be a start on how to resol­ve the issue. I recei­ved an ans­wer from Twit­ter a few days later, but with some­thing that I con­si­der to be com­ple­te­ly bes­i­de the point. The ans­wer, basi­cal­ly was, „If this is a pro­blem for you, you can rota­ti­on-lock your pho­ne.“ Come on, Twit­ter. You can do bet­ter than that. If the mail back had at least inclu­ded some­thing like „Thank you for repor­ting your con­cern, we will look at this intern­al­ly“ or „Thank you, we will con­si­der how to best deal with the issue for a future release,“ all would have been well. But to be told that this is a non-issue is, to be honest, most disap­poin­ting. And yes, I do inde­ed con­si­der this to be a pro­blem. And no, I do not con­si­der rota­ti­on-lock­ng the pho­ne an appro­pria­te solu­ti­on. (I do tend to type on the land­s­cape key­board, but read on the por­trait ori­en­ta­ti­on, so I do in fact qui­te like to chan­ge the direc­tion of the phone.

And it would have been easy to not make me frus­tra­ted about this, too.