Category Archives: Software

What does this app do?

Posted on by

Yesterday, after a productive afternoon of hackery I came across this interesting exclamation on Twitter:

While I sympathized with Mr. Balkan’s general point, I couldn’t help but see (and partially agree with) the article author’s point of view. Here’s the gist of the matter: popular blogger John Gruber has teamed up with developer Brent Simmons, and designer Dave Wiskus to launch a note-taking app called Vesper.

What does Vesper do? Apparently not much. It lets you take text or photo notes, tag them and share them via email or iMessage. The Verge, Macworld and GigaOm all have their own articles about it if you’re more interested. Macstories even has an interview with the creators. Its biggest selling points seem to be good design and John Gruber’s involvement.

I have no qualms with paying for software – I use OmniFocus as a task manager, I bought the Android and iOS versions of Instapaper and I paid for the Pinboard bookmarking service. All of them do useful things for me and do them well (better than most other apps and services in the same category). So what exactly would I be paying for if I bought Vesper? According to Marco Arment (of Tumblr and Instapaper fame) I’m paying for balls. Apparently the apps creators are extremely brave for releasing a feature-light app that’s about the same as a bunch of other apps while being comparatively more expensive (and having a mildly interesting Credits section).

Perhaps they are. But here’s the thing: I don’t care.

I don’t care how heroic Gruber and Co. are. I don’t really care that the app is $4.99. I do appreciate that the app looks well-designed and the interactions are well thought out. But I care more that the app doesn’t do very much and for some reason, I’m supposed to celebrate that. Apparently being “skillfully crafted” means that things I’m starting to take for granted (like oh.. I don’t know… simple export) are suddenly “power user features”. Somehow we’ve gotten to the point where the developer’s balls are more important than the app’s functionality and data loss is just as much of a problem as typos in the credits.

How did we get to this point and does it matter? I’m not sure. Perhaps it has something to do with the rise of The Cult of Design Dictatorship. I care about good design as much as the next guy and I’m glad that a small group of people can create and distribute widely used products. But when it comes to technology, I refuse to put form above function and I definitely won’t allow the developer’s pedigree to be a stand-in for functionality.

A week with the Nexus 4

Posted on by

I bought my first smartphone about a year and a half ago. It was the straight-from-Google version of the Samsung Nexus S, meaning that it came without any carrier-installed crapware and no contract. However, it was already over a year old and a generation behind the times when I got it. That meant that it was already slower than the current state of art and came with the older Android 2.2 (which I upgraded a few months later to Ice Cream Sandwich). Overall it was a good phone, but has been gradually showing it’s age. It was having trouble using newer apps and the upgrade to Ice Cream Sandwich had been awkward enough that I didn’t even try to update it to Jelly Bean. I had been using T-mobile as my carrier and though I had one of their contract-free prepaid Monthly4G plans, I had carelessly bought the version of the phone with the wrong radio chipset, meaning I only got EDGE service most of the time.

The thought to upgrade to a new phone had been at the back of my mind for a few months. But the announcement of the Galaxy S4 as Google’s next flagship device made me take a look at the available options. While the S4 looks great, I wasn’t about to shell out $650 for a new phone. However, it turned out that the current flagship phone — the Nexus 4 — is available for $350 and it’s only a few months old. It was available unlocked and a quick search of the Intertubes suggested that it worked well on T-mobile’s network.

Google Nexus 4

The Google Nexus 4

The Nexus 4 is a good, solid device and is definitely a big step up from the Nexus S. The 1280 x 768,  4.7-inch display looks great, it’s slimmer and the 8MP camera is a much better than what the Nexus S. It also comes with Android 4.2 (Jelly Bean) and is fast enough to run heavy duty modern apps without skipping a beat. It doesn’t have LTE, but on T-Mobile’s HSPA+ network the speeds I do get are more than sufficient for my needs. The battery life is better than what I’m used to — I can generally end a busy day with about 15-20% to spare. Admittedly, I don’t stream a lot of video or upload lots of photos, so your mileage will probably vary.

On my Nexus S I rarely installed apps and never really explored the Android ecosystem (or rather, the Google Play store). But with a newer phone with an up-to-date version of Android, it was time to go exploring. I was pleasantly surprised to find that Android apps seem to be developing a UI style that is quite different from the iOS counterparts (though not quite as different as Windows Phone). Apps from both large companies (such as Twitter) and smaller operations (like Astrid) sport a sharp, clean and mostly gradient-free design that I personally feel pretty refreshing. I also really like the Google+ app, though I can’t say I use it all that much and I’m looking forward to the new Gmail app. If you need more evidence that Android apps can be just as good looking as their counterparts on other platforms, check out Android Niceties. Sharing between applications and services is also so much nicer and painless than on iOS, though there are some bad apples (I’m looking at you, Feedly).

There are a few quibbles I have about the Nexus 4, but they’re not major and definitely not show-stoppers. For starters, the back of the phone is glass, not plastic or metal. I don’t have a history of breaking screens, but I will sometimes put down my phone pretty roughly on a table and I’m afraid I’ll end up cracking the back soon. Secondly, the headphone jack is on top of the phone. This is probably a good idea if you’re charging and listening to music at the same time, but makes it’s a bit awkward for listening on earphones with the phone in your pocket. With the Nexus S (which had the jack at the bottom) it was quite natural to put the phone in your pocket bottom-up and then turn your hand as you pulled it out to see the screen upright. The corresponding motion with the jack on the bottom seems rather more convoluted, but it might just be muscle memory that will get reprogrammed with time. Finally, (and this isn’t unique to the Nexus 4) I’m yet to find a Android to-do or task management app that is flexible enough as OmniFocus on OS X and Android.

All that being said, I am very happy with the Nexus 4. I really liked the Nexus S when I first got it and I’ve always liked Android. The Nexus 4 is a significant upgrade and I pretty impressed by the current state of the Android ecosystem. Barring unforeseen problems (or a very cheap upgrade option) I fully expect to hold on to this as my primary mobile device for the next few years. I don’t have any experiences with other Android devices (or other smartphones for that matter) so I can’t really compare, but I’m willing to take a chance and say you can’t get much better than a clean stock Android (especially if you use Google services as much as I do). As a final happy ending, I managed to hand off my Nexus S to a friend who decided to move up from a dumb phone. That makes one less unused device for me to keep around.

Sunday Selection 2013-06-02

Posted on by

Happy June Everyone! Hope your summer is off to a good start. Here’s a quick round-up of interesting stuff from the last week of May.

Around the Web

What happened to the Internet productivity miracle?

This isn’t the first article (and it certainly won’t be the last) to ask the question of what effect our technology is really having on us. This one approaches the question from a different angle: why haven’t the documented booms in productivity in the early part of the last decade kept going till the modern day?

Open-plan offices make employees less productive, less happy and more likely to get sick.

I spend most of my time working in Cornell CS’s open-plan Systems Lab. Even though it’s open-plan, it’s quite spacious, the desks face away from each other, it’s generally quiet and it’s easy to ignore things around you and focus on work. At the same time, I still like having an office where I can close the door (and everything else). This article gives a summary of reasons why open plan offices are a bad idea and backs them up with references to studies and surveys.

A Perspective: Developers vs Microsoft

I’ve always had a mild interest in how changing technologies affect the communities and developers that depend on them. It’s interesting to read about how Microsoft’s changing APIs and platforms have attracted and then driven away the developers that build on top of them

Video

The Forge – For Anybody Hurting

I’m lucky to not have lost a family member or a close friend to suicide, depression or any other form of mental illness. However, I do know people who have been affected by it. And while I don’t really believe that watching a single video will cure depression or prevent suicides (though it may save a few people), I do think that this video has a message that’s worth listening to.

Spam and user responsibility

Posted on by

Twitter, like any communication medium (physical or electronic) has a spam problem. They’ve been able to mostly keep it under control, but it surfaces every now and then. I was talking to a friend about this recently and he noted that certain kinds of spam are easier to detect than others. For example, a tweet full of suspicious URLs may very well be spam. But is an account that never tweets but follows lots of people a spam account? Part of this is an perception issue. I personally don’t care about being followed by (possibly) spam accounts. I get more annoyed if I get a tweet from one of them. However, I do know people who are really careful about who follows them. For Twitter, the question is how to tell spam tweets and spammers apart from legitimate traffic and users.

Getting users to report spammers is perhaps the first line of defense. If a large enough group of people report an account as a spammer, there’s a high probability that it actually is a spammer. But on the users side, what is my incentive to report an account as spam? Unfortunately, I feel that Twitter’s nature plays against it in this regard. In particular, a spam tweet is much less annoying than a spam email. Tweets and the Twitter stream are, by design, ephemeral and temporary. You see something and a few hours later it’s gone. You’re not expected to read each and every tweet and you’re certainly not expected to reply to everything and everyone (unless you’re  a self-styled social media guru, but that’s another matter altogether). Reporting a spammer is a pretty high overhead activity, especially with the current web interface. As far as I can tell, you can’t directly report a tweet, you have to click on the user image, click on the profile button and only then do you see the option to report spam. If I see a spam tweet, the easiest thing for me to do is shrug my shoulders and move on — it’ll be out of sight and out of mind in a while anyway.

Contrast this with email: I don’t reply to each and every email, but I do read most of it and I reply to a lot. Reading and answering emails (especially if they’re technical in nature) are fairly high load activities and my inbox definitely isn’t as ephemeral as my Twitter stream. Consequently, getting spam in my email inbox is correspondingly more annoying, especially if it’s more sophisticated spam (like a phishing attempt). It’s in my own best interests to report spam so that I have less to deal with in the future. Furthermore Gmail (and I would hope, most email interfaces) make it easy to report spam — generally just one click (two if you need to open a menu first, sometimes there’s a confirmation request).

(Aside: Note that Twitter associates “spam-ness” with the user, while email conventions associate it with the email itself. Objectively the two are isomorphic: the sender of spam message is very likely a spammer and a spammer account very likely sends out mostly spam. I find the difference is interface and convention interesting from an HCI point of view.)

An argument could be made that reporting spam is the users’ best interest, irrespective of quality of interface and immediate overhead. But I wonder if even this argument doesn’t quite work in Twitter’s case. Twitter is, and has always been, a largely public medium. Private accounts exist and you can block followers, but by and large you use Twitter to share everything with everyone. Email by contrast has always been more personal and private. But this means that reporting spam on Twitter is a lot like picking up litter off the street — it is bothersome, and you know that at some level you should do it, but is it really your problem? What’s really in it for you, and if you don’t do it someone else surely will, right? By contrast, spam email is pretty much exactly  like getting junk mail delivered right to your home.

While Twitter’s image as a public space has probably been key to its success, I do believe that it’s hard to get people interested in taking care of something they don’t have any ownership over (as far as I can tell the only way to pay for Twitter is to buy ads and it’s becoming increasingly harder to hook up non-official clients). To its credit, I haven’t found spam to be much of a problem — most days I don’t see (or at least don’t notice) any spam at all. Whatever they’re doing, it seems to be working. I don’t have any suggestions, just the above ruminations. But if you’re in the process of creating (or interacting with) any sort of user platform, it’s worth spending some time thinking about how to deal with spam.

Sunday Selection 2013-05-05

Posted on by

Happy Cinco de Mayo and Orthodox Easter everyone. Last week has been a bit quiet as far as reading is concerned. I have a hefty backlog in my RSS that probably won’t get cleared till next week. But here’s the pick of what I did read and discover:

Around the Web

10 Rules of  a Zen Programmer I’ve been doing meditation on a regular basis over the past few weeks and it’s been an interesting experience. I definitely feel calmer throughout the day and it’s getting easier to sit down and focus on tasks I would normally procrastinate on. This article agrees closely with both what I’ve been experiencing while meditating and as a programmer. I’m not a Zen practitioner, but you don’t have to be one to use the information this article provides.

I’m still here: back online after a year without the Internet This is the last (I think) in a series of articles by a journalist who spent a year offline. It’s an interesting read, though it ends on a very weak note. The author’s experience seems to agree with my own views on the matter: the Internet (and technology in general) is a tool and it’s up to us to use it best. Using it, or not using, is not suddenly going to make us a better or worse person. It’s up to us to use these tools according to our desires and help realize our potential.

Star Wars: Online review culture is dotted with black holes of bad taste This articles looks at the rise of popular review sites (focusing on Yelp and Amazon) and discusses how the reviews on these sites are often less then helpful to the point of negating the importance and usefulness of a review. There’s research going on at Cornell on better analyzing online reviews and review systems so this article was particularly interesting to me. While there’s something to be said for the usefulness of multiple opinions from different viewpoints, sometimes you just want an authoritative answer from an expert about the quality of a service and product, and that’s increasingly difficult to come by.

Software

Tomato.es As the end of the semester approaches and the amount of stuff I have to get done explodes, I’ve been starting to use the Pomodoro technique to keep on top of things. Tomato.es is a simple timer that counts off 25-minutes intervals. If you sign in using Twitter or Github, you can keep a record of what you’ve been doing in those intervals.