sjhcockrell

That's my take, too--it would be infinitely more useful in a work environment.

I can imagine how having a HUD could be useful while programming, even though I have two screens in front of me already.

I can also imagine how it would make certain elements of interacting with people working remotely--like seeing what someone's doing, whether it's programming in a terminal or sketching on a pad--so much easier.

That said, it'd definitely stay in an office drawer after-hours.

The thing that's most surprising to me is that their design team seems to have lost a lot of key staff recently--and it's not a huge team right now.[1]

Mari Sheibley's work was a huge part of defining the culture/visual tone of 4sq early on. Interesting to see where they go from here.

[1]:http://techcrunch.com/2012/11/27/ex-foursquare-designers-foc...

It's most definitely in the "tech to solve human problems" camp.

Interesting to hear that you feel more stressed when you lock yourself out of palette cleansing sites. For me, I sometimes get this background anxiety/agitation when working in front of a computer for long periods of time, which can tip me into distraction when I hit something frustrating.

My computer is a shared leisure/work machine, which means that it can fall into the "working in the bedroom effect:" I find that I don't work well in that space because it's where I sleep and relax at the end of a day.

I create a boundary between relaxing/working states by changing environment: going to a coffee shop, office, or another room.

For some reason, this script has a similar boundary/environment effect on me: an intentional step to create a different "space" where I am working.

Yup, that's a bug. Thanks for looking through the code!

Now I need to figure out why it seemed to work in the first place.

I'm in this camp--if I'm working on something in a browser and I get bored, my reflex is to open a new tab and do HN or reddit before I know what I'm doing.

Did a combination of Chrome/Safari nanny plugins for a while, but the effort of `sudo` + password seems to be working better and is a bit easier to turn on/off for me.

I haven't actually; I do know there's a number of these scripts out there, though.

I'll take a look, thanks for the suggestion!

The fragmentation is fairly significant, given that 85% of current Android devices are still running 2.2-2.3.x versions of the Android OS--both of which are now 2 years old.[1]

Four months ago, we were experimenting with a combination of PhoneGap and mobile website versions of an app, and that was an unholy nightmare of bugs--not because of the version of Android, but because of the custom UI that phone manufacturers added on top of the stock OS.

We got three different Android devices (running 2.2, 2.3, and 4.1), and debugging for presentation, rendering, and behavioral issues was pretty painful. Two bugs that I can recall off the top of my head are:

* the "HTC Duplicate Input Bug", where the browser inserted a second <input> or <textarea> element on top of the original element in the DOM when you apply focus to a text input element and bring up the soft keyboard

* issues with heavy caching and cookie management that resulted in failed logins (depending on the user's device) and unpredictable rollout of new versions of CSS and JS

The problem with Android fragmentation is not necessarily that it's spread across the number of devices and versions; it's that the phone manufacturers have incentives to continue using legacy versions of the software (2.2-2.3x) because they have already invested time and resources into building their proprietary UI on top of them.

[1]: http://developer.android.com/resources/dashboard/platform-ve...