Regarding ‘secret’ UI components

I want to jump back a couple years to something Loren Brichter said in reference to his pull-to-refresh UI and, specifically, the swipe-to-reveal tweet actions. This remains one of my most consistently referred to explanations when it comes to ultra-functional UI.

Now, I think you can split gestures into two categories. One is of the pull-down-to-refresh kind. These are gestures that are discoverable and explanatory. The other kind of gestures are like tapping-the-status-bar-to-scroll-to-the-top, or swipe-to-delete (or swipe-to-reply in Tweetie). These gestures you won’t discover on your own except by accident. These are not discoverable, and they are not explanatory.

This second class of gestures can exist (in my opinion) because they are not the only way to accomplish a goal. In the case of tapping the status bar, users already know how to scroll to the top manually. It’s slower, but it’s possible. In the case of swipe to delete, users already know they can tap on a message and then tap the trash button. So knowing the gesture isn’t necessary.

So when you’re inventing new gestures, it’s important to think about whether the gesture is required to use the app. If it’s the only way to accomplish a goal, you better be sure it’s discoverable and explanatory without needing to read a manual. If it’s the other kind of gesture, go nuts!

From Twitter Reloaded: an interview with Loren Brichter

Custom, front-end user settings page in WordPress

I find as I learn more and more on WordPress as a CMS, the requirement to keep users out of the WordPress dashboard altogether becomes increasingly common. The issue with prohibiting such access is, a user’s settings are normally handled through a dashboard view. In search of a solution, I found two routes:

1. Theme My Login, a plugin, handles this among many other things Its placement in the permalink structure of the page is not ideal, however, but it’s worth a shot.
2. On the WordPress.org forums, I eventually encountered this post by jimzqui. Using a custom template and a lot of additional CSS, this code is the shit to get a front-end settings page going. You’ll probably encounter an error – make sure you remove the ‘Resume’ field in his code, as chances are you don’t have one.