Friday, January 2, 2015

navigation - Different look and feel between administration and end user experience?


Lets say we have an app that performs something like surveys. There are two primary types of users, administrative users who set up and build the surveys, (who are actually the customers), and the 'public' users being surved, who will also have accounts and profiles.


Here is my question. Considering how few views exist on the public end, and how different the function; is it appropriate to have a mildly different look and feel from the administrative areas? What kinds of value does this visual shift between the experiences hold?


Or should the two kinds of users get the same basic look and feel? Is there value to the two ends being visually consistent?



I caught myself preparing to go through the extra work of making a different look and feel for the public, but then realized there a good arguments on either side.




usability - Swipe specific keyboard?


QWERTY was used to prevent the arms of a typewriter from clashing. DVORAK is made for productivity (~70% of the typing on the homerow)


If you use a swipe keyboard (as available on android 4.2?, swype app and similar) what would be the best layout theoraticaly? Dvorak would misinterpret a lot i'd guess if you only swipe back and forth on one row.



Answer



From a user experience point of view inputting information would be easiest, if the most used keys are in close proximity, and common keyboard combinations are next to each other.


While the DVORAK layout is efficient for typing with ten fingers that lay on the home key row and thus have fast access to the most commonly used letters, the same logic does not apply for swipe keyboard input, where you have one pointer. In fact, having all the most commonly used letters in a row might be counter productive in this case, because users would have to constantly slide left and right with constraint to one dimension, which actually makes longer movement paths.


Ideally, the most used keys would situate in the center area of the keyboard, allowing for little movement for the most common letters and detouring to the sides for the less frequently used letters.


The way swipe keyboards work, technically, is by comparing movement end points to possible words, under consideration of letters that were swiped over between corner points. In this light, the way QWERTY distributes the keys to left and right hand actually helps making words and the letters they constituate of more identifyable, because their movements are more characteristic. Clustering all the heavily used letters in the center area might thus backfire from a technical point of view, because it makes words less identifiable as less "zig-zags" movement happens.


With these two extremes, users' ease of input on the one hand and technical ease of word detection on the other hand, only thorough testing can reveal which would be the most efficient layout. My wager is, however, that it's those two extremes that dictate the framework. I doubt that DVORAK is actually a good fit with regards to both, usability and technical compability.


Thursday, January 1, 2015

gui design - Good reasons to use bad UI


When should we make a conscious decision to retain poor UI, even if temporarily? Not because of budget or time constraints but because of what I call the QWERTY paradox.


In short, the QWERTY paradox is that users have a better experience with a poor interface than with any of its contenders because it's been so widely learned.



QWERTY Paradox: The letters on a QWERTY keyboard were originally arranged to prevent typewriter typepresses from jamming. Of course, this is a not an issue today and the arrangement of the letters are actually rather inefficient.


There are several more efficient layouts for keyboards which have been around for a while such as the Dvorak keyboard. However, a good computer designer with a passion for usability ought to ship a keyboard with a QWERTY rather than a Dvorak keyboard.



The former has been used so often, users are much more efficient with the convention of QWERTY than with the unfamiliarity with Dvorak.



So my question is, On what criteria should we opt to retain bad UI to keep our UX pleasant (paradoxically)?


UPDATE


I think the point of the QWERTY paradox may have been lost. Essentially it's this:



The gain from an improvement can be significantly less than the friction from migrating to it.




Answer



Only when a change would be absolutely earth shattering. Changing the standard keyboard layout would mean hundreds of millions of people can't type any more. It's a change that affects the majority of keyboard users the world over at this point.



It might seem like this is a good reason to not change things when the change is disruptive, but it's really not. Most changes people can get used to over minutes or days. The problem with keyboards is that these are physical devices that can not feasibly be replaced. If you change keyboards, hundreds of millions of the old ones are still out there. There's no reason to change. You can't force the change.


In the digital space, change is almost always possible; Windows Vista made a great deal of people freak out, and the Word 2007 Ribbon confuses new users to this day, but you can adapt to them (especially due to the significant UI improvements in Windows 7 and Word 2010).


If you can force a change, people will get over it. You better have a good reason to force the change, as there will be short-term consequences, but if research really does indicates performance improvements, the change should be made. Allegedly Microsoft did find significant evidence supporting the Ribbon, hence their change.


The reason you really need to force a change is the longer a problem remains, the bigger a problem it becomes. Changing keyboards would have been easier in the 70s. If computers used different keyboards than typewriters it would have been a little annoying at first, but keyboard penetration was small. Now the level of inertia is almost completely insurmountable.


Change Fast when research supports it. The digital space has a lot more room for change than the physical one for many reasons, which is why you need to be sure physical things work before you distribute them.


sharpe ratio - Forget Kelly, forget fractional sizing. Where is the general theory?


I am struggling to find a general theory of position sizing. Help!


The literature is all about fractional position sizing, but that's just one of the innumerable strategies. What about all the other sizing strategies?


The problem:



  • Suppose I have a daily trading strategy that generates a daily return $r_i \sim N[\mu,\sigma^2]$

  • I start with capital $x_0$ and run my strategy once a day, for 1 year


  • each day I begin with the previous day's capital $x_{i-1}$ and I risk an amount $y_i=f(x_{i-1})$

  • at the end of the year, I end up with a capital $x_n \ge 0$


Let's look at common metrics:



  • $R=(x_n-x_0)/x_0$ the yearly return on investment

  • $\mu_R=E[R] =$ the yearly return expectation

  • $\sigma_R^2=\text{VAR}[R] =$ the yearly return variance

  • $Ϛ_R=\frac {\mu_R} {\sigma_R} = $ the Sharpe Ratio



Questions:



  • what utility function $U(R)$ would a risk-averse investor optimise?

  • what is the best trade sizing function $f(x_i)$ that optimises $U(R)$ ?


An example:



  • let's pick the Sharpe Ratio as utility function, so $U(R)=Ϛ_R$

  • let's explore how different trade sizing functions yield different utility



enter image description here




  • so function "B" in the chart corresponds to fractional trade sizing, while function "D" corresponds to constant trade sizing. The others two functions are less common, I picked them arbitrarily.




  • besides being different functions, each function has a tuning parameter $\theta$. As an example, for function "B", $\theta$ is the % of my current capital I risk at each trade. That is $y_i=f(x_{i-1})=\theta x_{i-1}$




  • I simulated 1M runs of each trade sizing function, also varying the tuning parameter $\theta$ between $0$ and $1$





  • the various trade sizing functions yield a very different Sharpe Ratio, and -somewhat surprisingly- fractional trade sizing is the worst! (see red curve below)




  • in the chart below are the results for daily return $\mu=1, \sigma=20$. But the differences in performance remain similar when I change $\mu$ and $\sigma$.




enter image description here


More questions:





  • why is everyone talking about fractional trade sizing, if it shows such a bad Sharpe Ratio?




  • did anyone study the problem more generally, instead of just trying arbitrary trade sizing functions, like I did in my empirical study?




Your opinion is welcome, thank you!




website design - Is it a good idea to have a large footer containing many links?


In recent years, it's become quite a common design pattern to have a large footer on every page, containing a 'mini sitemap'.


For example:


enter image description here


This has supposed SEO benefits but would also seem to be a legitimate use of page estate. However, such footers contain many, many links, and I'm wondering if that's a hindrance to screen readers and/or keyboard users.


Any thoughts?




html - Is there a convention for distinguishing internal and external links in a website?


From a user point of view, I think it is a reasonable idea to distinguish internal and external links. By internal links, I mean links that have the same domain name than the website displaying the link, and by external links, links that goes elsewhere.



To take an example, wikipedia distinguished external links with this small icon after the link: link icon


I have the following questions: is it considered a good practice to make this distinction ? And what are the more common ways to do it ?




adobe photoshop - How can I achieve colour overlay effect in PS?


enter image description here


I am trying to achieve the color overlay effect on a image. I have tried Gradient Map, black and white, a new layer with fill color and reduced opacity. But none are giving the best result. What will be the best way to achieve this effect?




technique - How credible is wikipedia?

I understand that this question relates more to wikipedia than it does writing but... If I was going to use wikipedia for a source for a res...